Prometheus MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ORG_ID | No | Optional: Organization ID for multi-tenant setups like Cortex, Mimir or Thanos | |
| PROMETHEUS_URL | Yes | Required: URL of your Prometheus server | |
| PROMETHEUS_TOKEN | No | Optional: Bearer token for authentication to Prometheus | |
| PROMETHEUS_PASSWORD | No | Optional: Password for basic auth authentication to Prometheus | |
| PROMETHEUS_USERNAME | No | Optional: Username for basic auth authentication to Prometheus |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Health check endpoint for container monitoring and status verification |
| execute_queryC | Execute a PromQL instant query against Prometheus |
| execute_range_queryB | Execute a PromQL range query with start time, end time, and step interval |
| list_metricsA | List all available metrics in Prometheus with optional pagination support |
| get_metric_metadataA | Get metadata (type, help, unit) for metrics. Returns all metric metadata when no metric name is provided. Use filter_pattern to search metric names and descriptions. |
| get_targetsA | Get information about all scrape targets |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: query types (instant vs range), metadata retrieval, target info, health check, and metric listing. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., execute_query, get_metric_metadata). No deviations.
Six tools cover the essential Prometheus operations without being excessive or insufficient. Well-scoped for the server's purpose.
Core CRUD-like operations for queries and metadata are present. Minor gaps like alert management or rule configuration are missing but not critical for the primary use case.