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
Microsoft's official Playwright MCP server that provides browser automation capabilities for AI agents. Enables navigating web pages, clicking elements, filling forms, taking screenshots, and extracting content. Supports headless and headed modes with Chromium, Firefox, and WebKit browsers. Ideal for web testing, scraping, and interactive browsing tasks.
Provides browser automation capabilities through the Model Context Protocol using Puppeteer. Enables AI agents to navigate web pages, take screenshots, click elements, fill forms, and execute JavaScript in a browser context. Useful for web scraping, testing, and interacting with web applications programmatically. Originally part of the reference servers, now archived and available in servers-archived.
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.
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 Browserbase MCP server for cloud browser automation. Lets AI agents create headless browser sessions, navigate pages, extract content, take screenshots, and perform actions using Stagehand, enabling reliable web automation and scraping at scale from AI-powered tools.
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.