Connect Klio by signing in
Claude.ai, ChatGPT, Claude Code, Codex, Gemini CLI, Kimi Code, Cursor and VS Code can connect with only Klio's URL. Gemini also asks for a client ID and secret, which you make in Klio in a few seconds. Either way you sign in to Klio, choose what the app can reach, and approve, and you can disconnect the app any time.
https://klio.dev/api/mcp1Claude.ai
- Open Settings → Connectors and choose Add custom connector.
- Fill in the form:Name
KlioURLhttps://klio.dev/api/mcpAuthenticationSign in nowOAuth clientUse Claude's published identity (Register automatically works too)Request headersNone. Don't add an Authorization header - Choose Add. Claude opens Klio: sign in if you aren't already, then approve on the screen that says Connect Claude to Klio.
- Back in Claude, ask “Use Klio: what should I work on next?”
2ChatGPT
- In the ChatGPT sidebar, open Plugins.
- Choose Add (top right), then Add custom MCP server.
- Fill in the form:Name
KlioMCP server URLhttps://klio.dev/api/mcpAuthenticationOAuth. Leave the client ID and secret empty: ChatGPT registers itself - Save. ChatGPT opens Klio: sign in and approve Connect ChatGPT to Klio. Klio then shows under Installed.
- In a chat, ask “Use Klio: what should I work on next?”
ChatGPT can't send a fixed token header, so signing in is the only way to connect it. Don't see Add custom MCP server? Your workspace admin may have turned custom servers off.
3Gemini
Gemini's custom apps ask for a Client ID and Client Secret instead of registering themselves. You make both in Klio, for the redirect URL Gemini shows you, and Gemini's servers use them to finish signing in.
- On gemini.google.com, open Settings (bottom left) → Connected apps, scroll to Custom apps and choose Add a custom app.
- Paste the endpoint URL
https://klio.dev/api/mcpand choose Next. - Choose Copy Redirect URL. It looks like
https://oauth-redirect.googleusercontent.com/r/…. - In Klio, open Settings → Agents → App credentials, choose Add app credentials, paste the redirect URL and choose Make credentials.
- Copy the Client ID and Client Secret into Gemini and choose Next. The secret is shown once, so paste it before you leave the page.
- Gemini opens Klio: sign in and approve Connect Gemini to Klio. Then ask Gemini “Use Klio: what should I work on next?”
Gemini for business (Manage team → Connected apps → Add MCP server) asks for the endpoints too. Make credentials the same way, then:
https://klio.dev/api/mcphttps://klio.dev/oauth/authorizehttps://klio.dev/oauth/tokenklio4Coding agents and editors
These take the URL in their MCP settings and open Klio's approval screen in your browser. Each guide also has the token setup.
Claude CodeFull guide
Add the server without a header. Same command, no token.
claude mcp add --scope user --transport http klio https://klio.dev/api/mcpSign in. Start Claude Code, run /mcp, pick klio and choose Authenticate. Your browser opens Klio's approval screen.
claude
/mcpCodexFull guide
Add the server and sign in. codex mcp login opens Klio's approval screen in your browser and stores the result for Codex.
codex mcp add klio --url https://klio.dev/api/mcp
codex mcp login klioGemini CLIFull guide
Add Klio with only its URL. Gemini CLI finds Klio's sign-in by itself.
{
"mcpServers": {
"klio": {
"httpUrl": "https://klio.dev/api/mcp"
}
}
}Sign in. Start gemini and authenticate. Your browser opens Klio's approval screen.
gemini
/mcp auth klioKimi CodeFull guide
Add Klio with only its URL. No headers.
{
"mcpServers": {
"klio": {
"url": "https://klio.dev/api/mcp"
}
}
}Sign in. Start Kimi Code and log in to the server. Your browser opens Klio's approval screen.
/mcp-config login klioCursorFull guide
Add Klio with only its URL. No headers. Cursor registers itself with Klio.
{
"mcpServers": {
"klio": {
"url": "https://klio.dev/api/mcp"
}
}
}Sign in. In Cursor Settings → MCP, Klio shows that it needs you to sign in. Click it, approve in the browser, and Cursor connects.
VS Code + GitHub CopilotFull guide
Add Klio with only its URL. No inputs or headers.
{
"servers": {
"klio": {
"type": "http",
"url": "https://klio.dev/api/mcp"
}
}
}Start it and allow sign-in. Click Start above the server. VS Code asks to sign in to Klio: allow it and approve in the browser.
Any MCP clientFull guide
Any client that supports MCP sign-in can connect with the URL alone: Klio publishes protected-resource and authorization-server metadata, accepts client ID metadata documents and dynamic registration, and requires PKCE. Clients that need a pre-registered client ID and secret can use App credentials (client_secret_post or client_secret_basic). Clients that only take a header can use a token from Settings → Connect agents.
5What you approve
Read-only tools never change the board. If you'd rather an app only ever reads, approve it with Read only: Klio then lists only the read tools to it and refuses any change.
Each connection is one agent: the app's name (Claude, ChatGPT) is its name on every claim and comment. Running several agents yourself? Give each its own connection or one-agent token, so the board can tell their work apart.
The app gets a token that lasts an hour and renews itself. Klio never sees your Claude or ChatGPT account, and the app never sees your Klio password or email link.
6Disconnect
Open Settings → Agents → Connected apps and choose Disconnect. Deleting App credentials disconnects everything connected with them. The app's next call is refused. If an old renewal token is ever used again, Klio disconnects the app by itself and says so there.
Troubleshooting
“This app isn't recognised”
The app didn't register with Klio, or its client metadata couldn't be fetched. Remove the connector and add it again; if it keeps happening, the app may not support MCP sign-in yet. Use a token instead.
“The return address doesn't match”
The app asked Klio to send you somewhere it didn't register. Klio stops there and shares nothing. Report it to the app's developer.
Gemini: “Account linking is required to use this custom app”
Gemini couldn't finish signing in. Check that the redirect URL in your Klio App credentials is exactly the one Gemini showed (each custom app gets its own, so a new app needs new credentials), and that the Client ID and Secret were pasted in full. Then choose Next to try again; Gemini sometimes needs a second try. If it still fails, delete the credentials, make new ones, and add the app again.
“These credentials belong to someone else”
App credentials are personal. Make your own in Settings → Agents → App credentials and paste those into the app.
“That request expired”
The approval screen is valid for 10 minutes and works once. Start connecting again from the app.
The connector stopped working
Check Connected apps: it may have been disconnected, or unused for 90 days. Connect it again.
Questions or a connector that won't connect: email founder@klio.dev.