Prometheus MCP Server

{
  "mcpServers": {
    "prometheus-mcp-server-prometheus": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/tjhop/prometheus-mcp-server:0.18.0"
      ]
    }
  }
}

claude mcp add --transport stdio prometheus-mcp-server-prometheus -- docker run -i --rm ghcr.io/tjhop/prometheus-mcp-server:0.18.0

{
  "mcpServers": {
    "prometheus-mcp-server-prometheus": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/tjhop/prometheus-mcp-server:0.18.0"
      ]
    }
  }
}

{
  "servers": {
    "prometheus-mcp-server-prometheus": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/tjhop/prometheus-mcp-server:0.18.0"
      ]
    }
  }
}

Config formats checked against the official docs on Oct 7, 2026: modelcontextprotocol.io (opens in a new tab), code.claude.com (opens in a new tab), cursor.com (opens in a new tab), code.visualstudio.com (opens in a new tab).

• alertmanagers

  Get overview of Prometheus Alertmanager discovery

• build_info

  Get Prometheus build information

• config

  Get Prometheus configuration

• docs_list

  List of Official Prometheus Documentation Files

• docs_read

  Read the named markdown file containing official Prometheus documentation from the prometheus/docs repo

• docs_search

  Search the markdown files containing official Prometheus documentation from the prometheus/docs repo

• exemplar_query

  Performs a query for exemplars by the given query and time range

• flags

  Get runtime flags

• healthy

  Management API endpoint that can be used to check Prometheus health

• label_names

  Returns the unique label names present in the block in sorted order by given time range and matchers

• label_values

  Performs a query for the values of the given label, time range and matchers

• list_alerts

  List all active alerts

• list_rules

  List all alerting and recording rules that are loaded

• list_targets

  Get overview of Prometheus target discovery

• metric_metadata

  Returns metadata about metrics currently scraped by the metric name

• query

  Execute an instant query against the Prometheus datasource, returning one value per series at a single point in time

• quit

  Management API endpoint that can be used to trigger a graceful shutdown of Prometheus

• range_query

  Execute a range query against the Prometheus datasource, returning values over a time window

• ready

  Management API endpoint that can be used to check Prometheus is ready to serve traffic (i.e. respond to queries

• reload

  Management API endpoint that can be used to trigger a reload of the Prometheus configuration and rule files

• runbooks_list

  List the runbooks embedded in this server: guided workflows (Agent Skills) for common Prometheus tasks

• runbooks_read

  Read the named runbook by skill name (e.g. check-system-health)

• runtime_info

  Get Prometheus runtime information

• series

  Finds series by label matchers

• targets_metadata

  Returns metadata about metrics currently scraped by the target

• tsdb_stats

  Get usage and cardinality statistics from the TSDB

• wal_replay_status

  Get current WAL replay status

• clean_tombstones

  Removes the deleted data from disk and cleans up the existing tombstones

• delete_series

  deletes data for a selection of series in a time range

• snapshot

  creates a snapshot of all current data into snapshots/- under the TSDB's data directory and returns the directory as…

• prometheus

  n/a

The prompt used was: querying my metrics is slow, can you help me figure out why? The prompt used was: use the tools from the prometheus mcp server to investigate the metrics from the mcp server and suggest prometheus recording rules for SLOs