Kafka MCP Server

Created By
Joel-hansona year ago
This project provides a **Model Context Protocol (MCP)** server that enables interaction with a Kafka cluster via standard tool-based interfaces. It exposes Kafka operations like producing messages, consuming, listing topics, and more — all accessible through Claude Desktop or any MCP-compatible client.
Overview

What is Kafka MCP Server?

Kafka MCP Server is a Model Context Protocol (MCP) server that facilitates interaction with a Kafka cluster through standard tool-based interfaces, allowing users to perform operations such as producing messages, consuming messages, and listing topics.

How to use Kafka MCP Server?

To use Kafka MCP Server, clone the repository, set up a Python environment, and start the server. You can then connect to Kafka and perform various operations using the provided tools.

Key features of Kafka MCP Server?

  • List Kafka topics
  • Create and delete topics
  • Produce messages
  • Comprehensive error handling
  • Extensible for additional Kafka operations

Use cases of Kafka MCP Server?

  1. Managing Kafka topics efficiently.
  2. Integrating Kafka operations into applications via MCP.
  3. Facilitating development and testing of Kafka-based applications.

FAQ from Kafka MCP Server?

  • What operations can I perform with Kafka MCP Server?

You can list, create, delete, and inspect Kafka topics, as well as manage connections and configurations.

  • Is Kafka MCP Server easy to set up?

Yes! The setup involves cloning the repository and configuring a Python environment.

  • Can I extend the functionality of Kafka MCP Server?

Yes! The server is designed to be extensible, allowing you to add more Kafka operations as needed.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Joel-hanson
Star
0
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago