tuqo

Deploy a site from Claude, ChatGPT or Cursor

With MCP, an AI model can publish sites on its own: you describe the task in plain language, and the agent calls Tuqo tools to create a site, deploy it and attach a domain.

Connecting

  • Claude.ai and ChatGPT (web chats) connect over OAuth. Add a connector with the address https://mcp.tuqo.ru/mcp; sign-in and project selection happen on the Tuqo side, so there is no key to paste. In ChatGPT, external connectors live in Developer Mode.
  • Cursor, Claude Code, Windsurf, Cline, Continue, Zed, Gemini CLI and others connect with a project key tqk_… from the panel. In the client’s MCP settings, set the URL https://mcp.tuqo.ru/mcp and the header Authorization: Bearer tqk_…. Claude Code, Cursor and Codex CLI can also sign in over OAuth in the browser instead.

Keys are created on the project’s AI & API tab. The full key is shown once, so copy it right away.

Step-by-step instructions for each client are on the Connect an AI page, for example Claude, ChatGPT and Cursor.

How to deploy

Just ask the model, for example:

Create a site called my-landing, put this HTML on it and attach the domain example.com

The agent calls the tools it needs (create_site, deploy_files, set_custom_domain and others) and returns a link. There are 56 tools in total, covering sites, deploys, domains, rollbacks, form submissions, analytics and gated access.

What to keep in mind

  • For static files the model generates itself, the best route is deploy_files: the files go up as they are, publishing is instant and uses no build minutes.
  • Build projects (with a package.json) go through deploy_site: Tuqo builds them on Node 24.
  • A media-heavy site can’t be assembled from a browser chat. For those, use the CLI in Claude Code or Cursor: npx @tuqo/cli deploy ./dist --site <site_id>.
  • Hosting is static only: server-side code does not run.

Connect an AI → · MCP docs → · What is MCP →