prometheus-mcp-server
If you are the rightful owner of prometheus-mcp-server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
This is an MCP server to allow LLMs to interact with a running Prometheus instance via the API to do things like generate and execute promql queries, list and analyze metrics, etc.
Prometheus MCP Server
About
This is an MCP server to allow LLMs to interact with a running Prometheus instance via the API to do things like generate and execute promql queries, list and analyze metrics, etc.
Tools
| Tool Name | Description |
|---|---|
alertmanagers | Get overview of Prometheus Alertmanager discovery |
build_info | Get Prometheus build information |
config | Get Prometheus configuration |
exemplars_query | Performs a query for exemplars by the given query and time range |
flags | Get runtime flags |
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 |
range_query | Execute a range query against the Prometheus datasource |
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 |
NOTE:
Because the TSDB Admin API endpoints allow for potentially destructive operations like deleting data, they are not enabled by default. In order to enable the TSDB Admin API endpoints, the MCP server must be started with the flag
--dangerous.enable-tsdb-admin-toolsto acknowledge the associated risk these endpoints carry.
| Tool Name | Description |
|---|---|
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/ |
Resources
| Resource Name | Resource URI | Description |
|---|---|---|
| List Metrics | prometheus://list_metrics | List metrics available |
| Targets | prometheus://targets | Overview of the current state of the Prometheus target discovery |
| TSDB Stats | prometheus://tsdb_stats | Usage and cardinality statistics from the TSDB |
Prompts
Not implemented yet, to be determined
Installation and Usage
This MCP server is most useful when fully integrated with tooling and/or installed as a tool server with another system. Installation procedures and integration support will vary depending on the tools being used. For example:
- some systems can only interact with MCP tools and not resources/prompts
- some systems use mcp.json config file format to manage MCP servers and some require custom formats
- some systems don't speak MCP directly and require tools like mcp-to-openapi to proxy
Please check the documentation for the tool being used/integrated for specific instructions and level of support.
Docker
docker run -it --rm ghcr.io/tjhop/prometheus-mcp-server <flags>
Go
With a working go environemnt, the prometheus-mcp-server can be installed like so:
go install github.com/tjhop/prometheus-mcp-server@latest
/path/to/prometheus-mcp-server <flags>
NOTE: Installing via this method will result in a build without embedded metadata for version/build info. If you wish to fully recreate a release build as this project does, you will need to clone the project and use goreleaser to make a build:
git clone https://github.com/tjhop/prometheus-mcp-server.git
cd prometheus-mcp-server
make build
./dist/prometheus-mcp-server_linux_amd64_v1/prometheus-mcp-server <flags>
Binary
Download a release appropriate for your system from the Releases page.
/path/to/prometheus-mcp-server <flags>
System Packages
Download a release appropriate for your system from the Releases page. A Systemd service file is included in the system packages that are built.
# install system package (example assuming Debian based)
apt install /path/to/package
# create unit override, add any needed flags
systemctl edit prometheus-mcp-server.service
systemctl enable --now prometheus-mcp-server.service
Note: While packages are built for several systems, there are currently no plans to attempt to submit packages to upstream package repositories.
Development
Development Environment with Devbox + Direnv
If you use Devbox and Direnv, then simply entering the directory for the repo should set up the needed software.
Local LLM with Ollama
See for an example MCP config for use with tooling.
Requires ollama to be installed.
NOTE:
To override the default LLM (
ollama:qwen2.5-coder:3b), runexport OLLAMA_MODEL="ollama:your_model"to override it before runningmake.
Using MCP Inspector and a local ollama instance:
Requires MCP Inpsector to be installed:
make inspector
Gemini with gemini-cli
See for an example config file to run gemini-cli with the prometheus-mcp-server. Requires gemini-cli to be installed.
Using `gemini-cli` and hosted models:
```bash make gemini ```Manual Setup
Required software:
- Working Go environment
- Podman for local tests/linting/etc
- GNU Make
- ollama
- mcp inspector
- mcphost
Building
The included Makefile has several targets to aid in development:
~/go/src/github.com/tjhop/prometheus-mcp-server (main [ ]) -> make
Usage:
make <target>
Targets:
help print this help message
tidy tidy modules
fmt apply go code style formatter
lint run linters
binary build a binary
build alias for `binary`
test run tests
container build container image with binary
image alias for `container`
podman alias for `container`
docker alias for `container`
mcphost use mcphost to run the prometheus-mcp-server against a local ollama model
inspector use inspector to run the prometheus-mcp-server
open-webui use open-webui to run the prometheus-mcp-server
gemini use gemini-cli to run the prometheus-mcp-server against Google Gemini models
Command Line Flags
The available command line flags are documented in the help flag:
~/go/src/github.com/tjhop/prometheus-mcp-server (main [ ]) -> ./prometheus-mcp-server --help
usage: prometheus-mcp-server [<flags>]
Flags:
-h, --[no-]help Show context-sensitive help (also try --help-long and --help-man).
--prometheus.url="http://127.0.0.1:9090"
URL of the Prometheus instance to connect to
--http.config=HTTP.CONFIG Path to config file to set Prometheus HTTP client options
--[no-]dangerous.enable-tsdb-admin-tools
Enable and allow using tools that access Prometheus' TSDB Admin API endpoints (`snapshot`, `delete_series`, and `clean_tombstones` tools).
This is dangerous, and allows for destructive operations like deleting data. It is not the fault of this MCP server if the LLM you're
connected to nukes all your data. Docs: https://prometheus.io/docs/prometheus/latest/querying/api/#tsdb-admin-apis
--log.file=LOG.FILE The name of the file to log to (file rotation policies should be configured with external tools like logrotate)
--mcp.transport="stdio" The type of transport to use for the MCP server [`stdio`, `http`].
--log.level=info Only log messages with the given severity or above. One of: [debug, info, warn, error]
--log.format=logfmt Output format of log messages. One of: [logfmt, json]
--[no-]version Show application version.
