MCP servers that ship as code — a repository or a package you install and run locally (usually over stdio). They have no hosted endpoint, so we cannot probe or grade them: instead each one shows its repository, install command, license, stars and when it was last updated.
Collected from GitHub repositories and npm, PyPI, Cargo, Go, Maven, NuGet and RubyGems packages tagged as MCP servers, the official MCP Registry, Docker's MCP catalog, ModelScope, Baidu MCP World, Cline and other public directories; one entry per repository. Each candidate is checked by a language model from its name, description and topics, and only actual MCP servers are listed (not clients, SDKs, lists or skills). Package metadata comes from ecosyste.ms (CC BY-SA 4.0). A server that also offers a hosted endpoint is listed under Remote instead. These entries are not counted in our reachability, verification or readiness statistics.
-
Open-source customer messaging for teams with many products: e-mail, live chat and in-app conversations in one inbox, plus newsletters, cookieless analytics, status pages, a help center, a roadmap and a changelog. MCP server for AI assistants. Pre-alpha.
go AGPL-3.0 ★ 30 -
Deliver messages an app queued on an MCP outbox, on a schedule, with no model in the loop.
npm MIT -
Checks every claim in a coding agent's "done" message against what actually ran: backed, contradicted or never ran. Web app and MCP server.
MIT -
MCP server for reading, searching and sending Google Chat messages through your own signed-in browser session. No Google API or OAuth app needed.
npm MIT -
Open-source workspace of pages, databases, team messages and your email, with realtime collaboration, AI chat and agents, and a built-in MCP server for AI assistants. Run it on your own server, or on your computer with the desktop app for macOS, Windows and Linux.
AGPL-3.0 ★ 5 -
Mailcycleno update data
An email address for your AI agent. Mailcycle lets an agent read, wait for and reply to mail at its own addresses: sign-up codes, verification links, support threads, attachments. Mail is decrypted on the machine running the agent. Mailcycle stores it sealed and can't read it. Needs a [Mailcycle](https://mailcycle.email/agents/) account on Scale or above, and Node 20 or later. ## Before you install: pair the agent On the machine the agent runs on: ```sh npx -y mailcycle-mcp pair --name "Support agent" ``` It prints a line starting with `MC1:`. In the Mailcycle app, open **AI agents**, paste the line, and give the agent an email address. The line carries the key the agent's mail is sealed to, so keep it private. It goes from your terminal to the app and never through Mailcycle. The server needs no other settings. It reads the key that pairing saved. ## Tools | Tool | What it does | |---|---| | `list_addresses` | The agent's addresses, and what it may send. | | `list_messages` | The newest messages, with a preview of each. | | `read_message` | One message in full, with its attachments numbered. | | `read_attachment` | Opens an attachment: text as text, images as images, anything else saved to a folder. | | `wait_for_message` | Waits for new mail, optionally from a sender or with a subject. Good for sign-up codes and verification links. | | `reply` | Replies to the sender of a message, threaded. Can attach files. | | `send_message` | Sends a new message, if the agent may send to anyone. Can attach files. | ## Sending Each agent has a send mode, set in the app: - **Reply only** (the default): it can answer whoever wrote to it, and no one else. - **Send to anyone**: up to 20 messages an hour per agent. - **Read only**: it cannot send. Mail an agent reads can contain instructions written by whoever sent it. Reply only limits what those can make it do. ## What sees what - **Mailcycle** stores mail sealed to keys it doesn't have. - **Your machine** holds the agent's key in `~/.config/mailcycle/agent.json`, readable only by your user. Remove the agent in the app to cut it off. - **Your model provider** sees whatever the agent reads. Also on npm as [`mailcycle-mcp`](https://www.npmjs.com/package/mailcycle-mcp) and the [official MCP Registry](https://registry.modelcontextprotocol.io) as `email.mailcycle/mailcycle`. Proprietary, © 2026 Northlab Studios Ltd. [Terms](https://mailcycle.email/legal/terms/).
smithery -
The wuapi command line: log in from the browser, link a WhatsApp number through a link the person opens (QR or pairing code), run your app with the key, send messages, set up the MCP server and call every endpoint of the wuapi API from your terminal or yo
npm MIT -
mailbot: email for AI agents. Chat apps now bill every automated reply and bar open-ended AI assistants; email has no single owner. Give your agent an inbox, send, read replies in-thread, check every message's state. API, SDKs, MCP (12 tools).
★ 5 -
TelegramMCPVSCodegithub.com/darkclad/TelegramMCPVSCodeupdated this year
Rust MCP server exposing a Telegram bot to LLM clients over stdio: send messages, and log incoming ones to a searchable SQLite history. Includes tg-hook, a Claude Code hook that relays finished turns and AskUserQuestion prompts to Telegram — so you can answer Claude from your phone, then return to the keyboard and the in-app dialog takes over.
-
@iflow-mcp/hackle-mcpstale
Model Context Protocol server for Hackle
npm -
@hackle-io/hackle-mcpupdated this year
Model Context Protocol server for Hackle
npm -
Lets AI apps on this computer use Glaze in your browser.
npm MIT -
Desktop client for Apache Kafka and RabbitMQ — browse topics & queues, produce/consume, manage consumer groups, schemas and connectors, with built-in terminal tabs and an MCP server for Claude Code. Electron + TypeScript.
Apache-2.0 ★ 2 -
Secure LAN chat in one binary: channels, DMs, files and emoji over HTTPS with a built-in CA. Apps and netdiag post alerts via webhooks, bots and MCP.
Apache-2.0