AgentDrives

Plunk

useplunk.com

Plunk is an email service for sending and automating email.

Can an AI agent use Plunk? Yes, without signing up. Our agent got into Plunk on its own in 5 minutes and did 2 of its 7 core tasks.

Visit Plunk Follow changes

Category

Email infrastructure

Connects by

MCP, API

Agent payments

None found

Driven 27 Oct 2026

From finding it to leaving

What an agent managed without a person, at each step.

  1. Find

    On its own

    Docs it can act on: llms.txt, an OpenAPI and an MCP server.

    176 doc pages read

  2. Get in

    On its own

    Runs locally, key by API, sign-up in a browser.

    5 minutes

  3. Use

    Partly

    Did: manage contacts, custom fields and CSV imports; build segments and track events. Not done: send any email, template or campaign.

    2 of 7 core tasks

  4. Pay

    Reaches the checkout

    Stopped at the card form.

  5. Leave

    On its own

    Nothing to cancel, deletes its account.

Getting in

3 of 3 ways in worked without a person.

The way that worked

Runs locally, no account5 minutes

  • An inboxNot needed
  • A browserNot needed
  • A personNot needed
  • Agent on a serverAPI, MCP, CLIPartlySigns up, confirms its email, gets an API key, makes its first API call and does 2 of its 7 core tasks, then stops: the rest needs a paid plan.
  • Assistant in its own browserLike ChatGPT agentPartlySigns up, confirms its email and does 2 of its 7 core tasks, then stops: the rest needs a paid plan.
  • Signed agentKnown to CloudflareYesThe sign-up page opens.

Every way in

Way inWhat happened
Runs locally, no accountWorked
Sign-up by APIWorked
Email and passwordWorked

What an agent can do with Plunk

2 of 7 core tasks done, and 11 of 19 others.

Core tasks

  • done there
  • tried, not done
TaskResultThrough
Build an email automationDoneAPIMCP
Add a contact to an automationDoneAPIMCP
Send a transactional emailBlockedAPI
Send an email from a templateEvery send needs a sender domain verified by DNS records.BlockedAPI
Draft an email campaignBlockedAPI
Schedule an email campaignBlockedAPI
Receive inbound emailNeeds a verified domain and an MX record.BlockedAPI

  • Reliability

    92of 100

    Core tasks that worked on all 3 runs

  • Handles mistakes

    65of 100

    Clear errors, retries without duplicates, honest limits

  • Surface tested

    77of 100

    Documented routes, tools and commands run and checked

  • Docs accuracy

    87of 100

    Documented operations that behaved as the docs say

  • Docs completeness

    69of 100

    How fully the docs describe each operation

  • What it can't do, and why

    • Send any email, template or campaign Every send needs a sender domain verified by DNS records.
    • Receive inbound email Needs a verified domain and an MX record.
    • Pay for the paid plan Only card checkout exists.
    • Delete the account through documented API The account is deleted in the dashboard only.

11 of 19 other tasks done

  • Validate an email addressDone
  • Create a list and add contacts to itDone
  • Update a contact or subscriberDone
  • Delete a contact or subscriberDone
  • Import contacts from a CSV fileDone
  • Track an event for a contactDone
  • Create a custom contact fieldDone
  • Create a segmentDone
  • Manage suppressions (bounce and complaint handling)Done
  • Create an API keyDone
  • Read usage and quotasDone
  • Add and verify a sending domainPartly
  • Track email opens and clicksPartly
  • Register a webhookPartly
  • Translate the unsubscribe footer and contact-facing pagesPartly
  • Self-host the platform on your own infrastructurePartly
  • Remove the product's branding from emailsPaid plan
  • Set a spend limitPaid plan
  • Create an email templateBlocked
  • Read campaign performanceBlocked
  • Set up a preference centre or unsubscribe pageBlocked

Paid-plan tasks don't count toward the level. The drive used the free plan.

Surface audit: 169 documented operations, 133 run, 123 passed, 17 not as documented, 27 blocked (sandbox or plan limits), 9 left out to stay safe.

How an agent connects

MCP, API, OpenAPI and llms.txt found.

The standards

  • MCP server

    37 tested

    Official server. Stdio server @plunk/mcp 0.17.0, 42 tools.

    45 tools across its docs

  • API

    90 tested

    REST at next-api.useplunk.com, about 115 documented endpoints.

    117 operations across its docs

  • OpenAPI

    Yes

    3.1.0, 18 operations; workflows, domains and events are not in it.

  • CLI

    None found

  • SDK

    None found

  • llms.txt

    Yes

    useplunk.com/llms.txt

  • Agent payments

    None found

    The checkout: Reached the card form and stopped: Pay-as-you-go; Checkout: Stripe Checkout; An invisible bot check loaded at checkout; Wallets: Link.

  • Docs

    No gaps in what we read

    Covers getting started, auth, error codes and code examples.

    2 of 6 documented ways to do the core work worked when tried.

    docs.useplunk.com

    176 of 177 pages read

Tips for agent builders

From this drive

5 tips
  1. Use sk_ for everything except POST /v1/track, which takes pk_.
  2. Check GET /domains/project/:projectId (or plunk_list_domains) before sending: without a verified domain every send, template and campaign returns 403.
  3. Workflow steps need a 'position'; UPDATE_CONTACT takes config.updates. Read the execution back: a bad config only fails at run time.
  4. Prefer the MCP server's plunk_add_workflow_steps and plunk_check_workflow: they validate before saving.
  5. Bulk contact jobs take {"mode":"ids","contactIds":[...]}.

How Plunk compares

In Email infrastructure

2nd of 2 Email infrastructure products our agent got into on its own.

ProductLevelFind to leave
AgentMailL5Find: On its own, Get in: On its own, Use: On its own, Pay: On its own, Leave: On its own.
PlunkL2Find: On its own, Get in: On its own, Use: Partly, Pay: Partly, Leave: On its own.
MailerSendL1Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached.
MailgunL1Find: On its own, Get in: Stopped, Use: Not reached, Pay: Partly, Leave: Not reached.
MailtrapL1Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached.
PostmarkL1Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached.
ResendL1Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached.
SendGridL1Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached.
All 8 in Email infrastructure

Sorted by level, then work done, then time to the first call. How we rank

For the team behind Plunk

Our agent got through Use and Pay only in part. Prove Plunk is yours, then see where each issue is, read your safety findings and ask for a free drive after a fix. How to fix each one comes with the Audit.

11 things to fix for agents

Agent blockers: 1 foundAgent surfaces: 18 issues foundSafety review: no issues found

  1. FindClear
  2. Get inClear
  3. UsePartly
  4. PayPartly
  5. LeaveClear

Claim Plunk, freeWhat a drive covers

On our standard

18 criteria: against other email infrastructure products where we measured 5 or more, otherwise against every product we measured.

All 18 criteria
How each criterion is graded

Where Plunk fits

Category
Tasks
Standards
Steps
Rivals

Every earlier drive is in the history. Data under CC BY 4.0.

JSONMarkdownAtomJSON Feed

Found an error? or read how corrections work.

Questions people ask about Plunk

Can an AI agent sign up for Plunk on its own?
Yes, over the API, without a browser.
Does Plunk have an MCP server, and can an agent connect to it?
Yes. Plunk has an official MCP server. The server runs on the agent's own machine and lists 42 tools. A new agent can get in on its own: in the drive of 27 Oct 2026, our agent signed up, verified and got its key without a person.
How does an AI agent get a Plunk API key?
In the drive of 27 Oct 2026, our agent got its Plunk API key over the API, without a browser or a person.
Can an AI agent delete its Plunk account?
Yes, in a browser, without a human. Project deleted without a browser; the account only in the dashboard (Account → Delete account after deleting the project). Afterwards login, session and secret key are refused. An uploaded image stays public.
Can an AI agent pay for Plunk?
Partly. Reaches the checkout: stopped at the card form. No card needed to start.

Cite this page

The page as a reference, in plain text, APA and BibTeX.

Cite this
Plain
AgentDrives, “Plunk: AI agent test drive”, 27 October 2026, https://agentdrives.com/tools/useplunk. CC BY 4.0.
APA
AgentDrives. (2026, October 27). Plunk: AI agent test drive. https://agentdrives.com/tools/useplunk
BibTeX
@misc{agentdrives_useplunk_2026,
  author = {{AgentDrives}},
  title = {Plunk: AI agent test drive},
  year = {2026},
  month = oct,
  url = {https://agentdrives.com/tools/useplunk},
  note = {Agent test drive, CC BY 4.0},
}

Something wrong on this page?

Tell us what's wrong. We check it against the drive and correct the page, with the date.