Plunk MCP
Plunk is an open-source, self-hostable email platform. Its official Node SDK only exposes track and send. The rest of the API (workflows, segments, templates, analytics) is reachable over HTTP but never made it into the SDK, which means Claude couldn’t reach it either.
Plunk MCP closes that gap. It’s a Model Context Protocol server that exposes 84 tools across the full Plunk API, so Claude (or any MCP client) can build campaigns, manage contacts, wire up workflows, and pull analytics directly.
It’s free, open source, and unaffiliated with Plunk. Built and maintained by Ignyte.
Who it’s for
Section titled “Who it’s for”- You self-host Plunk (or use useplunk.com) and want Claude to operate it for you.
- You’re sending transactional email from an app and would rather have Claude verify addresses, fire events, or chase down deliverability issues than wire up another dashboard.
- You manage multiple Plunk projects and want one assistant that can switch between them.
What’s in the box
Section titled “What’s in the box”84 tools across 11 categories:
| Category | Tools | What it covers |
|---|---|---|
| Transactional | 3 | Sending, event tracking, email verification |
| Contacts | 18 | CRUD, bulk import/subscribe/unsubscribe, custom fields |
| Campaigns | 10 | Full lifecycle: create, send, cancel, test, stats |
| Segments | 10 | Dynamic and static segments, member management |
| Templates | 7 | Reusable templates for sends, campaigns, workflows |
| Workflows | 16 | Steps, transitions, executions: the automation builder |
| Events | 6 | History, stats, names, usage |
| Domains | 4 | Add, verify, delete sending domains |
| Activity | 5 | Activity feed, upcoming sends |
| Analytics | 4 | Timeseries, top campaigns, top events |
| Uploads | 1 | Image uploads for templates and campaigns |
Tools are namespaced plunk_<verb>_<resource> and every one has a typed input schema, so Claude knows exactly what to pass without guessing.
Capability detection
Section titled “Capability detection”At startup the MCP probes one endpoint per category and only registers tools whose category responds. On older useplunk/plunk releases, missing features are simply hidden, so Claude won’t confidently call endpoints that don’t exist on your instance.
Install
Section titled “Install”The full install steps, configuration, and tool reference live in the README:
→ github.com/ignytehq/plunk-mcp
The short version: add an entry to ~/.claude.json (or your Claude Desktop config) pointing at npx -y @ignytehq/plunk-mcp with PLUNK_API_KEY and PLUNK_API_URL set, then restart Claude.
Requirements
Section titled “Requirements”- The active Plunk codebase:
useplunk/plunk, distributed asghcr.io/useplunk/plunk. Self-hosted or on useplunk.com. - Node.js ≥ 18 if running from source.
- The legacy
driaug/plunkimage is not supported. The README has a migration walk-through.
License & support
Section titled “License & support”MIT licensed. Issues and PRs welcome on GitHub. Unofficial, not affiliated with Plunk.