Skip to main content
Glama
aywengo

MCP Kafka Schema Reg

by aywengo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MCP Kafka Schema Reg

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

    • 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 REST API Server

      vinaykp
      F
      license
      Not graded
      quality
      D
      maintenance
      A server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.
      -

    • mcp-openapi-schema

      hannesj
      A
      license
      Not graded
      quality
      F
      maintenance
      A MCP server that exposes OpenAPI schema information to LLMs like Claude. This server allows an LLM to explore and understand large OpenAPI schemas through a set of specialized tools, without needing to load the whole schema into the context
      163 npm
      49
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and the get/list/count/test verbs help separate workflows. The few potentially confusable pairs, such as test_registry_connection vs test_all_registries or get_schema_by_id vs get_subjects_by_schema_id, are still described clearly enough to avoid frequent mis-selection.

    Naming Consistency4/5

    Tool names mostly follow a consistent lowercase snake_case verb_noun pattern with clear prefixes like get_, list_, count_, test_, and export_. The bare 'ping' tool and the awkwardly suffixed 'get_mcp_compliance_status_tool' are minor deviations from an otherwise predictable scheme.

    Tool Count2/5

    With 28 tools, the set is overloaded for its apparent scope. Many read operations are backward-compatibility wrappers for resources, and the extra count/export/meta tools inflate the surface beyond what an agent needs for normal Kafka Schema Registry workflows.

    Completeness2/5

    The tool set is overwhelmingly read-focused, covering schemas, subjects, contexts, configs, modes, and counts, but it lacks core mutation operations such as delete subject, delete schema version, update compatibility, and set mode. Only register_schema and create_context provide any write coverage, leaving obvious lifecycle gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources