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
Provides access to the Slack API through the Model Context Protocol. Enables AI agents to read and send messages, manage channels, search conversation history, and interact with Slack workspaces. Supports listing channels, reading threads, posting messages, and adding reactions programmatically. Originally maintained by Anthropic, now maintained by Zencoder.
A Model Context Protocol server that enables AI agents to interact with Discord through a bot. Agents can send and read messages in channels, list servers and channels, and manage basic server interactions while keeping the user in control. Useful for community automation, notifications, and conversational workflows on Discord.
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.