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
Integrates Twilio communication APIs with AI agents through the Model Context Protocol. Enables sending SMS messages, making voice calls, managing phone numbers, and querying message history. Supports programmable messaging, conversation management, and webhook configuration for real-time communication workflows.
MCP server for Zendesk Support. Lets AI agents search and read tickets, add comments and replies, update ticket status and fields, and query help-center articles. Useful for building support copilots, triaging and summarizing tickets, and drafting grounded responses from an AI assistant.
MCP server for Intercom. Lets AI agents search and read conversations and contacts, retrieve message history, and query help-center articles via the Intercom API. Useful for support analytics, conversation summarization, and building assistants that reason over customer communications.
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.