← All integrations

Enginemailer MCP server

38 operations0 webhooks

Manage Enginemailer subscribers, categories and custom fields, build and send email campaigns, and read subscriber activity through Enginemailer's N8N API.

Try Enginemailer with your agent

Connect Enginemailer, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Enginemailer on my account, then run one read-only example and show me the result.

Runs once, when you ask

Enginemailer tools and triggers

Tools are what your agent can do in Enginemailer through Corsair's MCP server. Triggers are the Enginemailer events a routine can start from.

N8n

  • Add Or Update SubscriberWrite

    Add or update a subscriber through Enginemailer N8N

    n8n.addOrUpdateSubscriber

  • Autoresponder CompletedRead-only

    List subscribers who completed an autoresponder

    n8n.autoresponderCompleted

  • Autoresponder TriggeredRead-only

    List subscribers who triggered an autoresponder

    n8n.autoresponderTriggered

  • ConnectRead-only

    Test the Enginemailer N8N connection

    n8n.connect

  • Deactivate SubscriberDestructive

    Unsubscribe a subscriber through Enginemailer N8N

    n8n.deactivateSubscriber

  • Delete N8n SubscriberDestructive

    Delete a subscriber through Enginemailer N8N

    n8n.deleteN8nSubscriber

  • Deleted SubscribersRead-only

    List deleted subscribers through Enginemailer N8N

    n8n.deletedSubscribers

  • Find SubscriberRead-only

    Find a subscriber through Enginemailer N8N

    n8n.findSubscriber

  • List FormsRead-only

    List Enginemailer forms through N8N

    n8n.listForms

  • List PagesRead-only

    List Enginemailer pages through N8N

    n8n.listPages

  • List PopupsRead-only

    List Enginemailer popups through N8N

    n8n.listPopups

  • Modified SubscribersRead-only

    List modified subscribers through Enginemailer N8N

    n8n.modifiedSubscribers

Connect Enginemailer to Claude, ChatGPT or Cursor

  1. 1

    Connect Enginemailer in Corsair

    Add your Enginemailer API key once in Corsair. Corsair stores the credential encrypted and makes the Enginemailer API calls for your agent, so it never goes into a prompt or a config file. Connect Enginemailer

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Enginemailer. On a ChatGPT personal plan, connect Enginemailer here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Enginemailer's read and write operations run right away and its 7 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/enginemailer, add the Enginemailer plugin, and connect with an API key. Then call methods like corsair.enginemailer.api.campaigns.assignRecipientList() from your app. Corsair keeps each tenant isolated.

Yes. Enginemailer requires an API key from your Enginemailer account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Enginemailer, GitHub, Notion, Stripe, and the rest. Trigger Enginemailer from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for manage enginemailer subscribers, categories and custom fields, build and send email campaigns, and read subscriber activity through enginemailer's n8n api. Common builds include sync jobs, admin tooling, and agents that call Enginemailer APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Enginemailer API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/enginemailer in the open repo. When Enginemailer ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Enginemailer data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Enginemailer data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Enginemailer on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 7 destructive Enginemailer operations. You can change a link's mode at hub.corsair.dev/me.