MCP server for LLMs to interact with Prometheus
Prometheus MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for LLMs to interact with Prometheus.
The prompt used was: > querying my metrics is slow, can you help me figure out why?
Once Prometheus is connected, these are the calls the assistant has available:
Tools — The Prometheus HTTP API outputs JSON data, and the tools in this MCP server return that JSON to the LLM for processing as it's structured and wellResources — The Resources tool exposed by this serverBinary — The Binary tool exposed by this serverMetrics — Once running, the server exposes Prometheus metrics on the configured listen address and telemetry path (:8080/metrics, by default). Please seeghcr.io/tjhop/prometheus-mcp-server on a container image is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need one environment variable: PROMETHEUS_MCP_SERVER_PROMETHEUS_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Prometheus's toolset — Tools, Resources, Binary and 1 more — is a fair guide to whether it matches your workflow. It is maintained by tjhop; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Tools | The Prometheus HTTP API outputs JSON data, and the tools in this MCP server return that JSON to the LLM for processing as it's structured and well understood by LLMs. |
| Resources | The Resources tool exposed by this server. |
| Binary | The Binary tool exposed by this server. |
| Metrics | Once running, the server exposes Prometheus metrics on the configured listen address and telemetry path (:8080/metrics, by default). Please see [Flags](#command-line-flags) for more information on how to change the liste |
{
"mcpServers": {
"prometheus-mcp-server-tjhop": {
"command": "docker",
"args": ["run", "-i", "--rm", "ghcr.io/tjhop/prometheus-mcp-server"],
"env": {
"PROMETHEUS_MCP_SERVER_PROMETHEUS_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| PROMETHEUS_MCP_SERVER_PROMETHEUS_URL | Endpoint or connection string the server talks to. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.