Getting started
Zeqqat is a package your MCP client runs. It exposes declared workflows as MCP tools, so an agent calls one tool instead of rediscovering a procedure across twenty.
Install
One command. It finds Claude Code, Cursor, Hermes, and OpenClaw, writes the config, installs the onboarding skill, and signs you in through your browser.
npx @zeqqat/mcp initIt never starts or restarts a harness. Open the one you want to use afterwards, and note that a harness reads its MCP config at startup, so an already-running one needs a restart.
Or by hand
The entry init writes. stdio only. Your client may nest it differently — OpenClaw puts it under mcp.servers, Hermes uses YAML under mcp_servers.
{
"mcpServers": {
"zeqqat": { "command": "npx", "args": ["-y", "@zeqqat/mcp"] }
}
}Pull a published workflow
Browse the registry, then pull by name. Connectors it needs come with it.
npx @zeqqat/mcp pull gaita/migrate-postgresCredentials stay yours
A published connector may only reference environment variables — the registry refuses a literal secret at publish time. Values are read from your environment when the workflow runs and go straight to the service that issued them. Nothing routes through this server, and there is no vault.
Publish your own
Publishing is a CLI operation, not a form on this site — a workflow is a file you version with your code. init already signed you in; if you skipped that, run login with no argument and approve the code in your browser.
npx @zeqqat/mcp loginnpx @zeqqat/mcp publish my-workflowFor CI, where there is no browser, mint a token at Settings → Tokens and pass it: npx @zeqqat/mcp login <token>.
Versions are immutable: republishing the same one is refused, so use --version to publish a new one. --private makes a record only you can read.
What gets reported
A workflow pulled from this registry reports six fields per run — which record ran, the outcome, how long it took, which step failed, and an anonymous install id. Never your inputs, hostnames, database names or error text. That is where a publisher’s run counts come from. A workflow you wrote yourself reports nothing at all, ever. ZEQQAT_NO_REPORT=1 turns it off entirely.
Full reference
Every command, flag and environment variable is in the package README, which ships with the version you installed — github.com/zeqqat/mcp.