DocMCP
Indexes technical documentation on a local vector database and integrates with AI IDEs for semantic search.
Browse 6,627+ Model Context Protocol servers for Claude, Cursor, and VS Code. Find the perfect tools for your AI workflow.
Indexes technical documentation on a local vector database and integrates with AI IDEs for semantic search.
Indexes and provides semantic search for local documents using a vector database and local language models.
Extends AI assistants' knowledge by processing private documents and codebases into a searchable database.
Enables AI assistants to directly query databases through DreamFactory's auto-generated REST APIs.
Enables querying of AWS DynamoDB databases using natural language requests via the Model Context Protocol (MCP).
Facilitates Retrieval Augmented Generation (RAG) using LlamaIndex, Gemini embeddings, and LanceDB for local knowledge storage.
Provides a Model Context Protocol (MCP) server for deep financial document analysis and content extraction from the SEC EDGAR database.
Enables AI models to interact with PostgreSQL databases through a standardized protocol.
Enables LLMs to read, write, and manage schemas in PostgreSQL databases.
Provides large language models with access to the Ensembl genomics database for querying genomic data, gene information, sequences, and variants.
Integrates Exasol database knowledge with Large Language Models via the Model Context Protocol.
Enables AI models to interact with FalkorDB graph databases using natural language queries and commands.
Expose Fathom Analytics data to AI assistants through the Model Context Protocol.
Connects AI assistants directly to Firebase Realtime Database services.
Enables AI assistants to securely connect and interact with external Firebird databases for SQL query execution and data management.
Provides API access to the USDA's FoodData Central database via a Model Context Protocol (MCP) server.
Retrieves data from Google Analytics 4 to provide insights into website and app performance.
Enables secure, type-safe interaction with Azure Blob Storage via the open Model Context Protocol (MCP) for seamless file management.
Provides seamless integration with Google Cloud Storage, enabling AI assistants to perform file operations, manage buckets, and interact with GCS resources directly.
Provides a remote Model Context Protocol server with GitHub OAuth authentication and integrated analytics tracking.
Provides a robust Model Context Protocol (MCP) server implementation in Go, demonstrating analytics reporting capabilities and modern Go development practices.
Provides a Model Context Protocol (MCP) server for interacting with Postgres databases and automating database operations.
Retrieves and analyzes Google Analytics 4 data, providing business intelligence feedback via a Model Context Protocol server.
Interfaces with the Google Analytics Data API using a Model Context Protocol (MCP) server.
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.