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
206
Tools
545
Categories
11
Contributors
182
Cloudinary's official MCP servers for managing media through conversational AI. Cover the full media workflow: uploading and transforming images and videos, organizing assets with structured metadata, configuring processing pipelines, and running AI-powered content analysis. Available as remote OAuth endpoints or local npx processes across several focused servers (asset management, environment config, structured metadata, and analysis).
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 MCP server backed by the Kagi API. Exposes Kagi's high-quality search and summarization tools to MCP-compatible clients, including web search and the Universal Summarizer for pages and videos. Useful for research workflows that want ad-free, privacy-respecting results with concise summaries. Requires a Kagi API key.
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.