Integrations · Claude
Connect Claude to Kentro over MCP
Add Kentro to Claude as a custom connector and ask about orders, stock and fulfillment in plain language. You sign in to Kentro as yourself and approve the connection. There is no API key to create or store.
- Claude on the web, Claude desktop and Claude Code
- Signs in as you
- Revoke at any time in Kentro
How do I connect Claude to Kentro with MCP?
Copy the Kentro MCP endpoint from Assistant Settings in Kentro IQ. In Claude, open Settings, then Connectors, choose Add custom connector and paste the URL. A browser window opens on Kentro: sign in to your workspace and click Approve. Claude can then read your orders, inventory, fulfillment and reports with your permissions.
What moves
What moves between Claude and Kentro
Nothing is copied on a schedule. Data moves when Claude calls a tool during your chat.
| Data | Direction | When |
|---|---|---|
| Orders, fulfillment and inventory | Kentro to Claude | When Claude calls a read tool such as listOrders or getInventorySummary |
| Report results and query rows | Kentro to Claude | When Claude runs a report with runKiqReport or a read-only query with runSqlQuery |
| Help center articles | Kentro to Claude | When Claude searches with searchKnowledgeBase |
| Your question or task | Claude to Kentro | When Claude calls askCopilot. Kentro AI works inside Kentro and returns its answer. |
| Dashboards and findings | Claude to Kentro | When you ask Claude to build a dashboard or mark a finding done |
| Orders, stock, labels, purchase orders and settings | None | Not available over MCP. People change these in the app. |
Checked on November 17, 2026
Setup
Connect Claude on the web or Claude desktop
Before you start: a Kentro user in a workspace where the assistant is on, your workspace key (acme for acme.kentro.app), and a Claude plan that allows custom connectors.
Step 1: Copy the endpoint in Kentro
In Kentro IQ, open Assistant, then Assistant Settings. In the panel named Connect your AI tools (MCP), copy the Endpoint: https://apis.kentro.live/kiq/v1/copilot/mcp
Step 2: Add a custom connector in Claude
In Claude, open Settings, then Connectors, and choose Add custom connector. Name it Kentro, paste the endpoint and confirm. Claude desktop uses the same steps in its own Settings.
Step 3: Sign in to your workspace
Claude opens a browser window on Kentro. If it does not, connect the new connector from its entry in Connectors. If you are not signed in, type your workspace key, click Continue and sign in as usual.
Step 4: Check the request and approve
The page Connect to Kentro Assistant names the client, the host it returns to (claude.ai for Claude) and your workspace. Click Approve. A request lasts 10 minutes; after that, start again from Claude.
Step 5: Ask your first question
Start a chat with the Kentro connector enabled and ask: "Use getSessionContext and tell me which workspace and user you are connected as."
Claude Code and Codex
One command for Claude Code or Codex
Claude Code and Codex connect from the terminal with one command each and sign in through the browser on first use. In Claude Code, add the server, run /mcp, select kentro-copilot and authenticate. Codex saves the server in its configuration file, finds Kentro's sign-in on first use and opens the browser. Either way the same Kentro approval page opens: sign in and click Approve.
Both commands, with the URL filled in, are also in Assistant Settings in Kentro IQ.
- No token to paste and no API key to store
- The connection acts as the user who approved it
- Use it to check live order and stock data while you build on the Channel API
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/mcpPrompts
What to ask Claude once it is connected
Two prompts are built into the server. Claude lists them where it shows a connector's prompts.
| Prompt or request | What you get |
|---|---|
| daily-ops-digest (built in) | New orders and revenue today against yesterday, the fulfillment pipeline, inventory that needs attention, failed syncs, and the top three actions |
| investigate-order (built in, takes an order number) | One order end to end: status, items, fulfillment orders, warehouse routing, labels and tracking, payment state and channel sync |
| "What were yesterday's top ten products by units sold?" | A ranked list from getTopProducts |
| "Show order 1042 with its fulfillment orders and tracking numbers." | The order from getOrderDetail |
| "Use getSessionContext, then list the tables I can query." | Who the connection acts as, and the tables open to read-only queries |
| "Using askCopilot, find orders unfulfilled for more than three days and explain why each one is stuck." | Kentro AI works through the orders and returns one answer |
Limits and notes
What Claude can and cannot do in Kentro
Claude reads. It looks up orders, inventory, fulfillment, reports and reconciliation exceptions, and it can hand a longer task to Kentro AI. It cannot create orders, buy labels, adjust stock, raise purchase orders or change settings.
Every call runs as the user who approved the connection, in one workspace. If your permission groups restrict data, Claude gets help center answers and no business data.
- 30 calls a minute and 600 a day per user; 120 a minute and 4,000 a day per workspace
- An askCopilot turn uses your workspace's Kentro AI usage, like a chat in the app
- One connection serves one workspace
- A tool result goes to Claude, and from there to Anthropic under your agreement with them
- you ›Which inventory items need attention this week?
- getInventorySummaryRead stock on hand and available by product
- getTopProductsRead the top sellers of the last 30 days
Some of your top sellers have less available stock than they sold last week. I listed them with on hand, available and weekly sales, lowest cover at the top.
Troubleshooting
If the connection does not work
| What you see | What to do |
|---|---|
| "This connection request has expired." | The request is older than 10 minutes or was already used. Start again from Claude. |
| "Your workspace's billing needs attention before an AI client can be connected." | An admin resolves billing in Kentro, then you connect again. |
| "Rate limit exceeded. Retry in 30s." | Wait for the time shown, then ask again. |
| Only knowledge base and tutorial tools appear | Your permissions limit the assistant to help center content. Ask an admin. |
| The connector stopped working | The connection may have been revoked in Assistant Settings. Remove the connector in Claude and add it again. |
Questions about Claude and Kentro
Which Claude plans can add the Kentro connector?
Any Claude plan whose settings allow custom connectors. In a Claude organization, an owner may have to allow custom connectors, or add the Kentro connector for the team, before members can use it. On the Kentro side no admin approval is needed, because a connection carries only the permissions of the user who approved it.
Do I need a Kentro API key to use Claude with Kentro?
No. Claude signs in through the browser with OAuth, as your Kentro user. Claude stores the tokens, and Kentro stores only a hash of the refresh token. API keys are for software you build on the Channel API, where you choose the scopes of each key.
Can I connect Claude to more than one Kentro workspace?
Yes. A connection belongs to the workspace you approved it in. Add a second custom connector with the same URL and a different name, then sign in to the other workspace when the browser window opens. Each connection reads only its own workspace.
How do I disconnect Claude from Kentro?
In Kentro IQ, open Assistant, then Assistant Settings, find the connection under Active connections and click Revoke. Claude loses access at once. Removing the connector in Claude does not revoke it in Kentro, so do both. Admins can see and revoke every connection in the workspace.
Is Claude with the Kentro connector the same as Kentro AI?
No. Kentro AI is the assistant built into Kentro, with your workspace's skills and saved learnings. Claude is your own assistant, working with Kentro's tools from outside. The askCopilot tool joins them: Claude hands a task to Kentro AI and gets the finished answer back.
Ask Claude about your real orders and stock
MCP access is part of every Kentro OS plan.


