MCP Prometheus
Related Servers
Alternatives to MCP Prometheus
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for PostgreSQL that enables schema exploration, safe SQL execution, EXPLAIN analysis, health checks, and index recommendations across multiple databases.10111MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI assistants to query and analyze Prometheus metrics through PromQL, with support for metric discovery and authentication.MIT
- FlicenseNot gradedqualityDmaintenanceIn-cluster MCP server for read-only diagnostics of Grafana, Prometheus, Alertmanager, and Loki, enabling metric queries, alert listings, and log queries through Grafana datasource proxies with Kubernetes RBAC authentication.-
- AlicenseNot gradedqualityDmaintenanceUnified MCP server for observability and monitoring, providing tools to query metrics, logs, and traces through Prometheus, Grafana, Loki, and Jaeger.2Mozilla Public 2.0

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.105Apache 2.0- AlicenseNot gradedqualityFmaintenanceAn MCP server that enables Large Language Models to retrieve, analyze, and query metric data from Prometheus databases through pre-defined routes.34MIT
TDQS
Scored across 12 tools
Most tools have distinct purposes, such as get_alerts for fetching alerts and run_check for executing specific checks. However, list_loki_apps, list_loki_environments, and list_loki_hosts are ambiguous without descriptions, potentially causing confusion about their specific functions and differences.
Tool names follow a highly consistent verb_noun pattern throughout, such as list_servers, run_promql, and find_logs. All tools use snake_case without any deviations, making the naming predictable and easy to understand.
With 12 tools, the count is well-suited for a Prometheus monitoring server, covering key operations like listing resources and running queries. It's slightly on the higher side but remains reasonable for the domain, though some tools like the Loki-related ones might be redundant or under-specified.
The toolset provides good coverage for querying and listing operations in Prometheus, including alerts, checks, and servers. However, there are notable gaps, such as missing tools for creating or managing alerts, configuring checks, or handling Loki data beyond listing, which limits full lifecycle management in the monitoring domain.