Skip to content
Agentmart
Submit a tool

Prometheus MCP

Prometheus MCP — query metrics, inspect alerts, and explore scrape targets (read-only).

Connector by mshegolev · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/mshegolev-prometheus-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Prometheus MCP — query metrics, inspect alerts, and explore scrape targets (read-only).

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
22 read · 0 write · 0 deleteRead-only
Secrets
2 (API keys, tokens or passwords)
Install scripts
Not scanned yet
Runs as
Python package

Tools by what they do 22

Read from the source code; the running server may list different tools.

Read 22 · Look things up without changing anything.

  • alertmanager_get_status
  • alertmanager_list_alert_groups
  • alertmanager_list_alerts
  • alertmanager_list_silences
  • correlate_alerts_across_instances
  • detect_cascading_alerts
  • federation_analyze_alerts
  • federation_list_instances
  • group_alerts_by_service
  • prometheus_get_build_info
  • prometheus_get_cardinality
  • prometheus_get_metric_metadata
Show 10 more tools
  • prometheus_get_runtime_info
  • prometheus_health_check
  • prometheus_list_alerts
  • prometheus_list_label_values
  • prometheus_list_metrics
  • prometheus_list_rules
  • prometheus_list_targets
  • prometheus_map_service_dependencies
  • prometheus_query
  • prometheus_query_range

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • PROMETHEUS_PASSWORD
  • PROMETHEUS_TOKEN

Other settings (environment variables or headers).

  • PROMETHEUS_SSL_VERIFY
  • PROMETHEUS_URL
  • PROMETHEUS_USERNAME

Tools (22)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • alertmanager_get_statusAM Statusread-only

    Get Alertmanager cluster status, version, and config. Wraps ``GET /api/v2/status``. Returns cluster state (ready/settling), version info, uptime, and the raw configuration YAML. Examples: - Use when: "Is Alertmanager healthy?" → check ``cluster_status``. - Use when: "What version of Alertmanager is running?" → check ``version_info``. - Don't use when: You want to see active alerts (call ``alertmanager_list_alerts``). Returns: dict with ``cluster_status`` / ``version_info`` / ``uptime`` / ``config_yaml``.

  • alertmanager_list_alert_groupsAM Alert Groupsread-only

    List alert groups from Alertmanager showing routing topology. Wraps ``GET /api/v2/alerts/groups``. Returns groups with their labels, receiver, and alert count — shows how alerts are grouped for notification. Examples: - Use when: "Why did I get one notification instead of many?" → check which alerts are in the same group. - Use when: "What receiver handles payment alerts?" → find the group and check its receiver. - Don't use when: You want individual alert details (call ``alertmanager_list_alerts``). Returns: dict with ``total_groups`` / ``total_alerts`` / …

  • alertmanager_list_alertsList AM Alertsread-only

    List alerts from Alertmanager with suppression state. Wraps ``GET /api/v2/alerts``. Returns alerts with their status (active/suppressed/unprocessed), silence IDs, and inhibition IDs. Unlike ``prometheus_list_alerts``, this shows WHY an alert is or isn't firing — suppressed alerts include ``silencedBy`` and ``inhibitedBy`` arrays. Examples: - Use when: "Why isn't the HighCPU alert firing?" → check if it's suppressed (silencedBy or inhibitedBy). - Use when: "Show all suppressed alerts" → filter by ``status.state == 'suppressed'``. - Don't use when: You want Prometheus-…

  • alertmanager_list_silencesList Silencesread-only

    List all silences from Alertmanager. Wraps ``GET /api/v2/silences``. Returns silences with matchers, status (active/pending/expired), creator, comment, and time bounds. Use this to understand which alerts are currently silenced and why. During incident handoffs, knowing what's silenced is critical — a silenced alert is invisible in Prometheus ``/alerts``. Examples: - Use when: "Is the HighCPU alert silenced?" → search silences for matching matchers. - Use when: "Who silenced alerts for the payment service?" → check ``createdBy`` and ``comment``. - Don't use when: You…

  • correlate_alerts_across_instancesCorrelate Alerts Across Instancesread-only

    Correlate alerts across multiple Prometheus instances. Identifies related alerts that fire simultaneously or in sequence across different Prometheus instances using temporal windows and label similarity. Use this to: - Understand cross-instance incident scope - Identify related alerts in different clusters/regions - Detect systemic issues affecting multiple instances Examples: - "Are there related alerts firing across our US and EU clusters?" - "Show me alerts that might be related to this HighCPU alert" Returns: CorrelationResult with correlated alerts, groups, and cascades.

  • detect_cascading_alertsDetect Cascading Alertsread-only

    Detect cascading alert patterns with directional dependency inference. Identifies alert propagation patterns that indicate dependency failures. Use this to: - Trace failure propagation paths through your system - Identify root cause candidates for complex incidents - Understand service dependency relationships Examples: - "What alerts typically fire after DatabaseConnectionFailed?" - "Show me the failure propagation chain in this incident" Returns: CascadeDetectionResult with detected cascades and root causes.

  • federation_analyze_alertsAnalyze Alerts Across Federation with Full Contextread-only

    Comprehensive alert analysis across all federated instances. Combines cross-instance correlation, root cause analysis, dependency mapping, and trend analysis to provide complete incident context in a single tool call. This tool integrates all v4.0 features: - Cross-instance alert correlation to identify related alerts - Root cause analysis with anomaly detection and change point identification - Dependency traversal to trace service relationships - Historical trend analysis to identify patterns - MTTR benchmarking against historical performance Returns structured JSON with all analysis dime…

  • federation_list_instancesList Federated Instancesread-only

    List all configured Prometheus and Alertmanager instances with health status

  • group_alerts_by_serviceGroup Alerts by Serviceread-only

    Group alerts by service identifiers across all instances. Clusters related alerts into service-level incident analysis bundles. Use this to: - Understand which services are affected by current incidents - Focus incident response efforts on specific service teams - Identify services with multiple simultaneous alerts Examples: - "Which services are currently experiencing alerts?" - "Group all alerts by service for my incident report" Returns: AlertGroupResult with alerts grouped by service identifier.

  • prometheus_get_build_infoBuild Inforead-only

    Get Prometheus build information. Wraps ``GET /api/v1/status/buildinfo``. Returns version, Go version, Git revision, branch, build user, and build date. Examples: - Use when: "What version of Prometheus is running?" → check ``version``. - Use when: Debugging version-specific behavior. - Don't use when: You want runtime stats (call ``prometheus_get_runtime_info``). Returns: dict with ``version`` / ``revision`` / ``branch`` / ``buildUser`` / ``buildDate`` / ``goVersion``.

  • prometheus_get_cardinalityGet Cardinalityread-only

    Get TSDB statistics and cardinality data from Prometheus. Wraps ``GET /api/v1/status/tsdb``. Returns head stats (total series, chunks, time range) and top-N lists: metrics by series count, labels by value count, and labels by memory usage. Use this to investigate cardinality explosions — the #1 operational Prometheus problem. High series counts slow queries and increase memory. Examples: - Use when: "Why is Prometheus using so much memory?" → check ``num_series`` and ``top_metrics_by_series``. - Use when: "Which labels have the most values?" → check ``top_labels_by_value…

  • prometheus_get_metric_metadataGet Metric Metadataread-only

    Get metric metadata (HELP text, TYPE, UNIT) from Prometheus. Wraps ``GET /api/v1/metadata``. Returns the metadata that Prometheus scraped from ``HELP``, ``TYPE``, and ``UNIT`` lines in the exposition format. Each metric may have multiple metadata entries if different scrape targets expose different help strings. Use this to understand what a metric measures, its type (counter, gauge, histogram, summary), and unit — essential for writing correct PromQL. For example, knowing a metric is a counter means you should use ``rate()`` or ``increase()``; a gauge can be used directly. Examples: - …

  • prometheus_get_runtime_infoRuntime Inforead-only

    Get Prometheus runtime information. Wraps ``GET /api/v1/status/runtimeinfo``. Returns operational data: goroutine count, time series count, storage retention policy, start time, corruption count, and config reload status. Examples: - Use when: "Why is Prometheus slow?" → check goroutine count and time series count. - Use when: "What's the retention policy?" → check ``storage_retention``. - Don't use when: You want the Prometheus version (call ``prometheus_get_build_info``). Returns: dict with ``start_time`` / ``goroutine_count`` / ``time_series_count`` / ``st…

  • prometheus_health_checkHealth Checkread-only

    Check Prometheus liveness and readiness. Calls ``GET /-/healthy`` and ``GET /-/ready`` — management endpoints outside the ``/api/v1`` namespace. Returns whether each probe returned a 200 status code. Use this to verify Prometheus is actually running before investigating blank query results. A failed health check means Prometheus is down; a failed readiness check means it's starting up or shutting down. Examples: - Use when: "Why are all my queries returning empty results?" → check if Prometheus is healthy first. - Use when: Setting up a new MCP connection — verify the target …

  • prometheus_list_alertsList Alertsread-only

    List all active and pending alerts from Prometheus. Wraps ``GET /api/v1/alerts``. Returns every alert that Prometheus currently tracks, with labels (including ``alertname``, ``severity``), state (``firing`` / ``pending``), the time it became active, and its current value. Also returns a summary grouped by state and a count by severity label. Examples: - Use when: "Are there any firing alerts right now?" → check ``firing_count`` and ``alerts`` where ``state='firing'``. - Use when: "Show me all critical alerts" → filter ``alerts`` by ``labels.severity == 'critical'``. -…

Show 7 more tools
  • prometheus_list_label_valuesList Label Valuesread-only

    List all values for a specific label from Prometheus. Wraps ``GET /api/v1/label/{label_name}/values``. Returns all distinct values for the named label across all time series, optionally filtered by a series selector. Use this to discover what entities exist for a given label dimension — for example, which jobs are running, which instances are scraped, or which namespaces have metrics. This is essential for building targeted PromQL queries during investigation. Examples: - Use when: "What jobs does Prometheus scrape?" → ``label='job'``; read the ``values`` list. - Use when: "Wh…

  • prometheus_list_metricsList Metricsread-only

    List all metric names known to Prometheus, with optional substring filter. Wraps ``GET /api/v1/label/__name__/values``. Prometheus returns all metric names at once — no pagination. Output is capped at 500 metrics after filtering, with a truncation hint when more exist. Use this first to discover valid metric names before writing PromQL expressions for ``prometheus_query`` or ``prometheus_query_range``. Examples: - Use when: "What metrics does Prometheus have about HTTP requests?" → ``pattern='http'``; read the ``metrics`` list. - Use when: "List all node_exporter metrics" …

  • prometheus_list_rulesList Rulesread-only

    List recording and alerting rules from Prometheus. Wraps ``GET /api/v1/rules``. Returns rule groups with their rules, including the PromQL expression, rule type (recording or alerting), and for alerting rules their current state (firing/pending/inactive). Use this to understand the alerting configuration, find recording rules that pre-compute useful aggregations, and investigate which rules are currently firing or have health issues. Examples: - Use when: "What alerting rules are configured?" → ``type='alert'``; inspect rule names and expressions. - Use when: "Are there any re…

  • prometheus_list_targetsList Targetsread-only

    List Prometheus scrape targets, summarised by job and health. Wraps ``GET /api/v1/targets``. Returns scrape targets with job name, instance address, health status (``up`` / ``down`` / ``unknown``), last scrape duration in milliseconds, and any last error. Also returns a summary grouped by job and health state. Examples: - Use when: "Which targets are currently down?" → filter ``targets`` where ``health='down'`` and check ``last_error``. - Use when: "How many instances of the 'node-exporter' job are up?" → check ``job_summary`` for the 'node-exporter' entry. - Use when…

  • prometheus_map_service_dependenciesMap Service Dependenciesread-only

    Map service-to-service dependencies from live Prometheus traffic metrics. Aggregates ``rate(<metric>[<window>])`` by (source_label, destination_label) via ``query_range`` and turns each returned series into a directed dependency edge (nodes = services, edge weight = mean request rate). No simulation — every node/edge comes from real series. When ``error_matcher`` is supplied a second query derives a per-edge error rate. Use this to: - Discover which services call which, and how heavily. - Spot high-error dependencies during an incident. Examples: - "Map dependencies for the prod namespa…

  • prometheus_queryInstant Queryread-only

    Execute an instant PromQL query against Prometheus. Wraps ``GET /api/v1/query``. Returns the result type (vector, scalar, matrix, string) and a list of samples each carrying labels, timestamp, and value. For ``vector`` results each element is one time series at the evaluation instant. Examples: - Use when: "Is the payment service up right now?" → ``query='up{job="payment-service"}'``. - Use when: "What is the current HTTP request rate?" → ``query='sum(rate(http_requests_total[5m])) by (job)'``. - Use when: "Show me all metrics for a specific instance" → ``query=…

  • prometheus_query_rangeRange Queryread-only

    Execute a PromQL range query returning time-series data points. Wraps ``GET /api/v1/query_range``. Returns one series per matching time series, each with labels and a list of ``[timestamp, value]`` pairs. Total points across all series are capped at 5000 with a truncation hint. Prometheus may reject the query with HTTP 422 (bad_data) if the step produces too many data points (> 11,000 per series). Increase the step or narrow the time range if this happens. Note: The Prometheus API does not support filtering by branch or commit in this endpoint — filters are expressed purely in PromQL label …

Signals

Stars
0
Forks
0
Open issues
0
Weekly downloads
55
Last commit
Aug 7, 2026 (2 months ago)
Last release
Jul 7, 2026 (3 months ago)
Last package publish
Aug 6, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.mshegolev/prometheus-mcp
Version
0.1.0
Auth
API key
Packages
pypi prometheus-mcp
License
MIT
Repository
github.com/mshegolev/prometheus-mcp
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
Official MCP Registrygithub-graphql

More from mshegolev

Cite this page

Prometheus MCP. Agent Mart. https://agentmart.dev/connectors/mshegolev-prometheus-mcp (last updated 2026-10-24)