
Mcp Debezium
io.github.dockndevaiPublished by GitHub account dockndevaiv0.3.0Updated Nov 17, 2026
Debezium / Kafka Connect CDC connector management for AI agents — governed, secret-safe.
Overview
MCP server for monitoring and managing Debezium CDC connectors through the Kafka Connect REST API, with read-only defaults and credential redaction.
- What you can do
- Inspect the Connect cluster, list connectors and plugins, and read a connector's config, status with failed-task traces, and topics
- Create and update connector configs, pause and resume connectors, and restart a connector or a single task
- Delete connectors in admin mode when deletion is explicitly enabled
- Redact secret-shaped config values and log guarded operations to an audit trail
- Gate destructive actions behind human approval prompts and dry-run previews
- When to use it
- Useful when you run Debezium or Kafka Connect and want an assistant to answer questions about failing connectors, show redacted configs, or perform restarts and lifecycle changes under a controlled access mode.
- Requirements
- Runs locally via npx from the npm package, so Node.js is needed. Requires CONNECT_URL pointing at the Kafka Connect REST API. Optional variables set the access mode (DEBEZIUM_MODE, default read-only), connector allowlist, protected connectors, delete gating, dry-run and audit logging. Network access to the Connect endpoint is required.
Installation
In SourceWeft
- Open Mcp Debezium in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-debezium
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.passwordand 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
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)
Claude Desktop · Cursor · Windsurf — same block in claude_desktop_config.json, .cursor/mcp.json, or ~/.codeium/windsurf/mcp_config.json:
OpenAI Codex CLI — in ~/.codex/config.toml:
VS Code (GitHub Copilot, Agent mode) — in .vscode/mcp.json:
Example prompts
- "Which connectors are FAILED, and why?"
- "Restart the failed task on
pg-orders." (needsread-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:
Develop
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
Source: README.md at commit 3f10c15
Tools
0Version history
2- v0.3.0LatestSep 29, 2026
- v0.2.2Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts