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
177
Tools
471
Categories
11
Contributors
155
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.
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.
Sanity's official MCP server that connects structured content to AI agents. Provides tools to run GROQ queries, read and write documents, explore and deploy schemas, manage content releases, and generate images, all with full schema context. Available as a hosted remote server at mcp.sanity.io and works with MCP-compatible clients like Cursor, Claude Code, and VS Code.
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.