addy-mcp
An MCP server that lets Claude (and other MCP clients) manage your account: aliases, recipients, usernames, custom domains, labels, rules, the blocklist and failed deliveries. It covers the full .
Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
uvx addy-mcp==0.1.2Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
ADDY_API_KEY=<secret> ADDY_API_KEY_FILE=<value> ADDY_READ_ONLY=<value> ADDY_BASE_URL=<value> claude mcp add io.github.former-stranger-addy-mcp -- uvx addy-mcp==0.1.2รันในเทอร์มินัล
{ "mcpServers": { "io.github.former-stranger-addy-mcp": { "command": "uvx", "args": [ "addy-mcp==0.1.2" ], "env": { "ADDY_API_KEY": "<secret>", "ADDY_API_KEY_FILE": "<value>", "ADDY_READ_ONLY": "<value>", "ADDY_BASE_URL": "<value>" } } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
An MCP server that lets Claude (and other MCP clients) manage your account: aliases, recipients, usernames, custom domains, labels, rules, the blocklist and failed deliveries. It covers the full .
Manage addy.io email aliases, recipients, domains, rules and blocklist.
Unofficial. This project is not affiliated with or endorsed by addy.io.
It runs on your own computer with your own API key. Nothing is hosted, and your key is only ever sent to addy.io.
In addy.io go to Settings → API Keys (https://app.addy.io/settings/api) and click Create New API Key. Consider giving it a name like "Claude" and an expiry date.
addy-mcp-<version>.mcpb from the Releases page.Requires uv. Open Settings → Developer → Edit Config and add:
{
"mcpServers": {
"addy": {
"command": "uvx",
"args": ["addy-mcp@latest"],
"env": {
"ADDY_API_KEY": "paste-your-api-key-here"
}
}
}
}
Then fully quit and reopen Claude Desktop. If it can't find uvx, replace "uvx" with the full path from which uvx (macOS/Linux) or where uvx (Windows). Desktop apps don't always see your shell's PATH.
claude mcp add addy --scope user --env ADDY_API_KEY=paste-your-api-key-here -- uvx addy-mcp@latest
This makes the server available in Claude Code (the CLI and the desktop app's Code tab). Claude Desktop's chat uses a separate config, set up above.
Run uvx addy-mcp@latest as a stdio server with ADDY_API_KEY set in its environment.
@latest makes uvx check PyPI for a new release each time the server starts. Leave it off and uvx keeps using whichever version it first downloaded. To stay on a specific version instead, use e.g. addy-mcp==0.1.1.
The setup above keeps the key in plain text in your MCP client's config file. That's the usual approach for local MCP servers, but you can do better:
Claude Desktop extension: the .mcpb install stores the key encrypted. Nothing else to do.
macOS Keychain (Claude Code and other clients): keep the key in the Keychain and fetch it only when the server starts, so it's never written to a config file. Add the key (you'll be prompted for it, so it doesn't end up in your shell history):
security add-generic-password -a "$USER" -s addy-mcp -w
Then add the server with a small wrapper instead of --env:
claude mcp add addy --scope user -- /bin/sh -c 'ADDY_API_KEY="$(security find-generic-password -a "$USER" -s addy-mcp -w)" || exit 1; export ADDY_API_KEY; exec uvx addy-mcp@latest'
If the server fails to start because uvx isn't found, replace uvx with its full path from which uvx.
On Linux, the same pattern works with secret-tool store --label=addy-mcp service addy-mcp and secret-tool lookup service addy-mcp. With 1Password, use op read "op://<vault>/<item>/credential" in place of the security command.
Key file: set ADDY_API_KEY_FILE to a file that only you can read (chmod 600), or to a Docker or Kubernetes secret mount.
VS Code: let VS Code prompt for the key and keep it in its secret storage:
{
"inputs": [
{ "type": "promptString", "id": "addy-api-key", "description": "addy.io API key", "password": true }
],
"servers": {
"addy": {
"type": "stdio",
"command": "uvx",
"args": ["addy-mcp@latest"],
"env": { "ADDY_API_KEY": "${input:addy-api-key}" }
}
}
}
Whichever you choose, use a separate addy.io key for each app or device, so you can revoke one without breaking the others, and give it an expiry date.
addy-mcp@latest (the commands above): restart Claude (or your MCP client) and the newest release is picked up automatically.uvx addy-mcp: uvx keeps using the version it first downloaded. Change addy-mcp to addy-mcp@latest in your config and restart Claude..mcpb): download the new .mcpb from the Releases page and install it the same way. Your API key and settings are kept, so you won't be asked for them again.To see which version is newest, run uvx addy-mcp@latest --version (available from 0.1.1). To hear about new releases, watch the repo on GitHub (Watch → Custom → Releases). Changes are listed in the changelog.
Every tool is labelled read-only, write, or destructive (MCP tool annotations), so clients like Claude can ask before running anything risky. Deleting an alias can be undone with restore_alias. Forgetting an alias is permanent.
ADDY_BASE_URL). It has no telemetry.ADDY_READ_ONLY if you only want Claude to look things up.git clone https://github.com/Former-Stranger/addy-mcp
cd addy-mcp
uv run --no-editable python -m pytest # unit tests (mocked HTTP, never touch a real account)
uv run ruff check && uv run ruff format --check
scripts/live_test.py exercises the server against a real account: it creates, updates, deletes, restores and finally forgets a throwaway alias and label. Run it with ADDY_API_KEY=... uv run --no-editable python scripts/live_test.py --yes.
--no-editable: on some macOS setups files in .venv get the "hidden" flag, and Python 3.13+ ignores hidden .pth files, which breaks editable installs. A regular install sidesteps that.
version in pyproject.toml, run uv run python scripts/sync_metadata.py, and update CHANGELOG.md.git tag v0.2.0 && git push origin v0.2.0.pypi deployment when GitHub asks (the release pauses until a maintainer approves it).The release workflow publishes to PyPI, attaches the .mcpb bundle to a GitHub release, and updates the MCP Registry listing.
A weekly workflow compares the addy.io API docs with scripts/addy_api_snapshot.txt and opens an issue when the API changes. After updating the tools, refresh the snapshot with python3 scripts/check_api_docs.py --update. Dependabot opens weekly pull requests for dependency and GitHub Actions updates.
Manage addy.io email aliases, recipients, domains, rules and blocklist.
{ "mcpServers": { "io.github.former-stranger-addy-mcp": { "command": "uvx", "args": [ "addy-mcp==0.1.2" ], "env": { "ADDY_API_KEY": "<secret>", "ADDY_API_KEY_FILE": "<value>", "ADDY_READ_ONLY": "<value>", "ADDY_BASE_URL": "<value>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: ADDY_API_KEY, ADDY_API_KEY_FILE, ADDY_READ_ONLY, ADDY_BASE_URL
Addy.io ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-09 Manage addy.io email aliases, recipients, domains, rules and blocklist.