Tuqo in Zed
Zed connects MCP servers as context servers over HTTP with headers. Create a project key in the panel at app.tuqo.dev, add Tuqo to the context servers settings with an authorization header, and manage sites with 52 Tuqo tools right from the editor.
Create a project key
In the Tuqo panel at app.tuqo.dev → project → API keys → create. Format tqk_…, shown once.
Open the settings
In Zed: settings.json, the context_servers block (your client's MCP settings).
Add the Tuqo server
The MCP address and an Authorization: Bearer tqk_… header (example below).
Deploy from the assistant
Ask it to create a site and publish it: Zed calls create_site and deploy_files and returns the link.
{
"context_servers": {
"tuqo": {
"url": "https://mcp.tuqo.ru/mcp",
"headers": { "Authorization": "Bearer tqk_xxx_yyy" }
}
}
}The Tuqo panel is in English, and the labels here are the ones it shows.
Zed + Tuqo: frequently asked
What exactly is Zed's config format? +
Tuqo serves standard HTTP MCP: put it into your client's context servers or MCP settings as the MCP address plus an Authorization header.
Do I need OAuth? +
No. In an editor a tqk_ key in a header is simpler. OAuth is for web chats that cannot store a key.
What is available after connecting? +
All 52 Tuqo tools: creating sites, deploy_files and deploy_site, domains, deploy rollbacks, gated access and reading form submissions.