Skip to main content
Glama
confluentinc

mcp-confluent

Official
by confluentinc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-confluent

No user-submitted related servers found.

    Related Servers

    • Kafka MCP Server

      jilanisayyad
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables interaction with Kafka clusters to manage topics, monitor consumer groups, and stream messages. It provides a comprehensive suite of tools for broker metadata inspection and local Kafka user management.
      MIT

    • kafka-mcp

      wklee610
      A
      license
      B
      quality
      B
      maintenance
      MCP server for Apache Kafka that allows LLM agents to inspect topics, consumer groups, and safely manage offsets (reset, rewind).
      19
      13
      Apache 2.0

    • mcp-kafka

      dockndevai
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP-capable clients to monitor and manage Apache Kafka clusters, including topics, partitions, configs, and consumer groups with lag, while enforcing configurable security modes, topic allowlists, protected topics, and audit logging.
      6
      439
      1
      MIT

    • Kafka MCP Enterprise Server

      vaquarkhan
      A
      license
      C
      quality
      B
      maintenance
      Reference implementation of KIP-1318, a secure Model Context Protocol server for Apache Kafka that enables AI agents to interact with Kafka clusters through governed tools and resources.
      11
      2
      Apache 2.0

    • MCP Kafka

      williajm
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that enables AI assistants to safely interact with Apache Kafka clusters, providing tools for topic management, message operations, consumer groups, and cluster information.
      3
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific resources (e.g., topics, connectors, tags, Flink statements), but there is some overlap between list-topics, search-topics-by-name, and search-topics-by-tag which could cause confusion in selection. The descriptions help clarify the differences, but the boundaries between listing and searching topics are not perfectly clear.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (e.g., create-topics, delete-connector, list-clusters) with minor deviations like add-tags-to-topic (which uses 'add' instead of 'create' or 'assign') and remove-tag-from-entity (using 'remove' instead of 'delete'). Overall, the pattern is predictable and readable, with only a few tools slightly deviating from the standard convention.

    Tool Count3/5

    With 24 tools, the count is on the higher side for a single server, bordering on heavy, but it covers multiple domains within Confluent Cloud (Kafka, connectors, tags, Flink, schemas). While comprehensive, it might feel overwhelming or overly complex for agents, suggesting a slight mismatch in scope versus tool density.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for the domains it addresses, including topics (create, alter, list, search, delete), connectors (create, list, read, delete), tags (create, list, add, remove, delete), and Flink statements (create, list, read, delete). There are no obvious gaps, and agents can perform full operations without dead ends in these areas.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources