PostgreSQL Operations
Provides professional, read-only operations and monitoring for PostgreSQL databases, offering performance insights, structure visibility, and configuration details.
Browse 6,627+ Model Context Protocol servers for Claude, Cursor, and VS Code. Find the perfect tools for your AI workflow.
Provides professional, read-only operations and monitoring for PostgreSQL databases, offering performance insights, structure visibility, and configuration details.
Serves as an interface between desktop applications and the PostHog platform, facilitating access to analytics and feature flags.
Enables searching and querying of the PubMed medical research database through the Entrez API.
Bridges AI assistants with StarRocks databases, enabling direct SQL execution and database exploration.
Connects 230+ data sources to AI for natural language data analysis.
Enables AI assistants to interact with HubSpot CRM data, leveraging vector storage and caching for improved performance.
Serves Tesla vehicle data and analytics from a TeslaMate database to AI assistants via the Model Context Protocol.
Enables Language Models (LLMs) to seamlessly connect to and retrieve data from various databases through a unified API.
Enables AI to perform data analysis on various database types (SQLite, MySQL, PostgreSQL, etc.) through a unified and secure connection configuration.
Executes MySQL database queries and streams the results via Server-Sent Events (SSE).
Provides safe, read-only access to SQLite databases for exploration and querying by Large Language Models (LLMs).
Enables AI applications to access and query databases using the Legion Query Runner with Model Context Protocol (MCP) integration.
Provides a Model Context Protocol (MCP) server for streamlined PocketBase database interactions.
Enables database introspection, management, and interaction with self-hosted Supabase instances from development environments using the Model Context Protocol.
Provides AI assistants with task management and agent memories capabilities using project-specific storage.
Provides advanced access to the ChEMBL chemical database through a Model Context Protocol (MCP) server.
Provides safe access to your iMessage database through the Model Context Protocol (MCP).
Captures user intentions and behavior patterns for MCP server analytics, eliminating guesswork and accelerating product development.
Enables searching and fetching of articles from the PubMed database.
Manage Appwrite project resources including databases, users, functions, and teams through an intelligent Model Context Protocol server.
Enables natural language querying of PostgreSQL databases using Ollama's LLM and the Model Context Protocol.
Provides comprehensive tools for interacting with PocketBase databases, enabling advanced database operations, schema management, and data manipulation through the Model Context P…
Enables interaction with a Nocodb database using the Model Context Protocol (MCP) to facilitate CRUD operations on Nocodb tables.
Integrates with The Movie Database (TMDB) API to provide movie information, search capabilities, and recommendations within Claude Desktop.
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.