MCP

MCP quickstart

Connect a compatible AI client, approve one workspace, and verify the connection with a read before allowing changes.

On this page

1. Connect your terminal client

Choose Codex or Claude Code below. Install your chosen CLI first, then run only its commands in your terminal. Both connect to the hosted RouteKite server with OAuth; no API key is needed.

For Codex, add the server and start browser sign-in with these commands. After approving access, start a new Codex session and use /mcp to check the connection.

Codex terminal setup

1codex mcp add routekite --url https://routekite.com/mcp2codex mcp login routekite

Or connect with Claude Code

Run these commands from the project where you want to use RouteKite. The first registers the server for that project; the second opens Claude Code.

Inside Claude Code, type /mcp, select RouteKite, and follow the browser sign-in flow. /mcp is a command inside the Claude Code conversation, not your shell.

Using Claude or Claude Desktop instead of the terminal? Follow the connector steps in Client setup.

Claude Code terminal setup

1claude mcp add --transport http routekite https://routekite.com/mcp2claude

2. Sign in and approve access

RouteKite opens a consent screen. Select the workspace the client may access and choose Read or Manage. Review the access summary before approving.

The client never receives your RouteKite password or a visible RouteKite API key.

3. Start with a read

Ask the client to check workspace readiness or list domains. Confirm that the response belongs to the intended workspace before continuing.

Example request

1Check my RouteKite workspace readiness and explain the next action. Do not change anything.

4. Preview before changing anything

Ask the client to prepare the operation without executing it. RouteKite returns confirmation_required with a structured summary and consequences.

Check recipients, sender, audience, template, storage impact, and destructive consequences as applicable.

5. Confirm, then inspect the result

Approve the exact preview. For tools that accept idempotency_key, the client must reuse one stable key for retries of that same operation.

After execution, retrieve the created object or delivery state. Do not treat a timed-out client response as proof that the operation failed.

6. Review or revoke the connection

Open Developers, then MCP Connections, to review the approved workspace, access level, recent activity, and last use. Revoke a connection that is no longer needed or trusted.