Skip to content
Docs

Reference

The official Emailit plugin for ChatGPT, Codex, Claude Code, Cursor and Grok bundles the hosted MCP server with skills and a rule that keeps secrets out of code.

Updated Oct 2, 2026

The Emailit plugin packages everything an AI assistant needs to work with Emailit: a connection to the hosted MCP server, skills that teach the assistant how Emailit works, and a Cursor rule for safe handling of secrets. It’s open source at github.com/emailit/emailit-plugins (MIT).

You sign in with your Emailit account through OAuth and choose which workspaces the plugin can use: all of them, or only the ones you select. No API key is stored in the plugin.

What’s included

Part What it does
MCP server https://api.emailit.com/mcp with 109 tools across emails, domains, DMARC, templates, audiences, contacts, suppressions, campaigns, automations, forms, verification, webhooks, events, API keys and workspaces
emailit skill Choosing between MCP tools and the REST API, safe sending, IDs, pagination, errors and the full tool list
emailit-get-started skill Connect, confirm the workspace, check a domain and send a first test email
emailit-domain-setup skill Add a domain, publish DNS records at any provider, verify and fix failed records
emailit-deliverability skill Bounces, spam placement, suppressions, DMARC reports and list verification, answered with data from your account
emailit-campaigns skill Audiences, contacts, campaigns, automations and signup forms, with safe sending
emailit-webhooks skill Events, filters, signature verification, batched payloads, retries and debugging
emailit-sdk skill Production code for the Node.js, Python, PHP, Laravel, Go, Ruby, Java, .NET and Rust SDKs, plus SMTP
Cursor rule Keeps Emailit API keys (secret_…) and webhook secrets (whsec_…) out of source code and reads them from EMAILIT_API_KEY and EMAILIT_WEBHOOK_SECRET

Skills load on demand: the assistant reads a skill when your request matches it, for example “why did my email bounce” loads emailit-deliverability.

Install

Open Plugins, search for Emailit and choose Connect. Sign in, choose the workspaces to allow and approve access. See ChatGPT.

Access and safety

  • OAuth 2.1 with PKCE. The assistant never sees your password. You approve sending access (send and manage sent email) or full access (everything), and pick the workspaces.
  • Confirmation before impact. Tools that send email, delete data or call external URLs are labeled so the client asks you first, and the skills tell the assistant to confirm.
  • Revoke any time under AccountConnected apps.
  • Headless clients such as the xAI API and CI jobs can send an Emailit API key as Authorization: Bearer <key> to the same server. Use a Sending Only key where you can.

Endpoints the plugin uses

The plugin talks only to Emailit:

Endpoint Purpose
https://api.emailit.com/mcp Hosted MCP server (Streamable HTTP)
https://api.emailit.com/.well-known/oauth-protected-resource/mcp OAuth protected resource metadata
https://api.emailit.com/.well-known/oauth-authorization-server OAuth authorization server metadata
https://api.emailit.com/oauth/register Dynamic client registration
https://api.emailit.com/oauth/authorize Sign-in and consent
https://api.emailit.com/oauth/token Token exchange and refresh
https://api.emailit.com/oauth/revoke Token revocation
https://api.emailit.com/v2 REST API, used by code the SDK skill writes into your project
smtp.emailit.com:587 SMTP, only if your project is configured for it

Manifests

The repository ships one manifest per client:

File Read by
plugin.json, mcp.json ChatGPT, Codex and other Agent Plugins clients
.cursor-plugin/ Cursor
.claude-plugin/, .mcp.json Claude Code, the Claude directory and Grok
.grok-plugin/plugin.json Grok
.agents/plugins/marketplace.json The Codex marketplace

The skills’ tool reference is generated from the MCP server’s tool catalog, the same source as the tool reference in these docs, so the tool names in skills always exist on the server.

Was this page helpful?

Thanks for the feedback.

Thanks, we read every message.