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
Directus' MCP integration connects agents to headless CMS data, schemas, and operations for governed content and application workflows.
Payload CMS provides an MCP integration for agents to explore and manage CMS content, schemas, and application workflows.
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.
The official Shopify Dev MCP server, built by Shopify, gives AI coding tools direct access to Shopify's developer platform. Agents can search Shopify documentation, explore and introspect the Admin and Storefront GraphQL API schemas, validate GraphQL operations, and scaffold Functions — keeping answers grounded in up-to-date, accurate Shopify APIs.
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.