Claws Mail plugin exposing the running mail client over a local, bearer-token MCP endpoint.
MCPpedia last refreshed this data
io.github.it-atelier-gn/claws-mail-mcp-plugin is an MCP server that claws Mail plugin exposing the running mail client over a local, bearer-token MCP endpoint. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 39/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-it-atelier-gn-claws-mail-mcp-plugin": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Native Claws Mail plugin that exposes the running mail client as an MCP server.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in communication / cloud
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
Programmable email inbox for AI agents — JMAP, PoW auth, stdio MCP server.
MCP Server for GCP environment for interacting with various Observability APIs.
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1
MCP Security Weekly
Get CVE alerts and security updates for io.github.it-atelier-gn/claws-mail-mcp-plugin and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Native Claws Mail plugin that exposes the running mail client as an MCP server.
It runs inside Claws Mail and serves a local, loopback-only HTTP endpoint (JSON-RPC over MCP, bearer-token protected). Any MCP-capable AI tool can then read folders and messages, search, compose, reply, forward, manage folders and flags, and send or receive mail through your already-configured accounts. Endpoint, port, token and read-only mode are set in mcp_pluginrc inside the Claws Mail config directory; the plugin writes a ready-to-paste client config to mcp_client.json in the same place on every start.
Prebuilt binaries are attached to each release, one per OS and supported Claws Mail version (e.g. mcp_plugin-linux-claws4.3.1.so, mcp_plugin-windows-claws4.3.0.dll). Pick the file matching your Claws Mail version and OS, then:
pkg-config --variable=plugindir claws-mail, typically ~/.claws-mail/plugins or %APPDATA%\Claws-mail\plugins on Windows).To build from source instead, see Building.
Once loaded, the plugin writes the real endpoint URL and bearer token to mcp_client.json in the Claws Mail config directory. Use those two values with whichever method below matches your tool. The server is loopback-only (127.0.0.1), so it is reachable only from AI tools running on the same machine as Claws Mail.
claude mcp add --transport http claws-mail http://127.0.0.1:8765/mcp \
--header "Authorization: Bearer <TOKEN>"
Settings > Developer > Edit Config, then merge in packaging/claude/mcp.json
(fill in <TOKEN>). Do not use the "Add custom connector" UI for this server:
that flow connects from Anthropic's servers, not from your machine, so it
cannot reach a loopback address.
code --add-mcp "{\"name\":\"claws-mail\",\"type\":\"http\",\"url\":\"http://127.0.0.1:8765/mcp\",\"headers\":{\"Authorization\":\"Bearer <TOKEN>\"}}"
Or copy packaging/vscode/mcp.json to .vscode/mcp.json; it prompts for the
token instead of storing it in the file.
export CLAWS_MCP_TOKEN=<TOKEN>
codex mcp add claws-mail --url http://127.0.0.1:8765/mcp --bearer-token-env-var CLAWS_MCP_TOKEN
This matches packaging/codex/config.toml, which Codex reads from
~/.codex/config.toml.
packaging/registry/server.json is published to the MCP registry as io.github.it-atelier-gn/claws-mail-mcp-plugin on every tagged release, via .github/workflows/ci.yml's publish-registry job (GitHub OIDC auth, no stored credentials). The registry rejects loopback URLs as remotes, so this is a discovery-only listing without connection details; it links back to this README for installation and the per-tool commands above.
Requires Meson, Ninja, a C compiler, and the Claws Mail development files (GTK3, GLib, GnuTLS, libgcrypt, enchant).
Install dependencies (Debian/Ubuntu example):
sudo apt-get install build-essential meson ninja-build pkg-config \
libgtk-3-dev libglib2.0-dev libgnutls28-dev libgcrypt20-dev libenchant-2-dev
If a claws-mail pkg-config file is not already on your system, build one with:
PREFIX="$PWD/.claws-sdk" ci/build-claws-sdk.sh
export PKG_CONFIG_PATH
... [View full README on GitHub](https://github.com/it-atelier-gn/claws-mail-mcp-plugin#readme)