SSM MCP Server
Related Servers
Alternatives to SSM MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA 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-
- FlicenseBqualityDmaintenanceA Model Context Protocol server that enables users to kickoff and monitor deployed CrewAI workflows through Claude Desktop.259-

fontem-mcp-serverofficial
AlicenseNot gradedqualityBmaintenanceA Model Context Protocol server that surfaces Fontem entities and queries to Claude via standard MCP tools.Apache 2.0- AlicenseCqualityDmaintenanceA Model Context Protocol server that provides access to Cloudeka's cldkctl CLI functionality through Claude Desktop, Cursor, and other MCP-compatible clients.1001MIT
- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol server enabling Claude to maintain user context through Apache Unomi profile management.112 npm10Apache 2.0
- AlicenseAqualityFmaintenanceModel Context Protocol (MCP) server implementation that enables Claude Desktop to interact with Google's Gemini AI models.659 npm261MIT
TDQS
Scored across 78 tools
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.
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.
78 tools is excessive for a server focused on monitoring and management. The granularity creates unnecessary complexity, with many tools covering similar concerns.
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.