Skip to main content
Glama
mateusdata

prometheus-mcp-server

by mateusdata

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PROMETHEUS_HOSTYesThe URL of your Prometheus instance (e.g., 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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
completions
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
context-prometheusC

Consultes as regras e diretrizes para fazer queries e interagir com o Prometheus

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

NameDescription
review-codeRevise o código para melhores práticas e possíveis problemas
query-metricaExecuta uma query Prometheus com base em uma métrica conhecida
saudacaoGera uma saudação para membros do time

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 10 tools

Disambiguation5/5

Every tool has a clearly distinct purpose targeting specific Prometheus resources or query types, with no overlapping functionality. For example, get-alerts retrieves alerts, get-series finds series by labels, and instant-query versus range-query handle different query modes, making misselection unlikely.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern with 'get-' or query-type prefixes for most tools, making them predictable. However, 'context-prometheus' deviates slightly by using a noun_verb structure and being in Portuguese, which breaks the pattern but is still understandable.

Tool Count5/5

With 10 tools, this is well-scoped for a Prometheus server, covering key operations like queries, metadata, alerts, rules, and status without being overwhelming. Each tool serves a distinct and necessary function in monitoring and data retrieval.

Completeness4/5

The toolset provides comprehensive coverage for querying, monitoring, and status checks in Prometheus, including instant and range queries, alerts, rules, and targets. A minor gap exists in management operations like configuration changes or data deletion, but core workflows are fully supported.

Maintenance

ActivityInactive
ResponsivenessNo issues