MARM
Provides protocol-based memory management for AI to improve response accuracy, reduce drift, and stabilize context over long sessions.
Browse 6,627+ Model Context Protocol servers for Claude, Cursor, and VS Code. Find the perfect tools for your AI workflow.
Provides protocol-based memory management for AI to improve response accuracy, reduce drift, and stabilize context over long sessions.
Maintains an ever-growing list of open source MCP servers.
Connect to various Model Context Protocol (MCP) servers and AI models through a unified command-line interface.
Orchestrates experimental, small-scale engineering agents with multi-provider LLM support for comparative evaluation.
Extends the capabilities of MCP-enabled LLM AI applications with various servers implemented in Java using the Quarkus framework.
Provides accurate Rust code suggestions for AI assistants by fetching current crate documentation and using LLMs to provide context.
Enables Java and Spring applications to interact with AI models and tools through the Model Context Protocol.
Enables voice-controlled AI workflows using Google Gemini and the Model Control Protocol.
Analyzes code using tree-sitter to provide context-aware code understanding for AI assistants.
Provides an interface between AI assistants and Tripo AI for generating 3D assets using natural language.
Provides Model Context Protocol (MCP) servers for integrating AI assistants with various applications.
Enables AI models to access and retrieve technical documentation from various agent frameworks.
Allows AI agents to request human intervention when uncertain, preventing hallucinations and improving accuracy.
Connect AWS FinOps capabilities to an AI assistant for cloud cost analysis, waste auditing, and budget insights using natural language.
Protects AI applications by automatically scanning and blocking malicious Model Context Protocol (MCP) traffic.
Connects Dify to external MCP servers, enabling LLMs to use their tools and resources within Dify workflows.
Provides up-to-date documentation for thousands of libraries directly within your AI code editor via the Model Context Protocol.
Enables interaction with the Dynatrace observability platform directly within development workflows.
Enables AI-powered coding tools to access Feishu documents via a Model Context Protocol server.
Manages personal knowledge, daily notes, and reusable prompts through GitHub Gists, accessible via MCP-enabled AI products.
Enables AI models to control and automate tasks within the Hangul Word Processor (HWP).
Provides a Model Context Protocol (MCP) server that offers tools for interacting with JMAP (JSON Meta Application Protocol) email servers.
Enables Make scenarios to be utilized as callable tools by AI assistants.
Integrate Model Context Protocol (MCP) servers into applications, providing access to a growing ecosystem of specialized AI capabilities.
MCP (Model Context Protocol) servers are tools that connect AI assistants like Claude, Cursor, and other AI coding tools to external data sources, APIs, and services. They enable AI models to access real-time information, execute code, interact with databases, and perform actions beyond their base capabilities. Check out our curated collection of the best MCP servers for Cursor →
MCP servers act as intermediaries between AI assistants and external systems. When you ask Claude or Cursor to perform a task requiring external data, the MCP server handles the request, fetches the data, and returns it in a format the AI can understand and use.
When selecting an MCP server, consider:
For detailed setup guides, see our Complete MCP Server Setup Guide →
Everything you need to know about installing, using, and troubleshooting Model Context Protocol.
To install MCP servers in Cursor: 1) Open Cursor settings (Cmd+,), 2) Navigate to MCP Servers section, 3) Click 'Add Server', 4) Enter server configuration (name and command), 5) Restart Cursor. Check out our curated collection of the best MCP servers for Cursor with detailed setup guides.
MCP servers are protocol-level integrations that work across multiple AI assistants (Claude, Cursor, etc.), while VS Code extensions are editor-specific. MCP servers provide context to AI models, whereas extensions add IDE functionality. MCP is more portable and AI-focused.
Most MCP servers listed are open-source and free. Some enterprise connectors (like Salesforce or Jira) may require paid API access to the underlying service, but the MCP server code itself is usually free.
Yes! The Model Context Protocol is open standard. You can build servers in Python or TypeScript/Node.js to expose your own internal APIs or databases to Claude and Cursor.
An MCP server is a lightweight program that exposes specific capabilities (data access, tool execution, prompts) to AI assistants through a standardized protocol. MCP servers allow Claude and other AI models to securely interact with external systems like databases, APIs, file systems, and web services while maintaining security boundaries.
MCP servers connect to Claude Desktop or other MCP-compatible clients through a standardized JSON-RPC protocol. When you configure an MCP server in Claude Desktop, Claude can access its resources (data/content), use its tools (functions to execute), and leverage its prompts (templated interactions). The protocol ensures secure, controlled access to external capabilities.
Essential MCP servers for beginners include: Filesystem (local file access), SQLite/PostgreSQL (database queries), GitHub (repository access), Brave Search (web search), and Memory (persistent context). These cover common use cases and have excellent documentation. Start with 2-3 servers and expand based on your needs.
Most MCP servers install via npm (npx) or Python (uvx/pip). Configure them in Claude Desktop's config file (claude_desktop_config.json) by specifying the command, arguments, and any required environment variables like API keys. Our directory links to each server's documentation with specific installation instructions.
MCP servers run locally on your machine with explicit permissions you configure. They can only access resources you authorize, and Claude cannot bypass these boundaries. However, always review server code, use official/verified servers when possible, limit permissions to what's necessary, and be cautious with servers that request broad access.
Resources are data sources Claude can read (files, database results, API responses). Tools are functions Claude can execute (run queries, send messages, create files). Prompts are pre-defined templates for common interactions. Most MCP servers expose one or more of these capability types.
MCP is supported by Claude Desktop (official), Cursor IDE, Continue (VS Code extension), and various community implementations. The protocol is open, so support is expanding to more AI development tools. Check our compatibility filters to find servers tested with your preferred client.
Our MCP servers directory is updated weekly with new servers, documentation improvements, and compatibility updates. We monitor GitHub releases, community contributions, and Anthropic announcements to ensure our listings reflect the latest MCP ecosystem developments.