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
A Model Context Protocol server for Google Drive that lets AI assistants list, search, and read files stored in Drive, with automatic export of Google Docs, Sheets, Slides, and Drawings to readable formats. Authenticates via OAuth 2.0 and exposes Drive files as MCP resources so agents can ground their answers in your documents without copying data into chat first.
Zoom's official remote MCP server, published to the MCP registry, that gives AI agents access to Zoom capabilities over the Model Context Protocol. Supports semantic meeting search, Zoom-wide chat and docs search, meeting assets and recording resources, and Zoom Docs import/export, so assistants can find and summarize meeting content and manage related data. Authenticates via OAuth.
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.