tuqo
SDK · tqk_ key in a header

Tuqo in GigaChat / GigaChain

GigaChat is connected through your agent's code, for example on GigaChain: the Tuqo tools are available as an MCP server. Start an MCP client with the Tuqo address and an authorization header, and the agent can create sites and deploy them.

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

Connect an MCP client

In the agent code, point an HTTP MCP server at the Tuqo address.

3

Pass the header

Authorization: Bearer tqk_… in the MCP client headers (example below).

4

Call the tools

The GigaChat agent calls create_site and deploy_files like any other tools.

# pseudocode of an MCP client in your agent
mcp_server = {
    "url": "https://mcp.tuqo.ru/mcp",
    "headers": {"Authorization": "Bearer tqk_xxx_yyy"},
}
# register the server's tools in your GigaChain agent

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

GigaChat (GigaChain) + Tuqo: frequently asked

Is there a ready-made GigaChat connector? +

Tuqo serves standard MCP over HTTP: connect it with any MCP client in your stack, GigaChain or your own.

Do I need OAuth? +

No. In agent code a tqk_ key in a header is simpler.

What access does the key have? +

It is set when the key is created. Deploys need editor or full access.

Connect another AI