Tuqo in MiniMax Code
MiniMax Code is MiniMax's development agent: an app plus the mcode console command. MCP servers are added under plugin management on the MCP Servers tab, with a form or pasted JSON, and stored in mcp.json in the MiniMax Code data folder (usually ~/.minimax/mcp.json). Plain MCP servers have no OAuth sign-in here, so Tuqo connects with a tqk_ project key.
Create a project key
In the Tuqo panel at app.tuqo.dev → project → AI & API → create. Format tqk_…, shown once.
Open MCP Servers
MiniMax Code → plugin management → the MCP Servers tab → add a server.
Paste the config
In JSON mode, paste the tuqo entry: type streamable-http, the MCP address and the Authorization header (example below). Run the connection test.
Check and deploy
With MiniMax Code running, mcode mcp list --human shows the server and mcode mcp tools tuqo shows the tools. Ask the agent to publish a site.
{
"mcpServers": {
"tuqo": {
"type": "streamable-http",
"url": "https://mcp.tuqo.ru/mcp",
"headers": { "Authorization": "Bearer tqk_xxx_yyy" },
"enabled": true
}
}
}The Tuqo panel is in English, and the labels here are the ones it shows.
MiniMax Code + Tuqo: frequently asked
Do I need OAuth? +
No. Plain MCP servers in MiniMax Code connect with static headers. You create the tqk_ key in the panel at app.tuqo.dev and revoke it there in one click.
How do I avoid keeping the key in plain text? +
The MiniMax Code docs advise against committing tokens and show an environment variable in the header value: "Bearer ${TUQO_API_KEY}".
The server is enabled but has no tools +
Test the server on the MCP Servers tab and run mcode mcp tools tuqo. A 401 means the key is wrong, expired or revoked: check the Authorization header and create a new key if needed.
How many tools does the agent get? +
All 52 Tuqo tools: sites, deploys, domains, rollbacks, gated access, form submissions. The key sets the permissions: editor is enough for deploys.