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 descriptions, licences and links are read from each package's own registry (npm, PyPI, crates.io, NuGet, RubyGems; Go and Maven packages are only checked to exist), and packages the registry no longer has are removed. 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.
-
linewhizgithub.com/kinzen-dev/linewhizupdated this year
Premium MCP server for AI-powered LINE Official Account management
pypi MIT -
L Harness — self-hosted LINE Official Account CRM: step messaging, broadcasts, forms and reservations, with MCP and TypeScript SDK. By Shudesu (野田修一).
go MIT ★ 617 -
Talk to your LINE Official Account through AI — broadcasts, Flex & tappable Rich Messages, Thai-ready rich menus, coupons, insights, LINE Shopping. New in 2.2: attach a picture, say send — zero hosting setup, verified before success. 51 tools (37+14), multi-OA. Works with Claude Cowork, Claude Code, Cursor, Codex & any MCP host.
npm MIT ★ 102 -
MCP server for interacting with your LINE Official Account
npm Apache-2.0 -
agenza-line-bot-mcpgithub.com/your-username/agenza-line-bot-mcpupdated this year
MCP server for interacting with LINE Official Account (Core features only - optimized for low memory)
npm Apache-2.0 -
MCP server that integrates the LINE Messaging API to connect an AI Agent to the LINE Official Account.
npm Apache-2.0 ★ 807 -
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