Connect Tuqo to your AI
Tuqo is an MCP server: add it as a connector and the model creates sites, builds and deploys projects, attaches domains, sets up auto-deploy from Git and reads form submissions. Web chats sign in over OAuth with no key; CLI and IDE clients use OAuth where they support it, or a project key.
https://mcp.tuqo.ru/mcpFiles ready and no agent needed? Publish them with Tuqo Drop, no sign-up required.
Send your AI one link
The agent opens https://mcp.tuqo.ru (or
https://tuqo.dev/ai.md) and gets a ready
instruction in English: the MCP address, both ways to authenticate and configs for its
client. It then adds the server and starts OAuth itself; you only confirm access on the
Tuqo screen (project, scope, lifetime). The connection appears in the panel and is
revoked in one click.
How each AI connects
| AI or tool | Type | Setup | Scope chosen | Where to configure |
|---|---|---|---|---|
| Claude (claude.ai) Chat | OAuth | Paste the URL | At sign-in | Settings → Connectors |
| ChatGPT Chat | OAuth | Paste the URL | At sign-in | Settings → Connectors (Dev Mode) |
| Claude Code CLI | tqk_ key | URL + header | In the key | Terminal (claude mcp add) |
| Cursor IDE | tqk_ key | URL + header | In the key | Settings → MCP / mcp.json |
| Gemini CLI CLI | tqk_ key | URL + header | In the key | ~/.gemini/settings.json |
| Qwen (Qwen Code) CLI | tqk_ key | URL + header | In the key | Qwen Code config (mcpServers) |
| GigaChat (GigaChain) SDK | tqk_ key | URL + header | In the key | Agent code (MCP client) |
| Windsurf IDE | tqk_ key | URL + header | In the key | Settings → Cascade → MCP / mcp_config.json |
| Cline IDE | tqk_ key | URL + header | In the key | Cline → MCP Servers / cline_mcp_settings.json |
| Continue IDE | tqk_ key | URL + header | In the key | Continue → MCP config (mcpServers) |
| Zed IDE | tqk_ key | URL + header | In the key | Zed → settings.json (context_servers) |
| OpenAI Codex CLI CLI | OAuth | Paste the URL | At sign-in | ~/.codex/config.toml (codex mcp add) |
| OpenCode CLI | OAuth | Paste the URL | At sign-in | opencode.json (mcp block) |
| VS Code + GitHub Copilot IDE | OAuth | Paste the URL | At sign-in | .vscode/mcp.json (MCP: Add Server) |
| Kimi Code CLI CLI | OAuth | Paste the URL | At sign-in | ~/.kimi/mcp.json (kimi mcp add) |
Click a name for step-by-step setup. Public configs and a Claude Code plugin: github.com/antiblef/tuqo-mcp.
Two ways to connect
For chats and clients that sign in through a browser
Claude (claude.ai) and ChatGPT do not store secrets, and Codex CLI, OpenCode, VS Code with Copilot and Kimi Code CLI support MCP authorization over OAuth. You give only the MCP address; sign-in and the choice of project and scope happen on the Tuqo side. The access is visible in the panel and revoked in one click.
- Add https://mcp.tuqo.ru/mcp as a custom connector or remote MCP server. Leave the client ID and secret empty: the client registers itself (dynamic client registration).
- 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.
For CLI, IDE and agents
Claude Code, Cursor, Gemini CLI, Qwen Code and GigaChat can store an Authorization header, and so can the OAuth clients when no browser is at hand (CI, a server). Create a project key (format tqk_…, shown once) and pass it in the header; you set the scope and the lifetime yourself.
- Panel → project → API keys → create a key with the scope you need.
- 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_..." }
}
}
}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 one 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 keys 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, send a tqk_ key in the Authorization header.
Is the panel in English? +
Yes, at app.tuqo.dev. It is the same account as the Russian panel at app.tuqo.ru, with the same sign-in: email and password, Yandex or VK. The labels on these pages are the ones the English panel shows.
Create a project and connect your AI
Free plan, one-minute setup, deploys in plain language.