Connect an AI client

Every client connects the same way: add the server URL, then sign in to LetKite in the browser window the client opens. There is no API key to copy.

Server URL:

https://mcp.letkite.com/mcp

Before you start, you need a LetKite account with at least one machine connected. You can check both in the console at https://dashboard.letkite.com.

What happens when you sign in

1. The client finds LetKite's sign-in server by itself, from the server URL, and registers as a client (see Sign-in and access).
2. A LetKite page opens. Sign in, choose the LetKite account if you belong to several, then choose what the client may do: its scopes, which machines it reaches, and the policy that limits it.
3. After you approve, the client receives a token for this connection only. The console lists the connection under Connections, where you can disconnect it at any time.

Claude (web and desktop)

1. In Claude, open Settings → Connectors → Add custom connector.
2. Name it LetKite and paste the server URL. Leave the advanced OAuth fields empty: Claude registers itself.
3. Choose Connect and sign in to LetKite in the window that opens.
4. In a conversation, turn LetKite on in the tools menu. Claude asks before each tool call unless you allow it for the conversation.

On Team and Enterprise plans, an organization owner may need to add the connector first.

Claude Code

claude mcp add --transport http letkite https://mcp.letkite.com/mcp

Then run /mcp in Claude Code, choose letkite and Authenticate; your browser opens the LetKite sign-in page. Add --scope user to make it available in every project.

ChatGPT

1. Turn on developer mode: Settings → Apps & Connectors → Advanced settings → Developer mode.
2. Under Apps & Connectors, choose Create, name it LetKite, paste the server URL and choose OAuth as the authentication.
3. Sign in to LetKite in the window that opens. In a chat, pick LetKite from the developer mode tools.

ChatGPT shows a confirmation before tools that change things, based on their destructiveHint annotations.

Cursor

Add LetKite to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "letkite": { "url": "https://mcp.letkite.com/mcp" }
  }
}

Open Cursor Settings → MCP; LetKite shows Needs login. Choose it to sign in.

VS Code

With GitHub Copilot's agent mode, add LetKite to .vscode/mcp.json in a workspace, or run MCP: Open User Configuration for all workspaces:

{
  "servers": {
    "letkite": { "type": "http", "url": "https://mcp.letkite.com/mcp" }
  }
}

Or from a terminal:

code --add-mcp '{"name":"letkite","type":"http","url":"https://mcp.letkite.com/mcp"}'

Start the server from the file or the MCP: List Servers command; VS Code asks to sign in.

Codex

codex mcp add letkite --url https://mcp.letkite.com/mcp
codex mcp login letkite

This adds LetKite to ~/.codex/config.toml, which you can also edit by hand:

[mcp_servers.letkite]
url = "https://mcp.letkite.com/mcp"

Kimi Code

kimi mcp add --transport http letkite https://mcp.letkite.com/mcp

The first time Kimi Code uses LetKite, it opens the LetKite sign-in page in your browser.

Other clients

Any MCP client that supports Streamable HTTP and OAuth 2.1 with dynamic client registration or client ID metadata documents can connect with the server URL alone. Clients that cannot register themselves are not supported yet; write to contact@letkite.com.

Check that it works

Ask the AI: “List my LetKite hosts.” It should call list_hosts and show your machines. If it shows none, connect a machine in the console first. If the call is refused, check the connection's policy in the console under Connections.