Kafka MCP Server

Created By
lovablefowla year ago
A Model Context Protocol (MCP) server for Apache Kafka implemented in Go, leveraging franz-go and mcp-go. kafka, mcp, mcp-server
Overview

What is Kafka MCP Server?

Kafka MCP Server is a Model Context Protocol (MCP) server for Apache Kafka, implemented in Go, which allows LLM models to perform common Kafka operations through a standardized interface.

How to use Kafka MCP Server?

To use Kafka MCP Server, install it via Homebrew or build it from source. Configure your MCP-compatible clients to connect to the server using the provided settings.

Key features of Kafka MCP Server?

  • Integration with Kafka for producing and consuming messages.
  • Security features including SASL and TLS authentication.
  • Error handling with meaningful feedback.
  • Pre-configured prompts for common Kafka operations.
  • Compatibility with MCP-compatible LLM models.

Use cases of Kafka MCP Server?

  1. Enabling AI applications to interact with Kafka seamlessly.
  2. Monitoring and managing Kafka topics and consumer groups.
  3. Performing diagnostics and health checks on Kafka clusters.

FAQ from Kafka MCP Server?

  • Can Kafka MCP Server work with any Kafka cluster?

Yes, it can connect to any Kafka cluster as long as the configuration is set correctly.

  • Is Kafka MCP Server secure?

Yes, it supports SASL and TLS for secure communication.

  • How can I contribute to Kafka MCP Server?

Contributions are welcome via Pull Requests on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
lovablefowl
Star
11
Language
Go
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago