tuqo
50 tools · OAuth 2.1 · Streamable HTTP

An MCP server that publishes websites

Any MCP client turns into a deploy tool: create a site, publish files, attach a domain, read form submissions, gate access, roll back. The person sees a live URL; the model sees structured results with a hint for the next step. 

https://mcp.tuqo.ru/mcp
Connect a client Server card (JSON) →

Built for agents

next_action in every response

Each tool result says what to do next, so an agent does not guess the workflow: create_site → deploy_files → show the URL → offer a domain or a form.

Idempotent deploys

deploy_files accepts an idempotency_key; a retry after a timeout returns the same deploy instead of a duplicate.

Edits without re-uploading media

get_manifest returns path and sha256 for the active version; unchanged files are referenced by hash, only changed files carry content.

OAuth consent chosen by the person

On the consent screen the user picks the project, the scope (read-only, editor, full) and the lifetime. Connections are listed and revoked in the panel.

Recommendations, not errors

After a publish the response may carry recommendations from 14 site checks: advice to relay to the person, never a blocker.

Drafts without an account

POST https://api.tuqo.ru/instant/deploy publishes a 24-hour draft with a claim link, so an agent can show a result before the person signs up.

All 50 tools

Sites (8)

list_sitescreate_siteget_siteupdate_sitedelete_siterestore_sitelist_trashedset_site_enabled

Deploys (9)

deploy_filesdeploy_siteget_manifestget_deploy_statuslist_deploysget_logsactivate_deployget_preview_urldelete_deploy

Domains and start (5)

set_custom_domainverify_domainlist_domainsdelete_domainwhoami

Forms (7)

get_forms_overviewget_form_submissionsget_autoreplyset_autoreplyadd_autoreply_fileremove_autoreply_fileset_autoreply_delivery

Analytics (1)

get_site_stats

Gated access (16)

get_site_accessset_site_passwordreveal_site_passwordopen_site_accessset_site_email_accessset_site_subscribers_accesslist_messenger_channelslist_site_access_emailsadd_site_access_emailadd_site_access_emailsset_site_access_email_labelremove_site_access_emailremove_site_access_emailsset_site_access_expiryset_site_access_opensset_site_access_brand

Member sign-up (4)

set_site_members_accessget_site_membersmoderate_site_memberset_site_documents

Files for agents and catalogs

Descriptions in the list above are Russian; the files themselves that agents read (SKILL.md, prompt.md, openapi.json, mcp.json) are in English.

MCP server — frequently asked

What is the endpoint and transport? +

https://mcp.tuqo.ru/mcp, JSON-RPC 2.0 over Streamable HTTP. A GET on https://mcp.tuqo.ru/ returns a Markdown self-description; the server card is at /.well-known/mcp.json.

How does authentication work? +

Two ways. OAuth 2.1 with dynamic client registration: add the server, the client gets a 401 with WWW-Authenticate, registers itself and opens the browser; the person signs in to Tuqo and confirms the project and scope. Or a project API key created in the panel, sent as Authorization: Bearer tqk_…

Which call should an agent make first? +

whoami. It returns the project, its name and the scopes of the current connection.

Is there a REST API with the same features? +

Yes: https://api.tuqo.ru/api/v1 with the same project keys. The OpenAPI 3.1 description is at https://tuqo.ru/openapi.json.

Are tool descriptions in English? +

Yes. Tool and parameter descriptions, instructions and error texts are in English. Panel labels quoted in instructions stay Russian with an English gloss, because that is what the person sees in the UI.

Is the server listed anywhere? +

In the official MCP registry as ru.tuqo/mcp and on Glama. The public repository with the server card, a Claude Code plugin and client configs is github.com/antiblef/tuqo-mcp.