Skip to main content
Glama
Prometheus MCP Server

Prometheus MCP Server

by yanmxa

Prometheus MCP Server

npm version License: MIT

A Model Context Protocol (MCP) server that provides seamless integration with Prometheus, enabling AI assistants to query metrics, discover available data, and analyze system performance through natural language interactions.

Features

  • Real-time Metrics Access - Query current and historical metrics data

  • Metrics Discovery - Find available metrics and monitoring targets

  • Multiple Auth Methods - Basic auth, bearer tokens, and TLS support

  • Type-safe - Full TypeScript implementation

Related MCP server: Prometheus MCP Server

MCP Configuration

Add to your MCP client settings:

{
  "mcpServers": {
    "prometheus": {
      "command": "npx",
      "args": ["prometheus-mcp-server"],
      "env": {
        "PROMETHEUS_URL": "http://localhost:9090"
      }
    }
  }
}

Using global installation

First install the package globally:

npm install -g prometheus-mcp-server

Then configure your MCP client:

{
  "mcpServers": {
    "prometheus": {
      "command": "prometheus-mcp-server",
      "env": {
        "PROMETHEUS_URL": "http://localhost:9090"
      }
    }
  }
}

Environment Variables

# Required
PROMETHEUS_URL=http://localhost:9090

# Optional Authentication
PROMETHEUS_USERNAME=admin
PROMETHEUS_PASSWORD=password
PROMETHEUS_TOKEN=bearer-token

# Optional Connection
PROMETHEUS_TIMEOUT=10000
PROMETHEUS_INSECURE=false

Available Tools

Tool

Description

Use Case

prom_query

Execute PromQL instant query

Get current metric values, alerts status

prom_range

Execute PromQL range query

Analyze trends, create graphs, historical data

prom_discover

Discover available metrics

Explore what metrics are available in your system

prom_metadata

Get metric metadata

Understand metric types, descriptions, and units

prom_targets

Get scrape targets info

Monitor scraping health and service discovery

Example Usage

Ask your AI assistant natural language questions:

  • "What's the current CPU usage across all servers?"

  • "Show me HTTP request rates for the last 6 hours"

  • "Which services have the highest memory consumption?"

  • "Are there any failing health checks?"

  • "What metrics are available for monitoring my database?"

Development

# Run with inspector
npm run inspector

# Run directly
npm run dev

Connection Methods

1. No Authentication

export PROMETHEUS_URL=http://localhost:9090

2. Basic Authentication

export PROMETHEUS_URL=http://localhost:9090
export PROMETHEUS_USERNAME=admin
export PROMETHEUS_PASSWORD=secret

3. Bearer Token

export PROMETHEUS_URL=https://prometheus.example.com:9090
export PROMETHEUS_TOKEN=your-bearer-token

Additional Options

For self-signed certificates or development:

export PROMETHEUS_INSECURE=true

License

MIT

Available Tools

5 tools
prom_discoverC

Discover all available metrics

Inputs: no named parameters.

prom_metadataC

Get metric metadata

Inputs: metric.

prom_queryC

Execute a PromQL instant query

Inputs: query (required), time, includes.

prom_rangeC

Execute a PromQL range query

Inputs: query (required), start (required), end (required), step (required), +1 more.

prom_targetsD

Get scrape target information

Inputs: state.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: discovery, metadata retrieval, instant queries, range queries, and target monitoring. There is no overlap in functionality, making it easy for an agent to select the right tool for each task without confusion.

    Naming Consistency5/5

    All tools follow a consistent 'prom_' prefix with descriptive suffixes (discover, metadata, query, range, targets). This uniform naming pattern enhances readability and predictability across the tool set.

    Tool Count5/5

    With 5 tools, this server is well-scoped for Prometheus monitoring tasks. Each tool serves a specific, essential function in the domain, and the count is neither too sparse nor overwhelming for the intended purpose.

    Completeness4/5

    The tool set covers core Prometheus operations well, including querying, metadata, and target discovery. A minor gap exists in lacking explicit alert or rule management tools, but agents can still perform most monitoring workflows effectively with the provided tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables Large Language Models to retrieve, analyze, and query metric data from Prometheus databases through pre-defined routes.
      33
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides access to Prometheus metrics and queries through standardized Model Context Protocol interfaces, allowing AI assistants to execute PromQL queries and analyze metrics data.
      6
      526
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A tool that enables access to Prometheus metrics data through a Model Context Protocol server, allowing interaction with monitoring data using natural language.
      MIT
    • A
      license
      B
      quality
      F
      maintenance
      Provides seamless integration between AI assistants and Prometheus, enabling natural language interactions with your monitoring infrastructure. This server allows for effortless querying, discovery, and analysis of metrics.
      10
      655 npm
      27
      MIT