Plunk Email Marketing MCP. Manage contacts and track events in conversation.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Plunk Email Marketing MCP Server handles your entire audience lifecycle via API calls. Manage contacts—create new users, update metadata, or delete records.
Send immediate transactional emails for alerts or onboarding sequences. You can also track custom user actions and list all saved templates or running campaigns directly through natural conversation with your AI agent.
What your AI agents can do
Create or update contact
Creates a new user profile in Plunk, or updates metadata for an existing contact record.
Delete contact
Permanently removes a specific contact from your entire Plunk audience list.
Get contact details
Retrieves all stored information and current status for one specific user contact.
Create, read, update, and delete user contacts within the Plunk audience database.
Queue transactional emails to specific recipients for notifications or alerts.
Log custom user events—like 'button_clicked' or 'profile_viewed'—to your Plunk audience.
Retrieve a list of all active and saved email marketing campaigns in the platform.
Get a complete list of every reusable HTML template you have created for emails.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Plunk Email Marketing: 8 Tools for Audience Ops
Run core marketing operations—from contact management to sending alerts—using these eight specialized tools through your AI agent.
019d846ecreate or update contact
Creates a new user profile in Plunk, or updates metadata for an existing contact record.
019d846edelete contact
Permanently removes a specific contact from your entire Plunk audience list.
019d846eget contact details
Retrieves all stored information and current status for one specific user contact.
019d846elist contacts
Fetches a list of every single active and inactive contact in your Plunk database.
019d846elist email campaigns
Pulls a summary of all email marketing campaigns you have set up or run previously.
019d846elist email templates
Displays every reusable HTML template available in your Plunk account for building emails.
019d846esend transactional email
Sends a one-time, non-marketing email (like an alert or reset) to the specified recipient(s).
019d846etrack user event
Logs a custom action performed by a user, recording data that helps segment your audience.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Plunk Email Marketing, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
This Plunk Email Marketing MCP Server handles your whole audience lifecycle directly through your AI client. You'll manage contacts, trigger emails, and track user behavior—all without leaving your chat interface.
Managing Your Audience Contacts
You can treat the Plunk database like your own CRM right here. Use list_contacts to fetch a complete roster of every single contact in your system, whether they're active or dormant. Need to know what one specific user is up to? Run get_contact_details and you'll get all their stored info and current status immediately.
If you need to add someone new, use create_or_update_contact; it either makes a brand-new profile for a user or updates the metadata on an existing record. And if that contact is junk? Run delete_contact and you permanently strip them from your Plunk audience list.
Tracking User Behavior
Your AI client uses track_user_event to log custom actions performed by users—stuff like 'button_clicked' or 'profile_viewed.' This data helps segment your audience so you know exactly who needs what message.
Sending and Auditing Content
To keep people informed, use send_transactional_email. You send one-time emails for alerts, password resets, or simple onboarding messages to specific recipients. When it comes to content, the server gives you full visibility. Run list_email_templates to display every reusable HTML template sitting in your Plunk account, so you know what's ready to go into an email.
You can also pull a summary of all marketing campaigns—both those you’ve set up and ones that ran previously—by calling list_email_campaigns. This gives you the full picture of your platform's history.
You get all this done by just talking to your agent. It reads the tools, figures out what you need, and executes the API calls for you.
How Plunk Email Marketing MCP Works
- 1 Subscribe to the server and provide your Plunk Secret Key.
- 2 Your AI agent uses natural language prompts (e.g., 'List all contacts') to invoke specific tools.
- 3 The MCP Server runs the tool against the Plunk API, returning structured data or confirmation messages directly into the chat.
The bottom line is you tell your AI client what marketing action to take; it handles the messy API calls for Plunk and gives you a clean answer right here.
Who Is Plunk Email Marketing MCP For?
Growth Marketers, Product Managers, and Customer Support reps. This setup is for anyone who spends time switching between email marketing dashboards, CRM tools, and analytics platforms just to execute a simple communication flow or check user status. Stop clicking through five different tabs at 2 AM.
Uses list_contacts to segment an audience and then uses send_transactional_email to test a quick blast or send welcome messages.
Triggers track_user_event whenever a new feature is used, allowing them to audit user behavior without writing manual logging scripts.
Uses get_contact_details to pull specific user metadata quickly and uses create_or_update_contact to correct an email address or subscription status on the fly.
What Changes When You Connect
- Stop manually checking user statuses. You can instantly
get_contact_detailsorlist_contactsright from your agent, getting real-time audience data without logging into Plunk's dashboard. - Send critical alerts immediately. Use
send_transactional_emailto send password resets or onboarding messages the second a user needs it, bypassing complicated workflow builders. - Build better automation logic. By using
track_user_event, you log specific actions (e.g., 'checkout_abandoned'), giving your marketing team better data than simple open rates. - Audit content fast. Need to know what templates are available? Run
list_email_templatesor check campaign status withlist_email_campaigns. It's all one prompt away. - Maintain clean data. Use
create_or_update_contactto ensure user metadata is current, and if necessary, usedelete_contactto scrub old records—all controlled by your AI agent.
Real-World Use Cases
The Onboarding Flow Failure
A new sign-up needs a welcome email immediately. Instead of going through the 'Automation' menu, calling get_contact_details confirms the user exists, and then triggering send_transactional_email sends the required message in two steps, solving the immediate communication gap.
Auditing User Behavior
A PM wants to know how many users saw the pricing page this week. They run a query that calls track_user_event for 'pricing_viewed'. The agent reports the count, letting them segment and build an email campaign using list_email_campaigns later.
Contact Cleanup
The data team spots old accounts that should be purged. They run list_contacts to find stale entries, then use delete_contact on the identified list, ensuring compliance and keeping the audience clean.
Emergency Communications
A service outage requires an immediate alert. The support agent calls send_transactional_email to target only affected users, bypassing scheduled campaigns entirely and notifying them instantly.
The Tradeoffs
Treating the tool like a database query.
Asking the agent to 'show me all emails sent last month.' The tools don't provide historical send logs, only listing available templates or campaigns. This will fail or return irrelevant data.
→
To see what marketing assets are ready, use list_email_templates. To check campaign status, call list_email_campaigns. Stick to the tool's explicit function.
Over-relying on contact deletion.
Running delete_contact because a user unsubscribed. Deleting them permanently removes all their data, potentially breaking downstream reporting that relies on historical records or metadata.
→
If a user leaves, use the agent to update their status via create_or_update_contact (setting 'Unsubscribed') instead of calling delete_contact. This keeps the record for auditing.
Trying to send bulk marketing blasts.
Asking the agent to 'Send a newsletter to everyone.' The send_transactional_email tool is for one-off alerts, not mass campaigns. You need to use Plunk's native campaign tools for that.
→
When It Fits, When It Doesn't
Use this server if your primary need is connecting ad-hoc marketing actions—like sending a single alert email or tracking a specific user action—to an existing audience list without switching contexts. It’s perfect for quick, operational tasks.
Don't use it if you need advanced segmentation based on complex scoring models (you'd need a dedicated CRM integration). Also, don't rely on it to manage the full lifecycle of campaign creation; list_email_campaigns only reports status. If your process requires proprietary API calls not covered by these eight tools, you’ll hit a wall. It is best for direct actions and data retrieval.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Plunk. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 8 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually managing contact lists sucks.
Right now, if you need to check a user's status or update their email, you jump into Plunk. You search for the user, open the profile page, find the field you want to change (like 'Subscription State'), and then hit save. It takes four clicks just to correct one piece of metadata.
With this MCP server, you just ask your agent: 'Update John Doe's subscription status to Active.' The agent handles all those API calls behind the scenes. You get confirmation—no dashboard jumping required.
Plunk Email Marketing MCP Server
You no longer have to copy a user list from one spreadsheet, paste it into Plunk's bulk uploader, and wait for the job to complete. You simply tell your agent: 'Send this email to these five users.' The action is immediate.
It shifts communication from tedious, multi-step UI operations to simple, direct conversation. That’s how fast you need your workflow to be.
Common Questions About Plunk Email Marketing MCP
How do I use the `send_transactional_email` tool? +
You prompt the agent with a clear request and specify the recipients. The tool requires the full email address(es) and the subject line. It sends one-time, direct emails—not mass campaigns.
Can I use `track_user_event` for everything? +
No. You must provide a specific event name (e.g., 'download_pdf') and structured JSON data explaining what happened. It's designed to log discrete, measurable user actions.
`list_contacts`: What does this tool actually return? +
It returns a list of contacts matching your query criteria—usually including their email address and their current subscription state (Subscribed/Unsubscribed).
Does `get_contact_details` show me everything about the user? +
Yes. It retrieves all stored metadata for a specific contact ID or email, giving you a complete snapshot of their record in Plunk.
When I use `list_email_campaigns`, are there limits on how many campaigns can be retrieved? +
The tool retrieves campaign data in paginated batches. If your audience has more than the default limit of campaigns, your agent will automatically call subsequent pages until all records are found.
What happens if I run `send_transactional_email` and a recipient address is invalid? +
The tool reports the failure instantly. Plunk provides specific error codes for delivery issues, such as 'invalid-recipient' or 'bounce detected,' letting you know exactly what went wrong.
How much metadata can I add when running `create_or_update_contact`? +
You can include virtually any custom data in the JSON payload. This lets your agent track niche details, like 'last viewed category' or 'preferred time zone,' alongside basic contact info.
Is deleting a user with `delete_contact` permanent? +
Yes, this action permanently removes the record from Plunk. Once your agent executes the deletion tool, that contact data is gone and cannot be retrieved or restored via the API.
Where do I find my Plunk Secret Key? +
Log in to your Plunk Dashboard, navigate to project settings, and you will find your Secret Key under the API section. It typically starts with sk_.
Can I send bulk newsletters with this agent? +
This integration is optimized for transactional emails and event tracking. For large-scale bulk newsletters, we recommend using the Plunk dashboard or their specialized campaign endpoints for maximum deliverability and compliance.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Bird (MessageBird)
Unified communications platform for SMS, WhatsApp, Email, and Voice — manage conversations and contacts at scale.
Keap
Manage CRM contacts, marketing campaigns, and sales automation via Keap.
Landbot
Empower your AI to generate, route, and interact with conversational chatbots and customers naturally.
You might also like
Cloverly
Offset carbon emissions at the point of transaction by purchasing verified carbon credits for shipments, rides, and purchases.
HERE Mobility
AI transit planning: discover routes, schedules, and stations for public transport via agents.
Cornershop
Automate LatAm grocery deliveries via Cornershop (by Uber) — search products, manage carts, track orders, and monitor shoppers from any AI agent.