prometheus-mcp-server
Related Servers
Alternatives to prometheus-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA TypeScript-based MCP server that integrates with Swagger/OpenAPI specifications to expose API endpoints as tools for Large Language Models (LLMs), enabling natural language interaction with any OpenAPI-compliant API.49MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables LLMs to understand and work with TypeScript APIs they haven't been trained on by providing structured access to TypeScript type definitions and documentation.17 npm46MIT
- -licenseNot gradedqualityNot gradedmaintenanceA production-ready TypeScript MCP server providing basic tools (add, echo, timestamp), resources (server info, greetings, data access), and prompt templates (analyze, code-review, summarize). Serves as a foundation for building custom MCP servers with extensible architecture.284 npm-
- AlicenseBqualityCmaintenanceA TypeScript-based MCP server that provides tools to interact with local Codex and Gemini CLIs via stdio transport. It enables users to execute prompts through the ask_codex and ask_gemini tools, supporting custom models and timeout configurations.111 npm6MIT
- AlicenseNot gradedqualityDmaintenanceA TypeScript/Node.js MCP server that wraps the Metabase REST API, enabling AI agents to execute queries, explore schemas, and build dashboards through structured tool calls.44 npmMIT
- AlicenseNot gradedqualityDmaintenanceProxy MCP server that translates tool calls into TypeScript code generation, enabling LLMs to orchestrate multi-tool workflows efficiently via code.9 npm14MIT
TDQS
Scored across 10 tools
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.
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.
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.
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.