Zeqqat

io.github.zeqqat由 GitHub 账号 zeqqat 发布v0.2.8更新于 Nov 8, 2026

Open source MCP gateway: agents call your APIs without holding keys or seeing secrets.

已验证Streamable HTTP可网页运行云端与基础设施开发者工具安全与监控

概览

AI 生成的概览

开源 MCP 网关,让 AI 代理通过一个 URL 调用你的 API 和 MCP,而无需持有密钥或看到机密信息。

可以做什么
  • 搜索、查看说明并执行经网关暴露的 API 端点,包括完整的 Dokploy API
  • 查看当前身份,并管理某个连接的权限与策略
  • 管理已保存的密钥,且不向代理暴露密钥内容
  • 从 OpenAPI 规范导入任意 API,使每个端点成为一个工具
  • 在代理内查阅网关文档
适用场景
当你希望代理操作你的 API 或 Dokploy 部署,但不想把原始 API 密钥交给它,并需要按连接设置权限、策略以及记录调用原因的活动日志时适用。
运行要求
远程端点 zeqqat.com(托管版,测试期免费),或自建 Docker Compose 加 Postgres。自建需配置 ZEQQAT_PUBLIC_URL、POSTGRES_PASSWORD、BETTER_AUTH_SECRET、ZEQQAT_ENCRYPTION_KEY 和 ENABLED_AUTH_PROVIDERS,以及用于登录的 GitHub 或 Google OAuth 客户端凭据。代理通过 OAuth 2.1 连接。
安装前请注意
网关会保存你的 API 密钥,并用 ZEQQAT_ENCRYPTION_KEY 加密;该密钥丢失或更换会导致已存密钥无法读取。代理可被授予创建、编辑和删除权限,使用前请检查每个连接的权限与策略。自建实例每天会向 zeqqat.com 发送匿名安装 ping,除非设置 ZEQQAT_TELEMETRY=0 或 DO_NOT_TRACK=1。托管版的密钥存放在 zeqqat.com 上。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Zeqqat,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

[Zeqqat]

[License] [Release] [Docker image] [Stars]

Give AI access to your APIs and MCPs. Minus the risk.

Website · Self-host guide · Agent docs · Blog

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


Zeqqat is an open source MCP gateway between AI agents and your APIs. 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. Add your domain to the zeqqat service on port 3000 and deploy.
  4. Open your domain, sign in, and connect your Dokploy.

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

Anywhere with Docker

bash
git clone https://github.com/zeqqat/zeqqat.gitcd zeqqatcp .env.example .env    # fill in the valuesdocker 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://zeqqat.example.com/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, for example https://zeqqat.example.com
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_PROVIDERSyesgithub, google, or both, comma separated
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

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:

json
{ "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.

bash
pnpm installcp .env.example .envpnpm dev

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

Contributors 🤝

[Contributors]

🤝 Contributing

Read the Contributing Guide before opening a pull request.

🔒 Security

Please report vulnerabilities privately. See SECURITY.md.

📄 License

Apache License 2.0


来源:README.md,提交 f4583be

工具

0
SourceWeft 尚未读取此服务器的工具。

版本历史

1
  1. v0.2.8最新Nov 8, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分