Claws Mail Mcp Plugin

io.github.it-atelier-gnPublished by GitHub account it-atelier-gnv1.0.2Updated Oct 24, 2026

Claws Mail plugin exposing the running mail client over a local, bearer-token MCP endpoint.

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

A native Claws Mail plugin that exposes the running mail client over a loopback-only, bearer-token-protected MCP endpoint so an assistant can read, search and…

What you can do
  • Read folders and messages from the configured Claws Mail accounts
  • Search mail across folders
  • Compose, reply and forward messages
  • Manage folders and message flags
  • Send and receive mail through the already-configured accounts
  • Report plugin version and status
When to use it
Use it when you run Claws Mail on the same desktop and want an AI assistant to triage, search, draft and send mail through your existing accounts without separate credentials.
Requirements
A desktop Claws Mail installation with the matching prebuilt plugin binary (or a build from source with Meson, Ninja, a C compiler and the Claws Mail development files) loaded via Configuration > Plugins. The endpoint, port, token and read-only mode are set in mcp_pluginrc in the Claws Mail config directory; the client config with URL and token is written to mcp_client.json. The server listens on 127.0.0.1 only, so the AI tool must run on the same machine.
Before you install
The bearer token in mcp_client.json grants access to your mailbox; keep it private and avoid committing it. The plugin can compose, reply, forward, send and receive mail and change folders and flags, so an assistant can act on your real accounts; enable read-only mode if you only want reading. Do not use the Claude Desktop custom connector flow, which cannot reach a loopback address.

Installation

In SourceWeft

  1. Open Claws Mail Mcp Plugin in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

claws-mail-mcp-plugin

[CI] [Claws Mail] [License: GPL v3+]

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.

Installing the plugin

Prebuilt binaries are attached to each release, one per OS and supported Claws Mail version (e.g. mcp-linux-claws4.3.1.so, mcp-windows-claws4.3.0.dll). Pick the file matching your Claws Mail version and OS, then:

  1. Save it in a folder of your choice, for example ~/.claws-mail/plugins or %APPDATA%\Claws-mail\plugins on Windows, as mcp.so or mcp.dll. Any file name works except one ending in _plugin.so or _plugin.dll: Claws Mail does not load such a file on startup and drops it from the plugin list.
  2. In Claws Mail, open Configuration > Plugins, click Load... and select the file.

Claws Mail loads the plugin again on every start.

To build from source instead, see Building.

Connecting an AI tool

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 Code

claude mcp add --transport http claws-mail http://127.0.0.1:8765/mcp \  --header "Authorization: Bearer <TOKEN>"

Claude Desktop

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.

VS Code / GitHub Copilot Chat

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.

Codex CLI

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.

MCP registry

The plugin is listed in the MCP registry as io.github.it-atelier-gn/claws-mail-mcp-plugin. The listing carries no connection details; install the plugin and connect your tool as described above.

Building

Requires Meson, Ninja, a C compiler, and the Claws Mail development files (GTK3, GLib, GnuTLS, libgcrypt; on Linux also enchant).

Linux

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.shexport PKG_CONFIG_PATH="$PWD/.claws-sdk/lib/pkgconfig"

Then configure and build:

meson setup buildmeson compile -C buildmeson test -C build

The plugin is built at build/mcp.so.

Windows (MSYS2)

Install the MINGW64 toolchain and dependencies:

pacman -S mingw-w64-x86_64-gcc mingw-w64-x86_64-meson mingw-w64-x86_64-ninja \  mingw-w64-x86_64-pkgconf mingw-w64-x86_64-gtk3 mingw-w64-x86_64-glib2 \  mingw-w64-x86_64-gnutls mingw-w64-x86_64-libgcrypt

Build the Claws Mail SDK and set PKG_CONFIG_PATH as above, then run the same meson setup / meson compile / meson test commands. The plugin is built at build/mcp.dll.

Plugin version

The version compiled into the binary (returned by plugin_version and the status tool) comes from -Dplugin_version, e.g.:

meson setup build -Dplugin_version=1.2.3

CI sets this from the pushed git tag on release builds. Without it, the build falls back to git describe, then to 0.0.0-dev.

Installing

meson install -C build

This installs the plugin into the Claws Mail plugin directory reported by pkg-config --variable=plugindir claws-mail. Load it from there once under Configuration > Plugins > Load...

Supported Claws Mail versions

Each release contains a Linux and a Windows build for every Claws Mail version listed in ci/claws-versions.json.

License

GPL-3.0-or-later, see LICENSE.

Source: README.md at commit acb712f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.2LatestOct 22, 2026
  2. v1.0.1Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts