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
206
Tools
545
Categories
11
Contributors
182
Official Docker MCP server for container management. Enables AI agents to list, start, stop, and inspect Docker containers, manage images, view logs, and execute commands inside running containers. Supports Docker Compose operations for multi-container applications and provides container health monitoring capabilities.
HashiCorp's official MCP server for Consul, providing integration with the Consul API for service discovery, configuration management, and service mesh operations. Lets AI agents list registered services and their health, read and write KV configuration entries, and inspect mesh intentions and config entries.
A Model Context Protocol server for HashiCorp Nomad that lets AI agents inspect and operate a Nomad cluster. Supports listing jobs, allocations, and nodes, reading allocation logs, and submitting or stopping jobs, which helps with debugging scheduling issues and running day-to-day workload operations.
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.