Discourse MCP CLI server (stdio) exposing Discourse tools via MCP
877 MCP servers
Feishu/Lark OpenAPI MCP
MCP Server for UI Library and ChatKit component discovery tools.
Telegram on your own account: read, search, send and press bot buttons. Writes need your approval.
Let AI agents notify you on Slack, Telegram, email, SMS, or push via an Alphorn webhook.
MCP server for interacting with your LINE Official Account
Microsoft Teams for Claude — read your chats, teams, channels, and open messages, via your browser
Automated DOCX Redlining Engine
MCP server for Microsoft Teams - search messages, send replies, manage favourites
A lightweight, multi-guild Discord MCP server with 95+ tools
Group chat for people and AI agents: join a room by invite link, read, reply, whisper, wait.
Official MCP server for Sinch communication services.
MCP server daemon for ours — one native ADAPT wrapper hosting N self-sovereign identities, exposing secure agent-to-agent messaging tools
A TypeScript implementation of a simple MCP server that exposes datetime information to agentic systems and chat REPLs
MCP server for Slack — read/write messages, manage threads, and react to messages.
This is a Model Context Protocol server that exposes all of Twilio APIs.
Read Messages history on macOS and send or reply through Messages.app.
WhatsApp for your agent: chats, messages, media, contacts and groups behind MCP tools.
MCP (Model Context Protocol) server for operating Chatwork from AI
Catch up on Slack without reading it. Unreads, threads, search. Browser-session or hosted OAuth.
MCP server for Telegram userbot — messages, media, reactions, polls & more. Built on GramJS/MTProto.
Communication & Collaboration MCP servers on mcprush send and read messages — chat, email, SMS — on rails that make an outbound message a deliberate act rather than a side effect of a tool call.
What to look at before installing one is what stands between the agent and a message a customer receives. Where a listing has an approval gate it is a tool on the surface, not a promise in the description. Every server here names the publisher behind it and whether that publisher has been verified, the runtime it uses, how it authenticates, the tool surface it exposes and the price model it is sold under — and where a security scan has been run against it, what the scan found. The filters on the left narrow it further and the sort at the top decides what comes first.
Nearly every server in this catalogue is connected straight to its publisher: the listing gives the publisher’s own address or start command, and mcprush is not in the path, so nothing is routed, metered or billed here. The exception is a server delivered through the mcprush gateway — there one key covers everything installed against your account, the calls are metered where you can see them and the ceiling on what they may cost is yours to set, and installing it is a line of the mcprush CLI: npx mcprush@latest add, followed by the server’s id. The listing says which of the two it is before you install anything.