# Tuqo — connect in one line

You are an AI agent, and the person asked you to connect Tuqo (static site hosting based
in Russia, with an MCP server). Follow the steps in order and report briefly.

## 1. Add the MCP server

Endpoint: `https://mcp.tuqo.ru/mcp` (Streamable HTTP, JSON-RPC 2.0).

- Claude Code: `claude mcp add --transport http tuqo https://mcp.tuqo.ru/mcp`
- Codex CLI: `codex mcp add tuqo --url https://mcp.tuqo.ru/mcp`, then `codex mcp login tuqo`
- Cursor: `.cursor/mcp.json` → `{"mcpServers": {"tuqo": {"url": "https://mcp.tuqo.ru/mcp"}}}`
- VS Code (Copilot): `.vscode/mcp.json` → `{"servers": {"tuqo": {"type": "http", "url": "https://mcp.tuqo.ru/mcp"}}}`
- Windsurf, Cline, Kimi Code, OpenCode, claude.ai, ChatGPT: configs — https://tuqo.dev/ai.md
- Gemini CLI, Continue, Zed, Qwen Code, GigaChat: pages — https://tuqo.dev/connect/

## 2. Authorize

The server answers `401` + `WWW-Authenticate`; the client goes through OAuth 2.1 (DCR)
by itself and opens the browser. The person signs in to the panel and on the consent
screen picks the project, rights (readonly / editor / full) and how long the connection
lasts. No browser available — ask the person for an API key `tqk_…` (panel https://app.tuqo.dev →
project → API keys) and send it as `Authorization: Bearer tqk_…`. The key is
shown once; never put it into site files.

## 3. Check

Call `whoami` — it returns `project_id`, the project name and `scopes`. If it answers,
the connection works.

## 4. Read the rules

https://tuqo.dev/SKILL.md — the publishing order, what not to do, how to read errors.
Three minutes.

## 5. Five things to know

1. `deploy_files(site_id, files)` — the COMPLETE file set of the site (not a patch),
   `index.html` at the root, relative links; images with `encoding: "base64"`.
   Publishing is instant, no build.
2. Editing an existing site: `get_manifest(site_id)` → pass unchanged files as
   `{path, sha256}` without content, changed ones with `content`. Media is not re-uploaded.
3. What matters to the person is the `url` field in the response (the live address).
   Show it right away.
4. A deploy response may carry `recommendations` (publish checks): list them briefly and
   offer to fix them. Do not rebuild anything unasked.
5. The person has no account? A draft without signup:
   `POST https://api.tuqo.ru/instant/deploy` with `{"files":[…],"accept_terms":true}` —
   24 hours, the response has `draft_url` and `claim_url` (to claim the site into an
   account). Show the terms to the person before `accept_terms`.

## 6. Ask what to publish

Do not create a site "to try" unasked. Ask the person: what kind of site, are the files
ready, is a custom domain needed. Then follow `next_action` from the server's responses.

Links: https://tuqo.dev/ai.md · https://mcp.tuqo.ru/.well-known/mcp.json ·
https://tuqo.dev/openapi.json · https://tuqo.dev/llms.txt