Skip to content

Kentro MCP ยท For Claude, Claude Code and Codex

Connect your AI assistant to your operations

Add one URL to Claude, Claude Code or Codex and ask about orders, stock and fulfillment. You sign in to Kentro as yourself and approve the connection, so the assistant sees exactly what you can see.

  • Claude on the web and desktop, Claude Code and Codex
  • OAuth sign-in as you, no API key
  • Revoke in Assistant Settings
  • Two built-in prompts
Kentro MCP endpoint
https://apis.kentro.live/kiq/v1/copilot/mcp

What is an ERP MCP server?

An ERP MCP server lets an AI assistant such as Claude or Codex use your business system through the Model Context Protocol, an open standard for connecting assistants to tools and data. The Kentro MCP server signs your assistant in as you, then gives it Kentro's order, inventory, fulfillment, reporting and reconciliation tools with your permissions.

Setup

Connect Claude in four steps

Claude on the web and Claude desktop shown. Claude Code and Codex use the same URL and the same approval, with one command each.

  1. Step 1: Copy the endpoint

    In Kentro IQ, open Assistant, then Assistant Settings. In the Connect your AI tools (MCP) panel, copy the endpoint: https://apis.kentro.live/kiq/v1/copilot/mcp

  2. Step 2: Add a custom connector

    In Claude, open Settings, then Connectors, and choose Add custom connector. Name it Kentro and paste the endpoint. In a Claude organization, an owner may need to allow custom connectors before you can add one.

  3. Step 3: Sign in and approve

    A browser window opens on Kentro. Enter your workspace key if asked and sign in as usual. Check the client and workspace named on the Connect to Kentro Assistant page, then click Approve. A request expires after 10 minutes.

  4. Step 4: Ask a question

    Ask "Use getSessionContext and tell me which workspace you are connected to." Then run the daily-ops-digest prompt for a summary of today's orders, fulfillment and stock.

Claude Code and Codex

One command for coding agents

Claude Code and Codex connect with one command and sign in through the browser when they connect. There is no token to paste.

The same commands, with your URL filled in, are in Kentro IQ under Assistant Settings.

  • Claude Code: run /mcp, select kentro-copilot and authenticate
  • Codex: sign in and approve when the browser opens
  • Then ask which workspace you are connected to
Add Kentro MCP to Claude Code or Codex
claude mcp add --transport http kentro-copilot https://apis.kentro.live/kiq/v1/copilot/mcp
codex mcp add kentro-copilot --url https://apis.kentro.live/kiq/v1/copilot/mcp

Other MCP clients

What another MCP client needs to connect

Kentro supports Claude and Codex. Another client can use the same URL if it supports everything in this table.

Requirements an MCP client must meet to connect to the Kentro MCP server
RequirementKentro MCP
TransportRemote Streamable HTTP at the server URL. No local (stdio) server and no package to install.
DiscoveryThe client reads the WWW-Authenticate header of the 401 answer and the protected resource metadata it points to.
Client registrationOAuth dynamic client registration (RFC 7591) as a public client, with no client secret.
Redirect URIhttps, or loopback (localhost, 127.0.0.1 or [::1]) on any port. Other schemes are refused at registration.
FlowAuthorization code with PKCE (S256), scope copilot, with refresh tokens.
TokenSent in the Authorization: Bearer header only. The access token lasts one hour.

A client that can only send a fixed API key or header cannot connect: Kentro MCP accepts no static tokens and no Kentro API keys. The docs list the discovery and authorization server addresses.

Checked on November 17, 2026

Tools

What your assistant can do, tool by tool

The server mirrors the tools Kentro AI uses, so a new tool reaches your client on the release that adds it. Your client lists the current set.

Kentro MCP tools by area, with what each group reads or writes
AreaToolsReads or writes
Kentro AI and contextaskCopilot, getSessionContextHands a task to Kentro AI; tells your client who it acts as and which tables it can query
Orders and fulfillmentgetOrdersSummary, listOrders, getOrderDetail, getFulfillmentPipelineReads
Inventory and productsgetInventorySummary, getTopProductsReads
Data querieslistQueryableTables, describeTable, sampleTable, runSqlQueryReads, on a read-only database connection
Reports and dashboardslistKiqReports, describeKiqReport, runKiqReport, listDashboards, createDashboardReads reports; Kentro AI builds dashboards
FindingsgetRecommendations, actOnFindingReads findings; marks one done or skipped
Reconciliationlist_recon_exceptions, get_recon_exception, explain_variance, suggest_matches, summarize_recon_periodReads and suggests; a person commits every fix
Knowledge and memorysearchKnowledgeBase, getKbArticle, listMyConversations, recallConversation, saveCopilotLearningReads help articles and your past chats; saves learnings
Orders, stock, purchase orders and labelsNoMCP toolOrders, stock and retailer purchase orders through the Channel API; vendor purchase orders and labels in the app

Built-in prompts: daily-ops-digest and investigate-order (takes an order number). Two tools stay inside the Kentro web app: triggerInteractiveTutorial and renderVisualization.

Checked on November 17, 2026

Permissions and control

Every call runs as you

Each call runs as the user who approved the connection, in the workspace it was approved in. Permissions are checked on every request, so a change to your role applies to the next call.

Users whose permission groups restrict data get help center answers and no business data. Admins see every connection in the workspace and can revoke any of them.

  • OAuth sign-in as you; no API key to store
  • Data questions run on a read-only connection
  • Connections are listed in Assistant Settings and can be revoked there
  • Rate limits: 30 calls a minute and 600 a day per user; 120 a minute and 4,000 a day per workspace
Security at Kentro
A key: the connection signs in as you

Questions about the Kentro MCP server

Which assistants support the Kentro MCP server?

Kentro supports Claude on the web and Claude desktop, Claude Code and Codex. Another MCP client can use the same URL if it supports remote Streamable HTTP and OAuth with dynamic client registration, the authorization code flow with PKCE and a bearer token. A connection belongs to the workspace you approved it in. To connect a second workspace, add another connector with the same URL and a different name, then sign in to that workspace.

Can the agent change my data?

Over MCP, your assistant reads orders, inventory, fulfillment, reports and reconciliation exceptions. Through Kentro AI it can also build dashboards, and it can mark findings done and save learnings. It cannot create orders, buy labels, adjust stock or change settings. Writes to operational records go through the Channel API, with a key that holds a write scope.

Does MCP access cost extra?

MCP and API access are part of every Kentro OS plan. When your assistant hands a task to Kentro AI with askCopilot, that turn uses the workspace's Kentro AI usage, like a chat in the app: $50 a month is included, and usage beyond it is metered at published rates up to a cap you set.

How is this different from the Kentro API?

MCP is for assistants that work for a person: they sign in as that person and use Kentro's tools in a conversation. The REST APIs are for software: an integration or an agent you build uses an API key with the scopes you choose. MCP reads and analyzes, and the Channel API writes orders, stock levels, shipments, invoices, payments and retailer purchase orders. Vendor purchase orders are created by a person in the app.

What data leaves Kentro when I connect an assistant?

A direct tool call sends its result, such as order details or query rows, to your AI client, which passes it to its model provider under your agreement with them. With askCopilot, Kentro AI runs inside Kentro and returns its final answer. Kentro receives what your client sends in tool calls and does not see the rest of your conversation.

Can I build my own agent on Kentro?

Yes. Use the MCP server for reading and analysis, and the Channel API for writes with a key that holds the channel:write scope. Every write takes an Idempotency-Key header, so a retried call never writes twice. The developer docs include an llms.txt index, ready prompts and agent skills for coding agents.

Your assistant, connected to the real numbers

One URL, one approval, and the same permissions you have in Kentro.

Choose what this site may use. Necessary storage is always on.

  • Necessary

    Remembers this choice for 12 months and keeps forms safe from spam. No tracking.

    Always on

Cookie policyPrivacy policy