AI agent
MCP setup status in Kition 0.1.41
Kition has MCP runtime contracts and timeline support, but the 0.1.41 Desktop UI does not expose a supported server-setup workflow.
Updated
By Kition Docs
Verified against Kition 0.1.41 (d3e1b931) on 2026-08-29
Current product status
The public client defines runtime API helpers for listing, saving, deleting, and reloading MCP servers. It also knows how to display server status and qualified MCP tool names.
Kition 0.1.41 Desktop Settings does not include an MCP pane, and the public client does not wire these helpers into a setup screen. There is no verified public <workspace>/.kition/mcp.json setup contract in this release.
Heads up
Do not follow old instructions that tell you to create .kition/mcp.json, use Keychain template references, or open Settings → Agent → MCP. Those surfaces are not shipped in the 0.1.41 public client.
Runtime contract visible in the client
These types document a client/runtime boundary, not a supported end-user configuration format. Passing an arbitrary transport string or header does not prove that a particular runtime will accept it.
- Known transport names are
stdioandstreamable_http - Server fields include name, enabled state, command, args, environment, URL, headers, and optional
auth_ref - Status can include connected state, tool count, last attempt, and an error
- MCP tools are qualified as
server__toolin the Agent timeline
No public setup steps yet
Until a Kition release exposes and tests the configuration UI, keep MCP integration out of production workflows that depend on the public Desktop client. Do not put real API tokens into workspace files to experiment around the missing UI.
If an organization provisions MCP through a managed runtime, use its own administrator documentation, least-privilege credentials, pinned server versions, and read-only smoke tests. That environment is outside the public 0.1.41 Desktop setup contract.
Related article status
The previous MCP setup article has been archived because it described an unverified config file, unsupported transports, OS-keychain references, and permission controls that are not present in the public 0.1.41 client.
Implementation sources
Related pages
Agent tool calls
Read the actual runtime tool names, availability signals, inputs, outputs, errors, and changed-file results shown in the Agent timeline.
Agent approvals and safety boundaries
Use the shell-command approval card and feature-specific previews without assuming Kition 0.1.41 has a universal per-tool permission editor.