Browse Model Context Protocol (MCP) servers and integrations.
Model Context Protocol (MCP) servers are standardized interfaces that allow large language models and AI agents to securely interact with external systems, tools, and data stores. Instead of relying on bespoke integrations, an MCP server exposes defined tools, resources, and prompts over a unified protocol. This architecture enables AI coding assistants, desktop agents, and autonomous workflows to query databases, manipulate local files, execute terminal commands, and call external APIs with fine-grained control.
This directory catalogs 1186 active MCP servers structured across 20 functional domains. Developers can browse servers organized by target environment and capability, including Databases & Data Stores for querying relational and vector backends, Developer Tools & Code Intelligence for IDE enhancements, and DevOps, CI/CD & Version Control for deployment automation. Additional domains include Cloud & Infrastructure, Security & Compliance, Browser & Web Automation, AI Memory & Context, and Files, Documents & PDFs. Each category groups servers designed to grant models access to specific operational layers without requiring custom middleware.
Selecting the right MCP server depends on your client environment, transport protocol, and execution runtime. First, confirm compatibility with your AI client, such as Claude Desktop, Cursor, Windsurf, or custom agent runtimes built on the MCP SDK. Second, inspect the server transport type; most run locally over standard input/output (stdio), while others operate remotely via Server-Sent Events (SSE) or WebSockets. Finally, evaluate the required permission scopes and authentication mechanisms. Production workflows benefit from servers that enforce read-only modes or explicit confirmation prompts prior to executing destructive actions on your infrastructure.
| MCP server | What it connects to | Type | Repository |
|---|---|---|---|
| MySQL Schema MCP Server | A server for retrieving MySQL database schema information using the FastMCP framework. | Open Source | |
| Task Orchestrator | AI-powered task orchestration and workflow automation with specialized agent roles, intelligent task decomposition, and seamless integration across Claude Desktop, Cursor | Unknown | |
| ZIP MCP Server | The ZIP MCP Server acts as a digital packing assistant for AI models, allowing them to manage compressed files just | Unknown | |
| Qlik Cloud | Interact with Qlik Cloud applications and extract data from visualizations using the Qlik Cloud API. | Unknown | |
| Qwen-Agent | A framework for developing LLM applications with capabilities like tool usage, planning, and memory, based on the Qwen model. | Open Source | |
| MCP ZAP Server | Exposes OWASP ZAP as an MCP server, enabling AI agents to orchestrate security scans, import OpenAPI specs, and generate reports. | Open Source | |
| WebRTC MCP Chat Server | A remote WebRTC chat server with secure temporary rooms and MCP support for background agents. | Unknown | |
| QuantConnect | A server for local interactions with the QuantConnect API. | Unknown | |
| Perplexity MCP Zerver | Interact with Perplexity.ai using Puppeteer without an API key. Requires Node.js and stores chat history locally. | Open Source | |
| Qdrant | Implement semantic memory layer on top of the Qdrant vector search engine | Open Source |
An MCP server is an application that implements the Model Context Protocol to expose data, tools, and prompts to AI assistants. It standardizes how models read external context and trigger actions in external systems.
Clients supporting MCP include Claude Desktop, Cursor, Windsurf, Continue, and various open-source autonomous agent frameworks that implement the Model Context Protocol client specifications.
The majority of MCP servers are open-source and free to run locally. However, some servers interface with third-party commercial APIs, cloud providers, or proprietary platforms that require paid subscriptions or API keys.
Developers can submit a server by providing its repository link, documentation, supported transport protocols (stdio or SSE), license type, and category classification through the FastPedia submission form.
Listings are ranked using objective criteria, including repository maintenance activity, implementation completeness, documentation quality, community usage signals, and protocol compliance.
MCP servers execute locally with the permissions of the host environment. Users should inspect server source code, verify required file system and network privileges, and configure client-side approval prompts before granting execution rights.