PlugWiki
plunk logo

Plunk MCP Server: Setup for Claude, Cursor and Other Apps

OfficialLocal
Getnpm@plunk/mcpuseplunk/plunk

Lets Claude or Cursor send email, manage contacts, draft campaigns and build automation workflows in your Plunk project.

This is the official Plunk server, published as @plunk/mcp. It runs on your computer and talks to Plunk with a secret key from Settings, then API Keys, in your Plunk dashboard. It works with the hosted Plunk product and with a self-hosted one.

Your project's key can read and change everything in that project. The server asks you to confirm before it sends a campaign or emails more than one person, but a client that cannot show a prompt cannot send at all. Use a read-only setting or a separate Plunk project if you want a safe first try.

Good for

  • Developers who send transactional email through Plunk and want the assistant to check or send it
  • Marketers who draft and schedule campaigns without opening the dashboard
  • Teams that build email automations and want the assistant to wire up the steps
  • Self-hosters running their own Plunk instance

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install plunk MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the plunk MCP server to Claude Code. Run this command:
    
    claude mcp add plunk -e PLUNK_API_KEY=<PLUNK_API_KEY> -- npx -y @plunk/mcp
    
    Ask me for PLUNK_API_KEY and only put the values in that config, nowhere else.
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

Built from the package data we hold. Not yet tested by us.

Tools

  • Browse or search your contacts

    Lists contacts in your Plunk project, or searches them, a page at a time.

    Try: “Find contacts whose email ends in @acme.com.”

    Network · plunk_list_contacts

  • Fetch one contact by ID or email

    Returns one contact with its custom data. You can pass an email address instead of an ID.

    Try: “Show me the Plunk record for ada@example.com.”

    Network · plunk_get_contact

  • Check one email's status

    Looks up a sent or scheduled email and says what state it is in and when it sends.

    Try: “Has the welcome email to ada@example.com gone out yet?”

    Network · plunk_get_email

  • Check if an address can receive mail

    Asks Plunk whether an email address looks deliverable before you send to it.

    Try: “Is sam@example.org a deliverable address?”

    Network · plunk_verify_email

  • List email templates

    Lists the reusable email templates saved in the project.

    Try: “What email templates do we have?”

    Network · plunk_list_templates

  • List campaigns and status

    Lists your campaigns and whether each is a draft, scheduled or sent.

    Try: “Which campaigns are still drafts?”

    Network · plunk_list_campaigns

  • Fetch one campaign in full

    Returns one campaign with its content and how many people it would reach.

    Try: “How many people will the October newsletter go to?”

    Network · plunk_get_campaign

  • Opens, clicks and bounces for a campaign

    Returns opens, clicks, bounces and their rates for one campaign.

    Try: “How did last week's product update campaign perform?”

    Network · plunk_get_campaign_stats

  • List audience segments

    Lists the saved groups of contacts you can target.

    Try: “List my segments.”

    Network · plunk_list_segments

  • List sender domains

    Lists the domains you send from and whether each is verified.

    Try: “Which sender domains are verified?”

    Network · plunk_list_domains

  • Re-check a domain's DNS

    Re-runs the DNS check for one sender domain and returns its verification status.

    Try: “Re-check the DNS for mail.example.com.”

    Network · plunk_check_domain

  • List automation workflows

    Lists your automation workflows and whether each one is switched on.

    Try: “Which workflows are enabled?”

    Network · plunk_list_workflows

From the official docs

Permissions

high risk · 5 things to watch

High risk

The assistant can read your Plunk data, change it, send email to your contacts and delete contacts and workflows. Turn on read-only mode and use a key from a test project until you trust how your assistant behaves.

What it can do

Watch out for

  • It can delete contacts and workflows

    The tools that delete contacts, workflows and workflow steps work on live data. Turn on read-only mode, or use a separate Plunk project for anything you cannot afford to lose. registry.npmjs.org

  • It can send real email to real people

    Sending a campaign cannot be undone. The server asks you to confirm and shows how many people will get it, so read that number before you approve. registry.npmjs.org

  • The key reaches the whole project

    The README says Plunk's secret key is all-or-nothing over its project. Keep a key for each project you connect, and do not reuse one from a self-hosted server's environment. registry.npmjs.org

  • Headless mode skips the send prompt

    Setting PLUNK_ALLOW_UNCONFIRMED_SENDS=true removes the confirmation step. Only use it for automation you fully trust. registry.npmjs.org

  • Domains, billing and keys are out of reach

    The README says adding or removing sender domains, billing, project deletion and key rotation are not exposed as tools. registry.npmjs.org

Security advisories

No published security advisories for the MCP server as of Nov 1, 2026.

7 other advisories are about the wider plunk project, not this MCP server. See them on GitHub

Technical details
Turning on read-onlySet PLUNK_READ_ONLY=true (or pass --read-only). The tools that change things are not registered at all, so they cannot be called.
Talks toPlunk API (hosted, or your own domain if you set PLUNK_API_URL)
Sign-in and keysThe secret key is passed in the PLUNK_API_KEY setting of your assistant's config on your machine.
Scopes
  • PLUNK_API_KEY: secret key (sk_...) for one Plunk project, full read and write access to that project

Questions

Is the Plunk MCP server official?

Yes. It ships from the Plunk repository as the official @plunk/mcp package.

Do I need an API key?

Yes. You need your project's secret key (starts with sk_) from Settings, then API Keys, in the Plunk dashboard. Without a key the server does not work.

Can I use it read-only?

Yes. Set PLUNK_READ_ONLY=true or pass --read-only. Then only the 16 read tools exist and nothing can be created, changed, sent or deleted.

Does it work with a self-hosted Plunk?

Yes. Set PLUNK_API_URL to your own API address. The server works with the hosted product and with self-hosted instances.

Can it send email without asking me?

Not by default. Sending a campaign, or emailing more than one person, asks you to confirm first. If your client cannot show prompts, sends are blocked unless you set PLUNK_ALLOW_UNCONFIRMED_SENDS=true.

Can it connect to more than one Plunk project?

Yes. Set one key per project named PLUNK_API_KEY_ followed by a project name. Every tool call then names the project it acts on.

How do I add it to Claude or Cursor?

Use the install box above and put your secret key in the PLUNK_API_KEY setting. Restart the app so it loads the tools.

Information

updated Nov 2, 2026

Publisher
Official
Package
@plunk/mcp
Registry
npm
Transport
stdio
Auth
API key
Version
0.17.0
License
AGPL-3.0
Last commit
Oct 28, 2026
Open issues
35

WebsiteGitHubnpmChangelogIssues

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 2
  1. registry.npmjs.org · registry.npmjs.org
  2. github.com · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.