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?
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.
Plunk also publishes a REST API
Plunk publishes an API, but per-tier gating wasn't extracted automatically.
See Plunk API pageWhat 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.
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
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
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
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.
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.
Scored 2026-05-21 by Joonas (TMB).
Plunk MCP & API FAQ
Is the Plunk MCP server official?+
Can I use the Plunk MCP with Cursor or Codex?+
Does Plunk have a public API?+
Sources
- Plunk official site: https://www.useplunk.com
- MCP server page: https://github.com/ignytehq/plunk-mcp
- API docs: https://docs.useplunk.com
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.

