Back to Browse

mcp-debezium MCP Server

by dockndevai
Data & AnalyticsModerate5.2LocalNew
Free

Monitor & manage Debezium CDC connectors for AI agents.

About

MCP server for Debezium / Kafka Connect. Monitor and manage change-data-capture connectors — status (with failed-task traces), config, pause/resume, restart, and lifecycle — with read-only / read-write / admin access modes, connector allowlists, protected connectors, delete gating, and always-on redaction of credentials in connector configs.

Security Report

5.2
Moderate5.2Moderate Risk

This is a well-designed MCP server with strong security fundamentals. Authentication is delegated to the Kafka Connect REST API (Basic Auth), authorization is properly layered via access modes with runtime policy enforcement, and sensitive data is redacted before returning to the user. Code quality is good with proper input validation, clear separation of concerns, and comprehensive unit tests. Minor areas for improvement include broader error handling and additional logging around auth failures, but these do not materially impact security posture. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.

7 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "mcp-debezium": {
      "args": [
        "-y",
        "@dockndevai/mcp-debezium"
      ],
      "command": "npx"
    }
  }
}

Getting Started

Once installed, try these example prompts and explore these capabilities:

  • 1"Which connectors are FAILED, and why?"
  • 2"Show the status of connector pg-orders"
  • 3"Show the config for mysql-inventory" (credentials come back redacted)
  • 4Tool: restart_task — restart a failed task (requires read-write mode)

Documentation

View on GitHub

From the project's GitHub README.

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 modesread-onlyread-writeadmin, layered so a mode never exposes tools above its level.
  • Credential redactiondatabase.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.
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)

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:

{
  "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:

[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:

{
  "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:

npm install
npm run build
node dist/index.js   # with the environment variables set

Develop

npm run dev
npm test          # security policy + config redaction
npm 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

Reviews

No reviews yet

Be the first to review this server!

mcp-debezium MCP Server - Monitor & manage Debezium CDC connectors for AI agents. | MCP Marketplace