Skip to main content

​
Endpoint

Hosted Klio speaks MCP over Streamable HTTP:
Self-hosted installs expose the same path on whatever host you run the MCP service on.

​
API key

Authenticate with the X-Klio-Key header:
Create keys in the dashboard under Settings → API keys. The key resolves the request to an org, and that org boundary is the one guarantee nothing crosses.
A key is org-wide. Anyone holding it can read and write everything in that org’s memory. Treat it like a database credential: environment variables or a password manager, never a committed file.
X-Vex-Key and the older X-AgentGuard-Key are accepted as legacy aliases for X-Klio-Key, and they will keep working — existing configs never break. New integrations should use the X-Klio-* names. When both a Klio and a Vex header are present, the Klio one wins.

​
OAuth

The hosted MCP server also accepts OAuth bearer tokens, verified against the Klio Cloud issuer, for clients that support the MCP authorization flow. In that case the agent identity defaults to the OAuth client_id unless X-Klio-Agent overrides it.

​
Headers

¹ Unless you are authenticating with an OAuth bearer token instead.

​
X-Klio-Agent

A stable, per-agent string — claude-code, cursor, codex, ci-bot. It is what makes a ledger of “who wrote what” possible, and it is what scope: "agent" resolves against. Clients that omit it are all folded into a single default agent identity. Things still work, but attribution collapses and private scope stops being meaningfully private.

​
X-Vex-Project

Lets a workspace declare its project once instead of passing project on every call. It accepts a git remote URL when the workspace is a git repo, and the repository root directory path when it is not — both resolve to the same project a matching project argument would.
Project resolution fails open: a missing header, an unrecognised identifier, or a lookup error all fall back to org-wide rather than failing the request. This keeps a misconfigured client working, but it means the header is a convenience — never a security control. The security boundary is the org.

​
Errors

A bare GET https://mcp.klio.tech/mcp returning 401 is expected — that is the endpoint confirming it is alive and requires auth.