Connect your agent to Tuqo
One endpoint, two ways in. Web chats sign in over OAuth with no key to paste; CLI and IDE clients use OAuth where they support it or a project key.
https://mcp.tuqo.ru/mcp OAuth 2.1, no key
- Add https://mcp.tuqo.ru/mcp as a custom connector or remote MCP server. Leave client id and secret empty: the client registers dynamically.
- The browser opens Tuqo. Sign in with Yandex ID, VK ID or email.
- Pick the project, the scope and the lifetime on the consent screen.
- Ask the agent to run whoami, then to publish a site.
Project key
- Panel → project → «API-ключи» → create a key with the scope you need. It is shown once.
- Put it in the client config as a header.
- Restart the client and run whoami.
{
"mcpServers": {
"tuqo": {
"url": "https://mcp.tuqo.ru/mcp",
"headers": { "Authorization": "Bearer tqk_..." }
}
}
} Clients
| Client | Type | Auth | Where to configure |
|---|---|---|---|
| Claude (claude.ai) | Chat | OAuth, no key | Settings → Connectors |
| ChatGPT | Chat | OAuth, no key | Settings → Connectors (Dev Mode) |
| OpenAI Codex CLI | CLI | OAuth, no key | ~/.codex/config.toml (codex mcp add) |
| OpenCode | CLI | OAuth, no key | opencode.json (блок mcp) |
| VS Code + GitHub Copilot | IDE | OAuth, no key | .vscode/mcp.json (MCP: Add Server) |
| Kimi Code CLI | CLI | OAuth, no key | ~/.kimi/mcp.json (kimi mcp add) |
| Claude Code | CLI | tqk_ key (OAuth where the client supports it) | Терминал (claude mcp add) |
| Cursor | IDE | tqk_ key (OAuth where the client supports it) | Settings → MCP / mcp.json |
| Gemini CLI | CLI | tqk_ key (OAuth where the client supports it) | ~/.gemini/settings.json |
| Qwen (Qwen Code) | CLI | tqk_ key (OAuth where the client supports it) | Конфиг Qwen Code (mcpServers) |
| GigaChat (GigaChain) | SDK | tqk_ key (OAuth where the client supports it) | Код агента (MCP-клиент) |
| Windsurf | IDE | tqk_ key (OAuth where the client supports it) | Settings → Cascade → MCP / mcp_config.json |
| Cline | IDE | tqk_ key (OAuth where the client supports it) | Cline → MCP Servers / cline_mcp_settings.json |
| Continue | IDE | tqk_ key (OAuth where the client supports it) | Continue → конфиг MCP (mcpServers) |
| Zed | IDE | tqk_ key (OAuth where the client supports it) | Zed → settings.json (context_servers) |
Per-client pages are in Russian; the English setup guide with config snippets for every client is ai.en.md. Public configs and a Claude Code plugin: github.com/antiblef/tuqo-mcp.
No Tuqo account yet?
An agent can publish a draft without sign-up: POST https://api.tuqo.ru/instant/deploy with the files and accept_terms: true. The draft lives 24 hours and comes with a claim link to move it into an account.
Details in ai.en.md
Connecting — frequently asked
Which scope should an agent get? +
read-only for browsing and stats, editor for deploys and forms, full for domains, deletion and access settings. With OAuth the person chooses on the consent screen; with a key the scope is fixed when the key is created.
Can I use one key for several projects? +
No. A key belongs to a project and sees only its sites. Create a key per project, or connect over OAuth and pick the project when signing in.
How do I revoke access? +
Panel → project → «Подключения ИИ» (AI connections) lists OAuth connections; «API-ключи» lists keys. Revoking is one click and takes effect immediately.
The client says 401 or opens a browser +
That is the OAuth flow starting: the server answers 401 with WWW-Authenticate, the client registers itself and asks you to sign in. Complete the sign-in and choose the project.
Does the server work with clients not listed here? +
Any MCP client that speaks Streamable HTTP works. If it cannot do OAuth, use a tqk_ key in the Authorization header.