Zeqqat

Official registry Cloud and DevOps

The MCP gateway for Dokploy: agents deploy and fix apps without holding keys or seeing secrets.

What can you do with Zeqqat?

  • Keys stay out of the model: API keys are encrypted at rest and never returned to an agent.
  • Scrubbed responses: env vars, tokens and private keys are stripped from every response before the model sees it.
  • Permissions per connection: allow reading, creating, editing or deleting, one connection at a time.
  • Policies: allow exactly the tools you list, and share policies with others.
  • Activity log: every request shows who asked, which agent, the reason it gave, what it called and what came back.
  • Teams: organizations, workspaces and roles, so teammates get their own access instead of a shared key.
  • The whole Dokploy API: all 554 endpoints, found by search, so your agent's context isn't flooded with tool definitions.
  • Any API from its OpenAPI spec: paste a link to an app's spec (Stripe, GitHub, your own) and every endpoint becomes a tool under your account, with read, create, edit and delete guessed for each. From the dashboard, from your agent with zeqqat_import, ...

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http zeqqat 'https://zeqqat.com/{org}/mcp/{connection}/{id}'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "zeqqat": {
            "type": "http",
            "url": "https://zeqqat.com/{org}/mcp/{connection}/{id}"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. ✨ Features
  2. 🚀 Getting Started
  3. ⚙️ Configuration
  4. ☁️ Cloud vs Self-hosted
  5. 🛠️ Development
  6. 🤝 Contributing
  7. 🔒 Security
  8. 📄 License

Talk to your Dokploy.

Website · Self-host guide · Agent docs · Blog · Discord

Works with Claude, Claude Code, ChatGPT, Cursor, Gemini and any MCP client.

Zeqqat is the safe, open source MCP for Dokploy, self-hosted or Cloud. Your agent connects to one Zeqqat URL instead of holding your API keys. Zeqqat decides what it may do, makes the call for it, and records everything. Self-host it on your own Dokploy for free, or use the hosted version at zeqqat.com.

✨ Features

  • Keys stay out of the model: API keys are encrypted at rest and never returned to an agent.
  • Scrubbed responses: env vars, tokens and private keys are stripped from every response before the model sees it.
  • Permissions per connection: allow reading, creating, editing or deleting, one connection at a time.
  • Policies: allow exactly the tools you list, and share policies with others.
  • Activity log: every request shows who asked, which agent, the reason it gave, what it called and what came back.
  • Teams: organizations, workspaces and roles, so teammates get their own access instead of a shared key.
  • The whole Dokploy API: all 554 endpoints, found by search, so your agent's context isn't flooded with tool definitions.
  • Any API from its OpenAPI spec: paste a link to an app's spec (Stripe, GitHub, your own) and every endpoint becomes a tool under your account, with read, create, edit and delete guessed for each. From the dashboard, from your agent with zeqqat_import, or with POST /api/integrations/import.
  • Standard OAuth sign-in: agents connect with OAuth 2.1, and each token only works on the connection it was issued for.
  • Self-hosted: one container and Postgres, with migrations applied on startup.

🚀 Getting Started

On Dokploy
  1. Create a Docker Compose service from this repository, or paste docker-compose.yml.
  2. Set the environment variables listed under Configuration below.
  3. In Domains, click Generate for a free address that already points at your server (or use your own domain), and add it to the zeqqat service on port 3000 with HTTPS on. Deploy.
  4. Open that address, create the first account (it owns this Zeqqat), and connect your Dokploy.

The full walkthrough is at zeqqat.com/docs/self-host.

Anywhere with Docker
git clone https://github.com/zeqqat/zeqqat.git
cd zeqqat
cp .env.example .env    # fill in the values
docker compose up -d

To reach it locally on http://localhost:3000, uncomment the ports lines in docker-compose.yml.

Connect an agent

After you connect your Dokploy, Zeqqat gives you a connection URL like https://your-zeqqat-address/you/mcp/deployment/a39f. Add it to your agent as a remote MCP server and sign in when asked. Your agent reaches Dokploy through a few stable tools: zeqqat_search, zeqqat_describe, zeqqat_run, zeqqat_whoami, zeqqat_policy, zeqqat_secret, zeqqat_import and zeqqat_docs.

⚙️ Configuration

VariableRequiredWhat it is
ZEQQAT_PUBLIC_URLyesYour install's URL, the address Dokploy generates for it, or a domain you own
POSTGRES_PASSWORDyesPassword for the bundled Postgres
BETTER_AUTH_SECRETyesSession secret: openssl rand -base64 32
ZEQQAT_ENCRYPTION_KEYyesEncrypts stored API keys: openssl rand -base64 32. Keep it safe, a new key makes stored keys unreadable
ENABLED_AUTH_PROVIDERSnoAny of password, github, google and email, comma separated. Default password: the first account you create owns the install, and everyone else joins with an invite link
GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRETfor GitHub sign-inA GitHub OAuth app with callback <your URL>/api/auth/callback/github
GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRETfor Google sign-inA Google OAuth client with redirect URI <your URL>/api/auth/callback/google
MAIL_FROM plus SMTP_URL or RESEND_API_KEYfor email sign-in, optional with passwordSender address, and how to send: any SMTP server (smtps://user:password@smtp.example.com:465) or a Resend API key. With email, people sign in with a 6-digit code; with password, forgotten-password links go by email (without a mailer, the owner makes them on the Team page)

Every option is documented in .env.example.

Anonymous install ping

So we can tell how many self-hosted installs exist and which versions they run, a self-hosted install sends one small ping to https://zeqqat.com/api/telemetry when it starts and once a day after that. The ping is exactly this, and nothing else:

{ "installId": "a random UUID made on first start", "version": "0.2.1" }

No IP address, hostname, users, emails, instances, API keys, connections or tool calls are ever sent, and zeqqat.com doesn't store your IP. The code is in lib/telemetry.ts.

To turn it off, set ZEQQAT_TELEMETRY=0 (DO_NOT_TRACK=1 works too) and restart.

☁️ Cloud vs Self-hosted

Zeqqat CloudSelf-hosted
CostFree while in betaFree and open source
SetupSign up at zeqqat.comOne Docker Compose service on your Dokploy
Where your keys liveEncrypted on zeqqat.comEncrypted on your own server
FeaturesEverythingEverything
UpdatesAutomaticPull a new image tag

🛠️ Development

You need Node 22, pnpm 9 and Postgres.

pnpm install
cp .env.example .env
pnpm dev

pnpm check runs typecheck, lint and tests. AGENTS.md explains the architecture. Built with Next.js, Postgres, Drizzle and Better Auth.

Contributors 🤝

🤝 Contributing

Read the Contributing Guide before opening a pull request.

🔒 Security

Please report vulnerabilities privately. See SECURITY.md.

📄 License

Apache License 2.0


Frequently asked questions

What is Zeqqat?

The MCP gateway for Dokploy: agents deploy and fix apps without holding keys or seeing secrets.

How do I install Zeqqat?

It runs as a remote server. In Claude Code: claude mcp add --transport http zeqqat 'https://zeqqat.com/{org}/mcp/{connection}/{id}'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Zeqqat need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Zeqqat open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains Zeqqat?

It is published by zeqqat. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.