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
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.
Official GitLab MCP server connecting AI tools to GitLab's DevOps platform. Enables agents to manage projects, issues, merge requests, branches, files, CI/CD pipelines, and the GitLab Duo workflow. Supports both GitLab.com SaaS and self-managed instances with fine-grained access tokens.
A powerful, native Go implementation of a Kubernetes MCP server with support for Kubernetes and OpenShift. Unlike kubectl wrappers, it interacts directly with the Kubernetes API server — no external CLI tools required. Distributed as a single lightweight binary for Linux, macOS, and Windows. Supports multi-cluster configurations, Helm chart management, Tekton pipelines, pod exec, log streaming, and optional OpenTelemetry distributed tracing.
Official MCP server for Qdrant vector search engine. Acts as a semantic memory layer enabling AI agents to store and retrieve information using vector similarity search. Supports storing text with metadata, semantic querying, configurable embedding models via FastEmbed, and both cloud-hosted and local Qdrant instances. Useful for building RAG pipelines, code search, knowledge bases, and long-term agent memory.
Cloudinary's official MCP servers for managing media through conversational AI. Cover the full media workflow: uploading and transforming images and videos, organizing assets with structured metadata, configuring processing pipelines, and running AI-powered content analysis. Available as remote OAuth endpoints or local npx processes across several focused servers (asset management, environment config, structured metadata, and analysis).
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.