Skip to main content
Glama
Germain-D

Pulsar MCP Server

by Germain-D

Related Servers

Alternatives to Pulsar MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with InfluxDB v3 (Core/Enterprise/Cloud Dedicated) through MCP clients. Supports database management, data querying and writing, schema inspection, and token administration operations.
      738 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-powered MCP clients to interact with data lakehouse components including Kafka, Flink, and Trino/Iceberg for managing topics, jobs, catalogs, and executing queries.
      2
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with Apache Flink clusters via the SQL Gateway, allowing query execution, session management, and job control through MCP tools.
      30 PyPI
      8
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables clients to interact with PipesHub data and functionality through MCP, including chat, search, record retrieval, directory browsing, sources, and agents.
      7
      1,329 npm
      6
      Apache 2.0
    • 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
      68 npm
      1
      MIT
    • 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

    TDQS

    A3.6/5.0

    Scored across 10 tools

    Disambiguation5/5

    All tools have clearly distinct purposes. The slight overlap between 'pulsar_all_connectors' and 'pulsar_list_connectors' is resolved by descriptions: one returns all connectors organized by type, the other lists connectors of a specified type.

    Naming Consistency5/5

    All tool names follow the consistent pattern 'pulsar_<verb>_<noun>' (e.g., create_topic, list_connectors). The naming is uniform and predictable, aiding agent selection.

    Tool Count5/5

    With 10 tools, the server is well-scoped for a Pulsar cluster management interface. Each tool serves a necessary function without redundancy.

    Completeness4/5

    The tool set covers core topic operations (CRUD, publish, consume, stats) and connector inspection. However, it lacks connector creation/deletion, which may be needed for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues