Client setup
Connect RouteKite to a client that supports remote Streamable HTTP MCP servers and OAuth.
On this page
Start with a prompt
Paste this into a Codex or Claude conversation to ask for setup help. It is a chat prompt, not a terminal command. A prompt alone does not install a connector or authorize access; your client may require the manual setup below.
Connect RouteKite’s MCP server at https://routekite.com/mcp and guide me through signing in.Use the hosted endpoint
Add https://routekite.com/mcp as the remote server URL. Complete RouteKite sign-in, select one workspace, choose Read or Manage, and approve the consent screen.
| Setting | Value |
|---|---|
| Server URL | https://routekite.com/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth with PKCE |
| Visible API key | Not required |
Client guidance
| Client | Where to add RouteKite | Important limitation |
|---|---|---|
| Codex | Add a remote MCP server and complete the browser authorization | Reconnect after RouteKite adds tools so the manifest refreshes |
| Claude Code | Register the HTTP server in your terminal, then use /mcp inside Claude Code | Default registration is scoped to the current project; complete browser sign-in |
| Claude and Claude Desktop | Customize, Connectors, +, Add custom connector | Organization owners add connectors for Team and Enterprise; each member then connects individually |
| Cursor | MCP settings or a remote entry in mcp.json | Use Streamable HTTP and complete OAuth when prompted |
| ChatGPT | Settings, Apps, Create a custom MCP app | Plan, workspace admin settings, and action permissions control read and write availability |
Connect with Codex
With Codex CLI installed, run these commands in your terminal. The first adds the hosted server; the second starts OAuth sign-in. Select your RouteKite workspace and access level in the browser.
Then start a new Codex session and use /mcp to check the connection. If you prefer the Codex IDE extension, open MCP servers from its gear menu, add a Streamable HTTP server with the same URL, and authenticate when prompted.
codex mcp add routekite --url https://routekite.com/mcpcodex mcp login routekite
Connect with Claude Code
With Claude Code installed, run these commands in your project directory. The server is registered for that project by default, then Claude Code opens.
Inside Claude Code, type /mcp, select RouteKite, and complete browser sign-in. Choose your RouteKite workspace and access level, then verify with a workspace readiness read. Do not run /mcp in your shell.
claude mcp add --transport http routekite https://routekite.com/mcpclaude
Connect with Claude or Claude Desktop
- 1
Add the connector
In Claude or Claude Desktop, open Customize, then Connectors. Use + and Add custom connector, and enter https://routekite.com/mcp. Older versions may place Connectors under Settings.
- 2
Sign in
Add RouteKite, choose Connect, and complete RouteKite sign-in and workspace consent. On Team or Enterprise, an organization owner must add the connector before members can connect.
- 3
Enable it in your conversation
Open the conversation’s + menu, choose Connectors, and enable RouteKite. Ask for workspace readiness to verify the connection.
First-session checklist
- Confirm RouteKite appears in the client's connected tools list.
- Refresh the tool list and confirm the expected production capabilities are visible.
- Run a readiness or domain read and confirm the intended workspace.
- Preview a harmless change and confirm that no data changes.
- Keep automatic approval disabled for sending and destructive tools.
Local stdio for self-managed development
The repository package can run over stdio with a dedicated scoped RouteKite API key. This path is for engineering and private automation, not the normal customer setup.
Keep ROUTEKITE_API_KEY in the process environment and use the production API base unless you are developing RouteKite itself.