Tuqo in Kimi Code CLI
Kimi Code CLI (the kimi command) is Moonshot AI's console agent. It reads MCP servers from ~/.kimi-code/mcp.json (a project's .kimi-code/mcp.json overrides it), and you can add or edit them right in a session with /mcp-config. Both Tuqo auth paths work: OAuth in the browser, or a tqk_ project key in a header.
Add the server
In a kimi session, type /mcp-config and add a tuqo server with the MCP address, or write the entry into ~/.kimi-code/mcp.json (example below). Only new sessions see a file edit, so start a new one afterwards.
Authorize
OAuth: /mcp-config login tuqo opens the browser: sign in to Tuqo, choose the project, the scope and the lifetime. For a key, see the question below.
Check
/mcp shows the server status and its tools.
Deploy
Ask the agent to create a site and publish it. It calls create_site and deploy_files and returns the live link.
{
"mcpServers": {
"tuqo": { "url": "https://mcp.tuqo.ru/mcp" }
}
}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.
There used to be kimi mcp add and a ~/.kimi folder +
That was the previous Kimi CLI; its repository is now archived. Kimi Code CLI keeps its config in ~/.kimi-code/mcp.json and edits servers with /mcp-config. kimi migrate copies server entries but not OAuth tokens, so sign in again with /mcp-config login tuqo.
How do I connect with a key instead of OAuth? +
Add a headers field to the tuqo entry: { "Authorization": "Bearer tqk_…" }. You create the key in the panel at app.tuqo.dev → project → AI & API. To keep the key out of the file, Kimi Code can read the token from an environment variable: put its name in bearerTokenEnvVar.
Where do I keep the key so it doesn't leak? +
In your user ~/.kimi-code/mcp.json or in an environment variable (bearerTokenEnvVar), not in the project's .kimi-code/mcp.json, which is easy to commit. With OAuth there is no key in the file at all.
So many tools. What do I do? +
Tuqo exposes 56 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.