Servidores MCP
El registro abierto de servidores Model Context Protocol. Encuentra herramientas, recursos y prompts para tus agentes de IA, filtrados por categoría, transporte o caso de uso.
Servidores
177
Herramientas
471
Categorías
11
Colaboradores
155
Connects AI agents to Datadog for monitoring, observability, and incident management. Enables querying metrics, viewing traces, searching logs, and managing monitors programmatically. Supports dashboard creation, alert configuration, and SLO tracking through the Model Context Protocol.
Prefect's MCP integration gives agents access to orchestration objects including flows, deployments, work pools, and run diagnostics.
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.
Apache SkyWalking's MCP server gives agents access to observability data for tracing, service topology, metrics, logs, and production incident investigation.
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.
Dagster's MCP integration enables agents to inspect and operate data assets, jobs, schedules, and runs in modern data platforms.
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.
Honeycomb's MCP server that lets AI assistants query and analyze observability data, including events, traces, alerts (triggers), and boards. Agents can run queries against datasets, inspect columns and schemas, and cross-reference production behavior with the codebase to investigate incidents. Connects to Honeycomb via API key or OAuth.
Skills frente a servidores MCP
¿cuál es la diferencia?Skillsel «qué hacer»
Una Skill reúne conocimientos prácticos —instrucciones, un prompt de ejemplo y modelos recomendados— para que un agente realice una tarea de forma consistente. Las Skills aportan conocimiento, no nuevas conexiones.
Servidores MCPel «cómo conectarse»
Un servidor MCP proporciona nuevas capacidades a un agente conectándolo con sistemas reales —bases de datos, API o archivos— mediante un transporte. MCP añade conexiones y acciones, no instrucciones de tarea.
Regla práctica: usa una Skill cuando necesites que el modelo realice bien una tarea y un servidor MCP cuando necesites conectarlo con una herramienta o sistema. Se complementan: una Skill puede utilizar las herramientas que proporciona un servidor MCP.
¿Has creado un servidor MCP?
Envíalo al registro: es de código abierto y está mantenido por la comunidad.