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
195
Tools
516
Categories
11
Contributors
171
An MCP server for managing content on a Ghost CMS instance. Exposes the Ghost Admin API as tools so AI assistants can list, draft, update, and publish posts and pages, manage tags, and look up authors, which suits editorial and blog automation workflows.
A Model Context Protocol server for Strapi headless CMS. Lets AI assistants list content types, query and filter entries, and create or update content through the Strapi REST API, along with media upload support, so agents can manage a Strapi project's content without leaving the conversation.
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.