Skip to main content
Glama
BrooksIan

SSM MCP Server

by BrooksIan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to SSM MCP Server

No user-submitted related servers found.

    Related Servers

    • Kafka MCP Server

      aswinayyolath
      F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server for Apache Kafka operations, enabling seamless integration with Claude Desktop and other MCP clients for cluster management, topic operations, and message streaming.
      2
      -

    • 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-server-kafka

      atengk
      A
      license
      A
      quality
      A
      maintenance
      Enables large language models and AI agents to securely and efficiently interact with Apache Kafka clusters through the Model Context Protocol.
      11
      65 PyPI
      Apache 2.0
    • fontem-mcp-server by fontem-eu

      fontem-mcp-serverofficial

      fontem-eu
      A
      license
      Not graded
      quality
      B
      maintenance
      A Model Context Protocol server that surfaces Fontem entities and queries to Claude via standard MCP tools.
      Apache 2.0

    • MCP cldkctl Server

      raffelprama
      A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server that provides access to Cloudeka's cldkctl CLI functionality through Claude Desktop, Cursor, and other MCP-compatible clients.
      100
      1
      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.4/5.0

    Scored across 78 tools

    Disambiguation2/5

    Many tools have overlapping purposes, e.g., get_broker vs get_broker_details vs get_broker_metrics, and get_topic_info vs get_topic_description. The abundance of similarly named tools makes it difficult for an agent to select the correct one without confusion.

    Naming Consistency3/5

    Most tools follow a get_<noun> pattern, but there are inconsistencies like get_admin_brokers vs get_broker, and variations like get_all_consumer_info vs get_consumer_info. Plural vs singular usage is inconsistent.

    Tool Count2/5

    78 tools is excessive for a server focused on monitoring and management. The granularity creates unnecessary complexity, with many tools covering similar concerns.

    Completeness3/5

    The set covers a wide range of read operations across brokers, topics, consumer groups, connectors, and alerts. However, it lacks mutation tools for most entities (e.g., create/update/delete topics or connectors), leaving notable gaps in lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources