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 分