Prometheus MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROMETHEUS_URL | Yes | URL of the Prometheus server | http://localhost:9090 |
| PROMETHEUS_TOKEN | No | Bearer token for authentication | |
| PROMETHEUS_TIMEOUT | No | Connection timeout in milliseconds | 10000 |
| PROMETHEUS_INSECURE | No | Allow insecure connections (for self-signed certificates) | false |
| PROMETHEUS_PASSWORD | No | Password for basic authentication | |
| PROMETHEUS_USERNAME | No | Username for basic authentication |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| prom_queryC | Execute a PromQL instant query |
| prom_rangeC | Execute a PromQL range query |
| prom_discoverC | Discover all available metrics |
| prom_metadataC | Get metric metadata |
| prom_targetsD | Get scrape target information |
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 5 tools
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.
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.
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.
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.