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 分