Skip to content
Docs

Reference

MCP server changelog

Changes to MCP server: new features, improvements and fixes.

October 2026

  1. Changed

    Campaign tracking follows the domain, with a per-campaign override

    CampaignsOpen & click trackingMCP server

    • Domain defaults: campaign emails now follow the sending domain’s Track loads and Track clicks settings, like API and SMTP mail. Until now, every campaign email requested open and click tracking whatever the domain said. If your campaign reports should keep showing loads and clicks, turn tracking on for the domain or override it in the campaign.
    • Tracking in the wizard: the Settings step of the campaign wizard has a Tracking card again. It shows the domain’s defaults, and Override domain tracking lets you set Track opens and Track clicks for that campaign. If the domain has no verified tracking CNAME, the card says so and links to the domain.
    • API and MCP: Create a campaign and Update a campaign accept track_loads and track_clicks (true, false, or null to follow the domain), and campaign responses return them. Duplicates and follow-ups keep the campaign’s override. The create-campaign and update-campaign MCP tools take the same fields.
    • Send summary: the Send step shows what the campaign tracks and whether that comes from the domain or the override.
    • Links to Emailit: click tracking skipped every link whose host contained “emailit”, such as links to emailit.com and dash.emailit.com, and links to customer domains with “emailit” in their name. Now only the links Emailit adds itself, such as unsubscribe and web version links, are left unchanged.

    See Create a campaign.

  2. Fixed

    email.held in the webhook event picker, test events and MCP

    WebhooksMCP server

    email.held already reached webhooks with All events on, but it was missing elsewhere: the Events picker, the Send test dialog and the event filter on the Events page didn’t list it, Send a test event returned 400 “Unknown event type”, and the MCP create-webhook, update-webhook and test-webhook tools rejected it. All of them accept it now.

    See email.held and Set up a webhook.

  3. New

    Connected apps and multi-workspace access for AI apps

    Account & securityMCP serverWorkspaces

    • Choose workspaces when you connect: allow all your workspaces (including future ones) or only the ones you tick, and pick where the app starts.
    • Work across workspaces: name a workspace in your request (“In Acme Client, list the domains”) and the assistant runs that one call there with the new workspace argument, without changing its default.
    • Your role applies: in workspaces where you’re a Member, AI apps can’t manage API keys or delete domains, over MCP and the REST API alike.
    • Connected apps: a new tab under Account lists every app you approved with its workspaces, access and connection date. Edit access changes its workspaces without reconnecting; Revoke access cuts it off immediately.

    See Connected apps and Workspaces and permissions. Integrations can manage grants with the new PUT /oauth/grants/:id/workspaces endpoint; see OAuth apps.

  4. New

    Emailit plugins for ChatGPT, Codex, Claude Code, Cursor and Grok

    MCP server

    The Emailit plugin bundles the hosted MCP server with seven skills and a Cursor rule:

    • emailit, emailit-get-started, emailit-domain-setup, emailit-deliverability, emailit-campaigns, emailit-webhooks and emailit-sdk.
    • A Cursor rule that keeps API keys and webhook secrets out of source code.

    Install it from the plugin directory in ChatGPT and Cursor, or from the emailit/plugins marketplace in Claude Code, Codex and Grok Build. On claude.ai and Claude Desktop, use the Emailit connector. See Plugins and skills and the guides for ChatGPT, Claude, Cursor, Codex and Grok.

  5. Improved

    Hosted MCP server covers the full API v2

    MCP serverREST API

    The MCP server at https://api.emailit.com/mcp now covers everything in API v2:

    • New toolsets: campaigns, automations, forms, DMARC reports, email verification, events, contact bulk actions and export, subscribers, and webhook tests, retries and secret rotation. See the tool reference.
    • Annotations: every tool is labeled read-only, destructive, idempotent or open-world, so clients can ask before running write actions.
    • Structured results: tools return JSON as text and as structured content for clients that parse it.
    • Built-in instructions: the server tells assistants to confirm recipients before sending and to ask before deleting anything.
    • Toolsets and read-only mode: load fewer tools with ?toolsets= or hide write tools with ?read_only=true. See Toolsets.
    • Stateless transport: no MCP sessions to expire; clients send every request with POST.

    Fixed: OAuth connections approved with both the sending and full scopes now work on every tool, and the workspace you switch to stays selected after the client refreshes its token.

September 2026

  1. New

    Hosted MCP server with OAuth

    MCP server

    The hosted server uses the Streamable HTTP transport. Clients that support OAuth open an Emailit sign-in and consent page, where you choose the workspaces to share and whether the client gets the sending or full scope. With OAuth, the assistant can also list, switch and create workspaces. Clients without OAuth can send an API key as a bearer token instead.

    Terminal
    claude mcp add emailit --transport http https://api.emailit.com/mcp

    See MCP server.

May 2026

  1. New

    Emailit MCP server

    MCP server

    The @emailit/emailit-mcp package exposes tools for emails, domains, API keys, audiences, contacts, templates, suppressions and webhooks. It runs over stdio or HTTP, needs Node.js 18 or later, and is MIT-licensed on GitHub.

    Terminal
    claude mcp add emailit -e EMAILIT_API_KEY=$EMAILIT_API_KEY -- npx -y @emailit/emailit-mcp

    See Local MCP server.

Was this page helpful?

Thanks for the feedback.

Thanks, we read every message.