집중된, 읽기 전용 MCP 서버로, 제한된 Prometheus 즉시 쿼리, 활성 알림, 대상 상태를 처리합니다. 알파: 테스트는 합성 HTTP 응답을 사용합니다. 실제 Prometheus 릴리스와의 호환성은 보장되지 않습니다.
Python 3.11+ 및 uv가 필요합니다.
uv sync --extra test
export PROMETHEUS_SAFE_URL=https://prometheus.example.invalid
uv run prometheus-safe-mcp프로세스는 stdio를 통해 MCP를 사용합니다. .env를 로드하지 않습니다. .env.example은 문서용일 뿐입니다. 읽기 전용, 네트워크 제한 Prometheus 엔드포인트의 URL을 구성하세요.
Related MCP server: Prometheus MCP Server
모든 도구는 HTTP GET을 사용합니다. 쿼리 길이, HTTP 지속 시간/바이트, 반환된 대상 수가 제한됩니다. 구성은 URL 자격 증명, 쿼리, 조각, 비 HTTP 스킴을 거부합니다. 감사 기록에는 PromQL 텍스트나 응답 본문 대신 작업 범주가 포함됩니다. 이는 업스트림 인증, 권한 부여 또는 이그레스 정책을 대체하지 않습니다. 보안 설계를 참조하세요.
uv run --extra test pytest
uv run python -m compileall -q src tests
uv buildMIT © 2026 Ben Gauger.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.0active_alertsprometheus_querytarget_healthScored across 3 tools
Each tool targets a clearly distinct aspect of Prometheus: querying metrics, listing active alerts, and checking target health. There is no functional overlap between them, making tool selection unambiguous.
All three tool names follow a consistent snake_case convention with a noun-like pattern (prometheus_query, active_alerts, target_health). The names are predictable and reflect their purpose without mixing conventions.
Three tools is a lean but reasonable count for a minimal Prometheus integration, covering the most common read-only operations. It feels slightly thin for a full-featured server but is appropriate for a focused purpose.
The surface covers core operations (query, alerts, health) but lacks obvious complementary features like range queries, alert rule management, or metric metadata retrieval. Agents may need to work around these gaps for more complex workflows.
Query OneLens cloud-cost data in natural language: breakdowns, trends, cost centers. Read-only.
Query Churn Solution cancellation-flow metrics, revenue, and feedback analytics (read-only).
Query Honeycomb observability data: traces, events, metrics, SLOs, triggers, and boards.
Query PanDev Metrics analytics and reporting data
