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
92
Tools
343
Categories
11
Contributors
79
Provides HTTP request capabilities through the Model Context Protocol. Enables AI agents to fetch web content, retrieve API responses, and download resources from URLs. Supports converting HTML to Markdown for easier consumption and can handle various content types including JSON, text, and binary data.
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.
Official Hugging Face MCP Server that connects AI assistants directly to the Hugging Face Hub ecosystem. Provides tools for searching and retrieving models, datasets, and research papers, running inference on thousands of Gradio-powered AI applications (Spaces), and accessing the full Hub API. Supports remote HTTP-streaming via https://huggingface.co/mcp with OAuth or Bearer token auth, as well as local stdio deployment. Works with Claude, Gemini CLI, VS Code, Cursor, and any MCP-compatible client.
Provides comprehensive search capabilities through the Brave Search API via the Model Context Protocol. Enables AI agents to perform web searches, local business searches, image searches, video searches, news searches, and AI-powered summarization. Supports both STDIO and HTTP transports.
Official Atlassian Rovo MCP Server — a cloud-based bridge between Atlassian Cloud and any MCP-compatible AI tool. Enables AI agents to search, summarize, create, and update Jira issues, Confluence pages, and Compass components in real-time. Uses OAuth 2.1 or API token authentication, respects existing user permissions, and supports remote HTTP-streaming as well as local stdio via the mcp-remote proxy. Works with Claude, GitHub Copilot, Gemini CLI, VS Code, Cursor, and ChatGPT.
Official Elastic MCP server that connects AI agents to Elasticsearch data using the Model Context Protocol. Enables natural language interactions with Elasticsearch indices — querying, analyzing, and retrieving data without custom APIs. Supports both stdio and streamable-HTTP transports, and works with Elasticsearch 8.x/9.x clusters including Elasticsearch Serverless. Distributed as a Docker container image from the Elastic registry.
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.