That Marketing Buddy
Home/MCP/Plunk
Plunk

Plunk MCP Server

Yes. Plunk has a community-built MCP server, hosted at github.com/ignytehq/plunk-mcp.

COMMUNITY MCP✓ alivePublic API
MCP status verified 2026-05-21Agent-readiness 4/10
Data from Buddy's database, auto-rechecked weekly

What is the Plunk MCP server?

The Plunk MCP server lets Claude, Cursor, Codex, and other MCP-compatible clients query campaigns, contacts, segments, and automation workflows without leaving the editor. The server is community-built. Expect occasional drift from the source tool and check the README before depending on it for production agents.

Three things you actually do with it: ask Claude which segments are growing fastest this quarter, have Cursor draft a 3-step welcome series for new ebook signups, and let Codex re-engage cold subscribers with personalised subject lines.

Plunk also has a public REST API at docs.useplunk.com. Use the API for scheduled jobs and custom dashboards. Use the MCP server when an LLM is in the loop.

For the rest of the picture see the full coverage on this tool..

Live in your Claude / Cursor / Codex

What you actually do with the Plunk MCP

plunk-mcp
>What's the open rate on my last 5 campaigns?
plunk.list_campaigns({ limit: 5 })
LAST 5 CAMPAIGNS · OPEN RATE
Black Friday Teaser42.1%
Product launch38.5%
Weekly digest #1227.0%
Welcome flow step 261.3%
Re-engagement attempt9.8%
Suggest A/B subject lines for the bottom two?
plunk-mcp
>Build a 3-email welcome series for new ebook subscribers
plunk.create_automation({ trigger: "list_added" })
AUTOMATION CREATED · 3 EMAILS
Day 0ebook delivery + intro
Day 2case study + soft CTA
Day 5product demo + 14-day trial
Review drafts before activation?
plunk-mcp
>Which segments are growing fastest this quarter?
plunk.segment_growth({ period: "Q4" })
TOP 3 GROWING SEGMENTS
Trial → Paid converters+187%
EU subscribers+62%
Re-engaged churned+34%
TMB SCORE FOR PlunkMCP: CommunityAgent fit: 4/10
Read review →

Examples illustrative. Actual responses depend on your data and the Plunk MCP server's tool surface.

How to connect Plunk MCP to Claude Desktop

Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.

{
  "mcpServers": {
    "plunk": {
      "command": "npx",
      "args": ["-y", "<server-package-name>"],
      "env": {
        "PLUNK_API_KEY": "your-api-key-here"
      }
    }
  }
}
// Server source: https://github.com/ignytehq/plunk-mcp
// Check the server's README for the exact "command" and required env vars.

Some MCP servers require an API key. Check the source page for setup: github.com/ignytehq/plunk-mcp.

Does Plunk MCP cost extra?

Community (free)

The Plunk MCP server is community-built — free to run, but you still pay for your Plunk subscription.

  • Community MCPs are normally self-hosted from a GitHub repo. There's no extra license fee.
  • Your Plunk account still needs whatever plan is required to access the data the MCP server queries.
  • Trade-off: zero MCP cost, but no guarantee it'll keep working when Plunk changes their UI or API.
MCP cost
Free (self-hosted)
Subscription required
Yes (your tool plan)
Maintained by
Community

Plunk also publishes a REST API

Plunk publishes an API, but per-tier gating wasn't extracted automatically.

Auth method
SDK languages
OpenAPI spec
Webhooks
Structured outputs
See Plunk API page

What you can do with Plunk from an AI agent

Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.

INDIE / SOLO

Skip the dashboard, ask Claude

  • "What campaigns underperformed this week?" answered in seconds
  • Quick one-off questions without leaving the editor
  • Pipe Plunk data into your personal notes / docs without writing a script
Effort: 30 seconds — paste the config, restart Claude
AGENCY

Run client analysis at agent speed

  • Hand the MCP server to your team — every consultant can ask Claude about any client's Plunk account
  • Multi-account workflows without context-switching the Plunk UI
  • Reports you'd normally spend hours on, done before standup
Effort: An afternoon — set up auth per client
IN-HOUSE TEAM

Production agent workflows

  • Embed in your internal Codex / Cursor agents that triage Plunk data daily
  • Combine with other MCP servers in a multi-step agent chain
  • Constrain agents to read-only roles to keep production Plunk safe
Effort: Days — security review + role config

Limits and gotchas

  • Community MCP — not maintained by Plunk. Check the README and last-update date before depending on it.
  • Fallback: the REST API works for any flow the MCP server doesn't cover.
  • Rate limits: MCP calls count against your underlying Plunk API quota. Burst usage from a curious agent can drain a daily allowance fast.
4/10

Agent-readiness verdict

Weak agent-fit despite community MCP. Plunk has a public API with docs and a community-built MCP server, but lacks OpenAPI specs, official SDK support, and structured outputs that agents need for reliable integration. The absence of webhooks and native LLM integrations means you'll spend cycles on custom glue code.

MCP server availablePublic API with docs

Scored 2026-05-21 by Joonas (TMB).

Plunk MCP & API FAQ

Is the Plunk MCP server official?+
No — it's a community build, not maintained by Plunk. Expect occasional drift and check the README before depending on it for production agents.
Can I use the Plunk MCP with Cursor or Codex?+
Yes — MCP is a protocol, not Claude-specific. Any MCP-capable client (Cursor, Codex, Windsurf, Zed) can use the same server config with minor path adjustments.
Does Plunk have a public API?+
Yes — public REST API at docs.useplunk.com.

Sources

Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.