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 SonarQube MCP server that brings code quality and security analysis into AI workflows. Lets agents fetch project issues, security hotspots, quality-gate status, and metrics from SonarQube Server or SonarCloud, so code health can be inspected and triaged conversationally.
GitHub's official MCP Server that connects AI tools directly to GitHub's platform. Enables AI agents to manage repositories, issues, pull requests, branches, files, actions workflows, and code security. Supports both remote (OAuth) and local (Docker/binary) modes with fine-grained toolset configuration.
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.