Tuqo in Gemini CLI
Gemini CLI connects MCP servers through its settings.json (the mcpServers block). Add the Tuqo address and an authorization header with a project key, then manage sites from the terminal in plain language.
Create a project key
In the Tuqo panel at app.tuqo.dev → project → API keys → create. Format tqk_…, shown once.
Open settings.json
The Gemini CLI config (~/.gemini/settings.json), the mcpServers block.
Add the Tuqo server
httpUrl with the MCP address and an Authorization header (example below).
Deploy
Ask it to create a site and publish it: Gemini calls the Tuqo tools.
{
"mcpServers": {
"tuqo": {
"httpUrl": "https://mcp.tuqo.ru/mcp",
"headers": { "Authorization": "Bearer tqk_xxx_yyy" }
}
}
}The Tuqo panel is in English, and the labels here are the ones it shows.
Gemini CLI + Tuqo: frequently asked
url or httpUrl? +
For HTTP transport Gemini CLI expects httpUrl. If your client uses SSE, check its documentation for the field name.
Do I need a Google account for Tuqo? +
No. Tuqo authenticates with the tqk_ key. A Google account is only needed for Gemini CLI itself.
Which scope should the key have? +
Any. Deploys need editor or full.