prometheus-mcp
Related Servers
Alternatives to prometheus-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityFmaintenanceA Model Context Protocol server that enables AI assistants to query Prometheus metrics, discover available data, and analyze system performance through natural language interactions.562 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI assistants to query and analyze Prometheus metrics through PromQL, with support for metric discovery and authentication.MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI agents to interact directly with Prometheus metrics data through natural language queries.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query Prometheus metrics, monitor alerts, and analyze system health through read-only access to your Prometheus server with built-in query safety and optional AI-powered metric analysis.MIT

prometheus-mcp-serverofficial
AlicenseNot gradedqualityBmaintenanceMCP server that lets LLMs interact with a running Prometheus instance via its API, enabling metric analysis, PromQL queries, and rule/target inspection. It also provides embedded documentation and guided runbooks for common Prometheus tasks.109Apache 2.0- AlicenseNot gradedqualityDmaintenanceA lean MCP server that provides LLM agents with transparent access to multiple Prometheus instances for metrics analysis and SRE operations.4GPL 2.0
TDQS
Scored across 10 tools
Most tools target distinct Prometheus resources, and the descriptions make the boundaries clear. The main ambiguities are list_targets vs scrape_pool_targets and list_labels vs label_values, which are related but scope-differentiated.
All tool names share the prometheus_ prefix and snake_case, but the pattern is mixed: some use list_* verbs, others use bare nouns like runtime_info or query_range. This is readable but not a consistent verb_noun convention.
Ten tools is well-scoped for a Prometheus MCP server, covering querying, metadata, targets, and informational endpoints without unnecessary bloat.
The surface covers core query, range query, metric metadata, label values, and target discovery. Missing alerting/rules or series endpoints, but the main monitoring workflows are well supported.