MCP Servers
The open registry for Model Context Protocol servers. Find the right tools, resources, and prompts for your AI agents — filtered by category, transport, or use case.
Servers
160
Tools
465
Categories
11
Contributors
142
MCP server for Grafana's observability platform. Enables AI agents to query metrics from Prometheus, search and analyze logs from Loki, query traces, list and manage dashboards, and investigate incidents. Useful for debugging production issues, building monitoring dashboards, and performing root cause analysis with AI assistance across the full Grafana LGTM stack.
MCP server for Sentry error tracking integration. Enables AI agents to retrieve and analyze issues, view error stack traces, search events by query, and access project performance data. Helps developers debug production errors by providing contextual error information directly in AI-powered development workflows.
Confluent's open-source MCP server that connects AI assistants to Confluent Cloud, Confluent Platform, and standalone Apache Kafka deployments. Provides tools to manage Kafka topics and connectors, work with Schema Registry, and run Flink SQL statements through natural language, helping teams operate streaming data platforms from an MCP client.
Dynatrace's official MCP server that brings the Dynatrace observability platform into AI workflows. Lets assistants query problems and vulnerabilities, run DQL against logs, metrics, and traces, inspect entities, and pull real-time monitoring data directly into a developer's coding environment for faster troubleshooting and root-cause analysis.
JFrog's MCP server lets agents work with Platform services for artifact repositories, build information, release lifecycle management, and software supply-chain workflows.
MCP server that lets AI assistants query and analyze Prometheus metrics through standardized interfaces. Exposes instant and range PromQL queries, metric and label discovery, and target/health inspection, allowing agents to investigate system performance and troubleshoot incidents using natural language instead of hand-writing PromQL.
Skills vs MCP servers
what's the difference?Skillsthe “what to do”
A skillA reusable, structured prompt/workflow with recommended models, an example prompt, and compatible tools. packages know-how — instructions, an example promptA ready-to-use prompt template that demonstrates how to invoke the skill., and recommended models — so an agent performs a task consistently. Skills add knowledge, not new connections.
MCP serversthe “how to connect”
An MCP serverModel Context Protocol server — a standard way to expose tools, resources, and prompts to AI agents and IDEs. gives an agent new capabilities by connecting it to real systems (databases, APIs, files) over a transportHow the client talks to the server: stdio (local process), SSE, or HTTP streaming.. MCP adds connections and actions, not task instructions.
Rule of thumb: reach for a skill when you need the model to do a task well, and an MCP server when you need it to reach a tool or system. They compose — a skill can rely on tools an MCP server provides.
Built an MCP server?
Submit it to the registry — it's open source and community-maintained.