MCP server changelog

• 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.

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/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.

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.

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.

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

See 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.

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

See Local MCP server.