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
195
Tools
516
Categories
11
Contributors
171
Official Elastic MCP server that connects AI agents to Elasticsearch data using the Model Context Protocol. Enables natural language interactions with Elasticsearch indices — querying, analyzing, and retrieving data without custom APIs. Supports both stdio and streamable-HTTP transports, and works with Elasticsearch 8.x/9.x clusters including Elasticsearch Serverless. Distributed as a Docker container image from the Elastic registry.
Official MCP server for interacting with MongoDB databases and MongoDB Atlas. Enables AI agents to query collections, run aggregations, manage indexes, inspect schemas, and perform CRUD operations. Also supports Atlas cloud management including cluster provisioning, database user management, performance advisor, and stream processing. Supports read-only mode for safe exploration.
A Model Context Protocol server that provides a natural-language interface for LLMs and agents to manage, monitor, and query data in CockroachDB. Supports schema exploration, query plan inspection, and running SQL, with a read-only-by-default posture so agents can investigate a distributed SQL cluster safely.
Community-supported MCP server from the Couchbase ecosystem that lets AI assistants interact with data in Couchbase clusters and Capella. Exposes tools to browse scopes and collections, run SQL++ (N1QL) queries, and read or modify documents, with authentication and safety controls enforced by the server. Useful for conversational data exploration and operational queries against Couchbase.
The official OpenSearch Model Context Protocol server, enabling AI assistants to interact with OpenSearch clusters. Lets agents list indices, inspect mappings, run search and aggregation queries, and read basic cluster health so they can explore and analyze data stored in OpenSearch through natural language.
Skills vs MCP servers
what’s the difference?Skillsthe “what to do”
A skill packages know-how — instructions, an example prompt, and recommended models — so an agent performs a task consistently. Skills add knowledge, not new connections.
MCP serversthe “how to connect”
An MCP server gives an agent new capabilities by connecting it to real systems (databases, APIs, files) over a transport. 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.