Docs / MCP server
MCP server
Give Claude Code, Cursor, VS Code and other MCP clients read-only access to the clusters open in Klystiq, with changes you approve.
Turn on Settings → MCP server and coding agents on this computer can use read-only tools on the contexts open in Klystiq.
Tools
- list contexts;
- list and get resources;
- events;
- metrics from Prometheus;
- container logs, if you allow them;
show_in_klystiq, which opens an object in a new tab in Klystiq.
Secret values are never returned.
Connect a client
Settings shows the exact command and a JSON snippet, with your token filled in, and a New token… button.
Claude Code:
claude mcp add --transport http klystiq http://127.0.0.1:47615/mcp \
--header "Authorization: Bearer <token>"
Cursor, VS Code and other clients that read JSON:
{
"mcpServers": {
"klystiq": {
"type": "http",
"url": "http://127.0.0.1:47615/mcp",
"headers": { "Authorization": "Bearer <token>" }
}
}
}
Settings also lists the calls agents made recently.
Security
- The server listens on
127.0.0.1only, on port 47615 by default. - Every request needs a random bearer token, kept in a private file next to Klystiq's settings.
- Requests from web pages are refused.
Letting agents propose changes
With Let agents propose changes turned on (it's off by default), agents also get three tools:
propose_scale;propose_restart;propose_apply, for one object, with server-side apply.
Each opens a dialog in Klystiq with the agent's name and reason, and, for an apply, a dry-run diff. Nothing changes until you approve. The agent waits up to 5 minutes for your answer and is told what happened. Read-only contexts refuse proposals, and approved changes are recorded in the audit log as coming from the agent.