prometheus-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROMETHEUS_BASE_URL | No | The base URL of the Prometheus server | http://localhost:9090 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| instant-queryC | Execute an instant Prometheus query |
| range-queryC | Execute a range Prometheus query |
| get-seriesC | Find series by label matchers |
| get-label-valuesC | Get label values for a label name |
| get-metadataC | Get metadata for metrics |
| get-targetsC | Get information about targets |
| get-alertsC | Get information about alerts |
| get-rulesB | Get information about alerting and recording rules |
| get-statusB | Get status information about the Prometheus server |
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 9 tools
Each tool has a distinct, clearly defined purpose. The instant-query and range-query are differentiated by query type, while the other tools retrieve specific Prometheus resources (series, labels, metadata, targets, alerts, rules, status) without overlap.
Most tool names follow a verb_noun pattern (get-series, get-label-values, get-metadata, etc.), but the query tools break the pattern with 'instant-query' and 'range-query' where 'query' comes after the adjective. This is a minor deviation but still readable and predictable.
Nine tools is well-scoped for a Prometheus server, covering the core read operations without redundancy. Each tool earns its place by providing a unique capability.
The surface covers the main read operations (query, series, labels, metadata, targets, alerts, rules, status), which is appropriate for a read-only Prometheus server. However, it lacks write operations (e.g., creating or modifying rules/alerts) and advanced query features (e.g., query for multiple time points or metric discovery).