Tuqo in Kimi Code CLI
In the Kimi ecosystem, MCP is supported by the Kimi Code CLI console agent (the kimi command): remote servers are added with kimi mcp add over http and stored in ~/.kimi/mcp.json. Both Tuqo auth paths work: OAuth via kimi mcp auth, or a tqk_ project key in a header.
Get access ready
Nothing to prepare for OAuth. For a key: the panel at app.tuqo.dev → project → API keys → create (tqk_…, shown once).
Add the server
kimi mcp add --transport http --auth oauth tuqo with the MCP address. The server name is required and goes before the address.
Authorize
kimi mcp auth tuqo opens the browser: sign in to Tuqo, choose the project, the scope and the lifetime. The token stays on your machine.
Deploy
Type /mcp to see the connected server and its tools, then ask the agent to create a site and publish it.
# OAuth: the browser opens by itself
kimi mcp add --transport http --auth oauth tuqo https://mcp.tuqo.ru/mcp
kimi mcp auth tuqo
# Or a project key in a header (the space after the colon is required)
kimi mcp add --transport http tuqo https://mcp.tuqo.ru/mcp \
--header "Authorization: Bearer tqk_xxx_yyy"The Tuqo panel is in English, and the labels here are the ones it shows.
Kimi Code CLI + Tuqo: frequently asked
Is this about the Kimi web chat or the CLI? +
The CLI. Adding your own MCP servers is documented for Kimi Code CLI, Moonshot's console agent. The Kimi web version does not document adding an external MCP server, so connect Tuqo from the CLI.
Where are the config and the tokens? +
Servers live in ~/.kimi/mcp.json (the mcpServers format, compatible with other clients), OAuth tokens in ~/.kimi/mcp-oauth/. List and status: kimi mcp list; remove the entry: kimi mcp remove tuqo.
Error in the key header +
The header format is KEY: VALUE with a space after the colon and the whole string in quotes: "Authorization: Bearer tqk_…". Without the space the header is parsed wrong and the server returns 401.
So many tools. What do I do? +
Tuqo exposes 52 tools. If the model's context is narrow, connect with read-only access (a read-only key, or read-only on the consent screen) and switch to full access for the deploy.
Nothing changed after editing the config +
Restart kimi: MCP servers are read when a session starts. Check the connection with /mcp right in the session: it shows the servers and the loaded tools.