Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Claws Mail plugin exposing the running mail client over a local, bearer-token MCP endpoint.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
The maker has not listed install details in the registry. See the maker’s README below.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account it-atelier-gn, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.2) reached the registry 17 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code.
In the same category: Spec Driven Development, Remote Desktop Commander, SolveHub
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
CAPTCHA and anti-bot solving for Turnstile, DataDome, Akamai, PerimeterX and Imperva.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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-linux-claws4.3.1.so, mcp-windows-claws4.3.0.dll). Pick the file matching your Claws Mail version and OS, then:
~/.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.Claws Mail loads the plugin again on every start.
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 "
Settings > Developer > Edit Config, then merge in packaging/claude/mcp.json (fill in ). 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.
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.
Requires Meson, Ninja, a C compiler, and the Claws Mail development files (GTK3, GLib, GnuTLS, libgcrypt; on Linux also 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="$PWD/.claws-sdk/lib/pkgconfig"
Then configure and build:
meson setup build
meson compile -C build meson test -C build
The plugin is built at build/mcp.so.
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.
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.
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...
Each release contains a Linux and a Windows build for every Claws Mail version listed in ci/claws-versions.json.
GPL-3.0-or-later, see LICENSE.