mcp-prometheus
Related Servers
Alternatives to mcp-prometheus
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables agents to explore dashboards and run their panel queries with template variables resolved, query Prometheus and Loki datasources, and read alerts, silences and annotations across Grafana's sources in a context-friendly, read-only-by-default form, with write tools available only when explicitly enabled.1440 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables read-only access to Percona Monitoring and Management 2.x through PromQL metric queries and Query Analytics, so clients can list monitored databases, surface the slowest queries, inspect query details, and run validated SELECT queries against QAN's ClickHouse data. TLS verification, input validation, and Viewer-role tokens keep access strictly observational.32 PyPI3MIT
- AlicenseCqualityDmaintenanceExecutes constrained, read-only Prometheus queries for instant metrics, active alerts, and target health, with bounded resource usage and audit records.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to discover and investigate logs and metrics in the OpenObserve open source edition through read-only tools for stream inspection, SQL log searches, field-value lookups, context queries, and PromQL metric queries. It exposes no tools that modify data or configuration, relying on authenticated OpenObserve user permissions as the real authorization boundary.1MIT
- AlicenseAqualityBmaintenanceEnables read-only querying and exploration of Grafana Loki logs and LogQL metrics, including labels, fields, volume, stats, patterns, rules, and contextual log retrieval, with responses shaped for context windows.1438 npmMIT

wallras-mcpofficial
AlicenseCqualityBmaintenanceEnables AI agents to check drift, read requests and agent runs, work the review queue, fetch prompts, and run regression sets, with read-only access unless writes are explicitly enabled.22MIT
TDQS
Scored across 12 tools
Each tool maps to a distinct Prometheus resource or action, and descriptions explicitly cross-reference each other (e.g. query vs query_range, list_metrics vs describe_metric, list_labels vs describe_metric) to steer selection. The only mild overlaps are the metadata cluster (list_metrics/describe_metric/list_labels/list_label_values) and the catch-all prometheus_request, but each has stated guidance on when to prefer it.
All twelve tools share a prometheus_ prefix and snake_case, with a mostly verb_noun pattern (query_range, list_alerts, describe_metric, get_tsdb_status, list_label_values). A few drop the verb (query, request, auth_status), which is a minor but readable deviation.
Twelve tools is well within the ideal 3-15 range and each one covers a distinct slice of Prometheus's read API (query, metadata, alerts, rules, targets, TSDB, connectivity). Nothing feels padded or redundant.
Core read workflows are fully covered: instant and range queries, metric/label discovery, alerts, rules, scrape health, cardinality, and instance identity. Minor gaps remain (no dedicated /api/v1/series or exemplars wrapper, config/flags only partially surfaced via auth_status), but the prometheus_request escape hatch lets an agent reach them.