Mcp Debezium

io.github.dockndevai由 GitHub 帳號 dockndevai 發布v0.3.0更新於 Nov 17, 2026

Debezium / Kafka Connect CDC connector management for AI agents — governed, secret-safe.

概覽

AI 產生的概覽

透過 Kafka Connect REST API 監控與管理 Debezium CDC 連接器的 MCP 伺服器,預設唯讀並自動遮蔽憑證。

可以做什麼
  • 檢視 Connect 叢集資訊、連接器與外掛清單,以及單一連接器的設定、狀態(含失敗任務追蹤)與主題
  • 建立與更新連接器設定,暫停、恢復連接器,重新啟動連接器或單一任務
  • 在管理員模式且明確允許時刪除連接器
  • 遮蔽設定中的機密值,並將受保護操作寫入稽核日誌
  • 對破壞性操作要求人工確認,並支援試執行預覽
適用情境
適合執行 Debezium 或 Kafka Connect 的團隊,想讓助理排查失敗的連接器、查看遮蔽後的設定,或在受控權限模式下執行重新啟動與生命週期變更。
執行需求
透過 npx 從 npm 套件在本機執行,需要 Node.js。需設定 CONNECT_URL 指向 Kafka Connect REST API。選用變數可設定存取模式(DEBEZIUM_MODE,預設唯讀)、連接器允許清單、受保護連接器、刪除開關、試執行與稽核日誌。需要能連線至 Connect 端點的網路。
安裝前請注意
寫入與管理工具會改動正式 CDC 資料流:建立、更新、暫停、恢復、重新啟動與刪除。刪除需同時具備管理員模式與 DEBEZIUM_ALLOW_DELETE。除非確實要變更,否則維持預設唯讀模式,並啟用允許清單、受保護連接器與人工核准。連接器設定可能含資料庫憑證;回傳值會遮蔽,但伺服器本身仍以 Connect 端點授予的權限存取。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Mcp Debezium,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

mcp-debezium

[CI] [License: MIT] [npm]

A Model Context Protocol server for Debezium (via the Kafka Connect REST API). It lets an MCP-capable client (Claude Desktop, Claude Code, etc.) monitor and manage change-data-capture connectors — status, config, restarts, lifecycle — with behaviour controlled entirely by flags.

Safe by default: it starts read-only, can be scoped to an allowlist of connectors, protects critical connectors from mutation, redacts credentials in connector configs, and gates deletion behind an explicit opt-in.

Features

  • Monitoring — worker/cluster info, connector list, plugins, per-connector config, status (with failed-task traces), and topics.
  • Management — create/update, pause/resume, restart connector or a single task.
  • Lifecycle — delete connectors (admin).
  • Access modes — read-only → read-write → admin, layered so a mode never exposes tools above its level.
  • Credential redaction — database.password and other secret-shaped config values are replaced with ***REDACTED*** before results are returned.
  • Security flags — connector allowlist, protected connectors, delete gating, dry-run, and JSON audit logging (see below).

Security model

ConcernFlagDefaultEffect
What can the server do?DEBEZIUM_MODEread-onlyread-only exposes monitoring only; read-write adds lifecycle management; admin adds delete. Tools above the mode are never registered.
Which connectors are in scope?DEBEZIUM_CONNECTOR_ALLOWLIST(all)When set, operations on other connectors are refused.
Which connectors are read-only forever?DEBEZIUM_PROTECTED_CONNECTORS(none)Inspectable but never paused/reconfigured/deleted.
Can it delete?DEBEZIUM_ALLOW_DELETEfalsedelete_connector needs this and admin mode.
Preview without touching ConnectDEBEZIUM_DRY_RUNfalseWrite/admin tools validate + log intent, then return.
Audit trailDEBEZIUM_AUDIT_LOGtrueEmits a JSON line to stderr per guarded operation.
Interactive confirmation(automatic)—Destructive & high-impact actions prompt the human to approve via MCP elicitation before running. The prompt shows the tool, the exact (secret-redacted) arguments and a fingerprint (for update_connector_config a redacted current → new config diff, for create_connector the redacted config); the target's version is pinned across the prompt and the action is refused if it changed; a prompt nobody answers is a refusal.
Require a humanDEBEZIUM_REQUIRE_HUMAN_APPROVALfalseWhen true, delete_connector, create_connector and update_connector_config are refused if the client cannot elicit (instead of falling back to the *_ALLOW_* gate alone).
Credential redaction(always on)—Secret-shaped config values are redacted before return.

Tools

Read (read-only+): cluster_info, list_connectors, list_connector_plugins, get_connector, get_connector_config, get_connector_status, get_connector_topics

Write (read-write+): create_connector, update_connector_config, pause_connector, resume_connector, restart_connector, restart_task

Admin (admin): delete_connector (needs DEBEZIUM_ALLOW_DELETE)

Quickstart — add to your agent

Published on npm as @dockndevai/mcp-debezium. No clone or build needed — your MCP client runs it on demand with npx. Start in read-only mode; see .env.example for every variable and docs/CLIENTS.md for the full per-client guide.

Claude Code (CLI)

bash
claude mcp add debezium -e CONNECT_URL="http://localhost:8083" -e DEBEZIUM_MODE="read-only" -- npx -y @dockndevai/mcp-debezium

Claude Desktop · Cursor · Windsurf — same block in claude_desktop_config.json, .cursor/mcp.json, or ~/.codeium/windsurf/mcp_config.json:

json
{  "mcpServers": {    "debezium": {      "command": "npx",      "args": [        "-y",        "@dockndevai/mcp-debezium"      ],      "env": {        "CONNECT_URL": "http://localhost:8083",        "DEBEZIUM_MODE": "read-only"      }    }  }}

OpenAI Codex CLI — in ~/.codex/config.toml:

toml
[mcp_servers.debezium]command = "npx"args = ["-y", "@dockndevai/mcp-debezium"]env = { CONNECT_URL = "http://localhost:8083", DEBEZIUM_MODE = "read-only" }

VS Code (GitHub Copilot, Agent mode) — in .vscode/mcp.json:

json
{  "servers": {    "debezium": {      "type": "stdio",      "command": "npx",      "args": [        "-y",        "@dockndevai/mcp-debezium"      ],      "env": {        "CONNECT_URL": "http://localhost:8083",        "DEBEZIUM_MODE": "read-only"      }    }  }}

Example prompts

  • "Which connectors are FAILED, and why?"
  • "Restart the failed task on pg-orders." (needs read-write)
  • "Show the config for mysql-inventory." (credentials come back redacted)

Run from source (development)

Prefer the published package above. To run from a clone:

bash
npm installnpm run buildnode dist/index.js   # with the environment variables set

Develop

bash
npm run devnpm test          # security policy + config redactionnpm run typecheck

Publishing

This server ships a server.json for the official MCP registry and an mcpName for npm ownership validation. See PUBLISHING.md for publishing to npm and listing on the MCP registry, Smithery, Glama, Cursor, and PulseMCP.

License

MIT

來源:README.md,提交 3f10c15

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

2
  1. v0.3.0最新Sep 29, 2026
  2. v0.2.2Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分