How Zeqqat works.
How Zeqqat works
Zeqqat is an MCP gateway. One connection URL gives an agent access to the integrations (tool sets such as Dokploy) a person connected, on the instances (servers) they added. The agent sees eight built-in tools: zeqqat_import adds an app from a link to its OpenAPI spec, zeqqat_search finds tools, zeqqat_describe shows one tool's inputs and outputs, zeqqat_run calls a tool on one instance, zeqqat_whoami returns the context, zeqqat_policy shows what is allowed on each instance, zeqqat_secret creates a random secret you never see, zeqqat_docs answers questions about Zeqqat. Normal flow: search for a task (for example deploy), describe the tool you picked, then run it with the operationId, the instance name from the context, and inputs matching the tool's input schema. Search, describe and run each need a reason: one line saying what the user asked you to do. Use exactly the same wording on every call you make for one request; Zeqqat groups those calls together in the activity log people use to audit the connection. A call without a reason is refused.
The context object
Every tool result starts with a context object: account (the account that owns this connection), workspace, connection name, the integrations this connection reaches with their instances, and a notice. account has a username and a type: personal (one person, the only owner) or organization (owned by a group with owners). It is the owner of the connection, not necessarily the person calling. Each integration is named @author/slug, which tells you whose tool set it is, and carries toolCount, how many tools it has. zeqqat_whoami also lists its categories, the kinds of tools it has (for example application, docker, project); search a category to see its tools. Instance names are chosen by the user, for example prod or staging. An integration that is not listed is not connected: tell the user, they can add it in the Zeqqat dashboard.
Next: Using the tools