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
92
Tools
343
Categories
11
Contributors
79
Official Expo MCP server that connects AI coding assistants to Expo projects and EAS services. Enables searching and reading Expo documentation, managing EAS builds and workflows, installing compatible libraries, inspecting TestFlight crashes and feedback, and automating visual verification through simulator screenshots and interactions. Supports both remote server capabilities and local development server features for advanced automation.
GitHub's official MCP Server that connects AI tools directly to GitHub's platform. Enables AI agents to manage repositories, issues, pull requests, branches, files, actions workflows, and code security. Supports both remote (OAuth) and local (Docker/binary) modes with fine-grained toolset configuration.
Official Figma MCP server that brings design context directly into AI coding workflows. Provides tools for extracting design information, generating code from Figma selections, taking screenshots, creating and editing Figma files, generating diagrams from Mermaid syntax, searching design systems, managing Code Connect mappings, and uploading assets. Supports both remote (OAuth) and local (desktop app) server modes.
Official GitLab MCP server connecting AI tools to GitLab's DevOps platform. Enables agents to manage projects, issues, merge requests, branches, files, CI/CD pipelines, and the GitLab Duo workflow. Supports both GitLab.com SaaS and self-managed instances with fine-grained access tokens.
Official MCP server for Qdrant vector search engine. Acts as a semantic memory layer enabling AI agents to store and retrieve information using vector similarity search. Supports storing text with metadata, semantic querying, configurable embedding models via FastEmbed, and both cloud-hosted and local Qdrant instances. Useful for building RAG pipelines, code search, knowledge bases, and long-term agent memory.
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 Elastic MCP server that connects AI agents to Elasticsearch data using the Model Context Protocol. Enables natural language interactions with Elasticsearch indices — querying, analyzing, and retrieving data without custom APIs. Supports both stdio and streamable-HTTP transports, and works with Elasticsearch 8.x/9.x clusters including Elasticsearch Serverless. Distributed as a Docker container image from the Elastic registry.
Skills vs MCP servers
what's the difference?Skillsthe “what to do”
A skillA reusable, structured prompt/workflow with recommended models, an example prompt, and compatible tools. packages know-how — instructions, an example promptA ready-to-use prompt template that demonstrates how to invoke the skill., and recommended models — so an agent performs a task consistently. Skills add knowledge, not new connections.
MCP serversthe “how to connect”
An MCP serverModel Context Protocol server — a standard way to expose tools, resources, and prompts to AI agents and IDEs. gives an agent new capabilities by connecting it to real systems (databases, APIs, files) over a transportHow the client talks to the server: stdio (local process), SSE, or HTTP streaming.. 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.