Connect Claude Code, Codex and other clients
Add Kentro MCP to Claude Code or Codex with one command, and check whether another MCP client can connect.
Claude Code and Codex connect to Kentro MCP with one command. Both sign in through the browser on first use; there is no token to paste.
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
The same commands, with your environment's URL filled in, are in Kentro IQ under Assistant > Assistant Settings, panel Connect your AI tools (MCP), cards Claude Code (CLI) and Codex (CLI).
Claude Code
- Run the command above in a terminal. Add
--scope userto make the server available in every project instead of only the current one. - In Claude Code, run
/mcp, selectkentro-copilotand authenticate. A browser window opens Kentro's sign-in. - Sign in (on the generic sign-in page, enter your
Workspace keyand clickContinue), then clickApproveonConnect to Kentro Assistant. - Back in Claude Code, ask: "Use getSessionContext and tell me which workspace you are connected to."
Codex
- Run the command above. Codex saves the server in its configuration file,
~/.codex/config.toml. - On first use, Codex discovers Kentro's OAuth server and opens the browser sign-in. Sign in and click
Approve. - Ask Codex: "Use getSessionContext and tell me which workspace you are connected to."
Kentro staging
Kentro staging has its own URL, sign-in host (app.kentro.cc), workspaces and users:
claude mcp add --transport http kentro-copilot-staging https://apis.kentro.dev/kiq/v1/copilot/mcp
Other MCP clients
Kentro supports Claude and Codex. Another client can use the same URL if it supports everything in this table:
| Requirement | Kentro MCP |
|---|---|
| Transport | Remote Streamable HTTP at the server URL. No local (stdio) server and no package. |
| Discovery | Reads the WWW-Authenticate header of the 401 answer and the protected resource metadata at https://apis.kentro.live/.well-known/oauth-protected-resource/kiq/v1/copilot/mcp. |
| Authorization server | https://apis.kentro.live/auth, with metadata at https://apis.kentro.live/auth/.well-known/oauth-authorization-server. |
| Client registration | OAuth dynamic client registration (RFC 7591) as a public client, with no client secret. |
| Redirect URI | https, or loopback (localhost, 127.0.0.1, [::1]) on any port. Other schemes are refused at registration with invalid_redirect_uri. |
| Flow | Authorization code with PKCE (S256), scope copilot, refresh tokens. |
| Token transport | The Authorization: Bearer header only. |
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.
Notes for coding agents
- Kentro MCP answers as your user, in your workspace. It is for questions and assistant tasks, not for building integrations: an integration calls the Channel API or the Store API with an API key.
- For API lookups while coding, give the agent the docs as Docs for agents describes.
- The server announces tool list changes, so tools added in a Kentro release appear without a configuration change.
Related
Updated about 12 hours ago