prometheus.com
prometheus.com logo

Prometheus

Connects AI systems to Prometheus monitoring infrastructure for executing PromQL queries, discovering metrics, and retri...

Created byApr 22, 2025

Prometheus MCP Server

A [Model Context Protocol][mcp] (MCP) server for Prometheus.
This provides access to your Prometheus metrics and queries through standardized MCP interfaces, allowing AI assistants to execute PromQL queries and analyze your metrics data.

Features

  • Execute PromQL queries against Prometheus
  • Discover and explore metrics
  • Authentication support
  • Docker containerization support
  • Provide interactive tools for AI assistants
The list of tools is configurable, so you can choose which tools you want to make available to the MCP client. This is useful if you don't use certain functionality or if you don't want to take up too much of the context window.

Usage

  1. Ensure your Prometheus server is accessible from the environment where you'll run this MCP server.
  1. Configure the environment variables for your Prometheus server, either through a .env file or system environment variables:
  1. Add the server configuration to your client configuration file. For example, for Claude Desktop:
Note: if you see Error: spawn uv ENOENT in Claude Desktop, you may need to specify the full path to uv or set the environment variable NO_UV=1 in the configuration.

Docker Usage

This project includes Docker support for easy deployment and isolation.

Building the Docker Image

Build the Docker image using:

Running with Docker

You can run the server using Docker in several ways:

Using docker run directly:

Using docker-compose:

Create a .env file with your Prometheus credentials and then run:

Running with Docker in Claude Desktop

To use the containerized server with Claude Desktop, update the configuration to use Docker with the environment variables:
This configuration passes the environment variables from Claude Desktop to the Docker container by using the -e flag with just the variable name, and providing the actual values in the env object.
Note about Docker implementation: The Docker setup has been updated to match the structure of the chess-mcp project, which has been proven to work correctly with Claude. The new implementation uses a multi-stage build process and runs the entry point script directly without an intermediary shell script. This approach ensures proper handling of stdin/stdout for MCP communication.

Development

Contributions are welcome! Please open an issue or submit a pull request if you have any suggestions or improvements.
This project uses `uv` to manage dependencies. Install uv following the instructions for your platform:
You can then create a virtual environment and install the dependencies with:

Project Structure

The project has been organized with a src directory structure:

Testing

The project includes a comprehensive test suite that ensures functionality and helps prevent regressions.
Run the tests with pytest:
Tests are organized into:
  • Configuration validation tests
  • Server functionality tests
  • Error handling tests
  • Main application tests
When adding new features, please also add corresponding tests.

Tools

[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]

License

MIT

Prometheus MCP Server

A [Model Context Protocol][mcp] (MCP) server for Prometheus.
This provides access to your Prometheus metrics and queries through standardized MCP interfaces, allowing AI assistants to execute PromQL queries and analyze your metrics data.

Features

  • Execute PromQL queries against Prometheus
  • Discover and explore metrics
  • Authentication support
  • Docker containerization support
  • Provide interactive tools for AI assistants
The list of tools is configurable, so you can choose which tools you want to make available to the MCP client. This is useful if you don't use certain functionality or if you don't want to take up too much of the context window.

Usage

  1. Ensure your Prometheus server is accessible from the environment where you'll run this MCP server.
  1. Configure the environment variables for your Prometheus server, either through a .env file or system environment variables:
  1. Add the server configuration to your client configuration file. For example, for Claude Desktop:
Note: if you see Error: spawn uv ENOENT in Claude Desktop, you may need to specify the full path to uv or set the environment variable NO_UV=1 in the configuration.

Docker Usage

This project includes Docker support for easy deployment and isolation.

Building the Docker Image

Build the Docker image using:

Running with Docker

You can run the server using Docker in several ways:

Using docker run directly:

Using docker-compose:

Create a .env file with your Prometheus credentials and then run:

Running with Docker in Claude Desktop

To use the containerized server with Claude Desktop, update the configuration to use Docker with the environment variables:
This configuration passes the environment variables from Claude Desktop to the Docker container by using the -e flag with just the variable name, and providing the actual values in the env object.
Note about Docker implementation: The Docker setup has been updated to match the structure of the chess-mcp project, which has been proven to work correctly with Claude. The new implementation uses a multi-stage build process and runs the entry point script directly without an intermediary shell script. This approach ensures proper handling of stdin/stdout for MCP communication.

Development

Contributions are welcome! Please open an issue or submit a pull request if you have any suggestions or improvements.
This project uses `uv` to manage dependencies. Install uv following the instructions for your platform:
You can then create a virtual environment and install the dependencies with:

Project Structure

The project has been organized with a src directory structure:

Testing

The project includes a comprehensive test suite that ensures functionality and helps prevent regressions.
Run the tests with pytest:
Tests are organized into:
  • Configuration validation tests
  • Server functionality tests
  • Error handling tests
  • Main application tests
When adding new features, please also add corresponding tests.

Tools

[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]
[object Object]

License

MIT