A runtime boundary exists; the public setup workflow is not shipped yet.
Client/runtime contract
The public client defines list, save, delete, and reload requests for MCP servers plus connection status and discovered-tool metadata.
Known transport names
The typed contract names `stdio` and `streamable_http`. It does not validate the old SSE/plain-HTTP setup instructions as a public user workflow.
Timeline support
When a managed runtime already provisions a server, Kition can display qualified tools in `server__tool` form and show server/tool labels in the Agent timeline.
No public config file contract
Do not create `.kition/mcp.json` or paste tokens into workspace files from an old guide. Wait for a release with a tested configuration UI or use separate managed-runtime documentation.
What MCP integration means here
An MCP integration connects an Agent runtime to external tools through a server contract. The existence of client types or runtime APIs is different from a public setup flow that a desktop user can reproduce. The boundaries above describe the verified client surface rather than a configuration tutorial.
Check availability before configuring a server
Identify the installed release, its actual settings controls, and the runtime documentation that applies to it. A configuration file from another client is not automatically a supported Kition file. Do not place access tokens in workspace documents as a substitute for a verified credential flow.
| Evidence | What it establishes |
|---|---|
| Types and API helpers | A software boundary exists |
| Published setup controls | A user can configure the feature |
| Tested connection and tool call | The specific server can be used in that environment |