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
Buildkite's official MCP server for querying and operating CI/CD pipelines, builds, jobs, artifacts, and organization-level delivery workflows.
Official CircleCI MCP server. Lets AI agents fetch build and pipeline status, retrieve failed build logs, and diagnose flaky or broken jobs so developers can fix CI failures without leaving their AI-powered tools.
MCP server for Jenkins CI/CD. Enables AI agents to trigger builds, inspect job and build status, stream console logs, and diagnose failing pipelines, bringing continuous integration workflows into AI-powered development environments.
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.
Official Netlify MCP server for managing web deployments. Lets AI agents create and configure sites, trigger and monitor deploys, manage environment variables, and read build logs. Useful for shipping frontends and serverless functions, debugging failed builds, and automating deployment workflows from an AI assistant.
Microsoft's official MCP server for Azure DevOps. Brings Azure DevOps capabilities to AI agents, including managing work items and boards, browsing Git repositories and pull requests, querying builds and pipelines, and accessing wikis and test plans. Lets teams drive their Azure DevOps workflows through natural language from MCP-compatible tools.
JFrog's MCP server lets agents work with Platform services for artifact repositories, build information, release lifecycle management, and software supply-chain workflows.
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.