Skip to main content
Glama
etruong42

Prometheus MCP

by etruong42
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

NameDescription
prometheus_query_rangeA
Query Prometheus /query_range API endpoint and return
an image of a plot of the time series monitoring data.
Use this tool whenever the user asks about the status
of their compute infrastructure.
prometheus_alert_rulesB

Query the Prometheus /rules API. Returns a list of alerting and recording rules that are currently loaded. In addition it returns the currently active alerts fired by the Prometheus instance of each alerting rule.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
file://promql_for_gcp_docs.md/
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools target completely different aspects: one retrieves alert and recording rules, the other queries time series data and returns a plot. There is no overlap in functionality, making selection unambiguous.

Naming Consistency4/5

Both tools share the 'prometheus_' prefix and follow snake_case. One uses a noun phrase ('alert_rules') and the other a verb-noun phrase ('query_range'), which is a minor inconsistency but still predictable and descriptive.

Tool Count2/5

With only 2 tools for a complex system like Prometheus, the server is severely under-scoped. Many essential operations (e.g., listing metrics, instant queries, target discovery) are missing, limiting its usefulness.

Completeness2/5

The server covers only alert rules and range queries with plots, leaving out critical Prometheus capabilities such as instant queries, metric metadata, targets, or alert management beyond listing rules. Agents cannot perform basic monitoring workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources