tuqo
CLI · tqk_ key in a header

Tuqo in Claude Code

Claude Code (Anthropic's CLI and desktop app) connects MCP servers over HTTP. There are two ways: a tqk_ project key in a header, handy for CI and scripts, or the same command without a key. Then Claude Code opens the browser and you approve access (project, scope, lifetime) on a Tuqo page.

Project key in the Authorization header · scope of your choice
1

Create a project key

In the Tuqo panel at app.tuqo.dev → project → API keys → create. Format tqk_…, shown once.

2

Add the MCP server

Run claude mcp add with the address and the authorization header (below).

3

Check the connection

Ask "show my sites": Claude Code calls list_sites.

4

Deploy

"Build the project and publish it." The agent publishes the static files and returns the link.

claude mcp add --transport http tuqo https://mcp.tuqo.ru/mcp \
  --header "Authorization: Bearer tqk_xxx_yyy"

The Tuqo panel is in English, and the labels here are the ones it shows.

Claude Code + Tuqo: frequently asked

Can I connect without a key (OAuth)? +

Yes: run the same claude mcp add command without --header. On first use Claude Code opens the browser, you sign in to Tuqo and approve access (project, scope, lifetime). The connection appears under AI connections and is revoked there. A tqk_ key is more convenient for CI and scripts that have no browser.

What access does the key have? +

You set the key's scope when you create it: read-only, editor or full. Deploys need editor or full.

Where do I get the MCP address? +

https://mcp.tuqo.ru/mcp. It is also shown on the AI connections tab in the panel. Tip: just send the agent the link https://mcp.tuqo.ru; a GET on it returns connection instructions.

Connect another AI