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
175
Tools
465
Categories
11
Contributors
153
Official Vercel MCP server that gives AI tools secure access to Vercel projects via OAuth. Enables searching Vercel documentation, managing projects and deployments, analyzing deployment logs, and interacting with Vercel infrastructure. Supports Streamable HTTP transport with OAuth authentication and integrates with Claude Code, Cursor, VS Code, ChatGPT, Codex CLI, and other AI assistants.
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 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.
Official PagerDuty MCP server for incident management. Lets AI agents list and triage incidents, acknowledge and resolve them, look up on-call schedules, and query services so responders can manage operational incidents from AI-powered tools.
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.
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.
Skills vs MCP servers
what’s the difference?Skillsthe “what to do”
A skill packages know-how — instructions, an example prompt, and recommended models — so an agent performs a task consistently. Skills add knowledge, not new connections.
MCP serversthe “how to connect”
An MCP server gives an agent new capabilities by connecting it to real systems (databases, APIs, files) over a transport. 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.