Quickstart
Connect an AI assistant
Connect ChatGPT, Claude, Cursor, Codex or Grok to Emailit in about three minutes, sign in with OAuth, choose your workspaces and try your first prompts.
This quickstart connects an AI assistant to Emailit through the hosted MCP server. Once connected, you can ask it to send email, check delivery, set up domains, manage contacts and templates, run campaigns and automations, all in plain language.
Before you begin
- An Emailit account with at least one workspace. Sign up at dash.emailit.com.
- An AI tool: ChatGPT, Claude, Claude Code, Cursor, Codex, Grok or another MCP client.
- To send real email, a verified sending domain. You can explore everything else without one.
1. Add Emailit to your AI tool
Open Plugins, search for Emailit and choose Connect. If Emailit isn’t listed yet, add https://api.emailit.com/mcp with developer mode. See ChatGPT.
Go to Settings > Connectors, choose Browse connectors, search for Emailit and choose Connect. If it isn’t listed, choose Add custom connector with https://api.emailit.com/mcp. See Claude.
claude plugin marketplace add emailit/emailit-plugins
claude plugin install emailit@emailit-pluginsThen run /mcp, select emailit and choose Authenticate.
Install Emailit from Settings > Plugins (or /add-plugin emailit), then choose Connect next to emailit in Settings > MCP. See Cursor.
codex mcp add emailit --url https://api.emailit.com/mcp
codex mcp login emailitOr install the Emailit plugin with codex plugin marketplace add emailit/emailit-plugins. See Codex.
On grok.com, open Connectors > New Connector > Custom and enter https://api.emailit.com/mcp. In Grok Build, run grok plugin install emailit --trust after adding the marketplace. See Grok.
For VS Code, Windsurf, Zed and other clients, see Other clients.
2. Sign in and choose workspaces
-
Sign in. Your browser opens the Emailit sign-in page. Enter your email and password, plus your authenticator code if you use two-factor authentication.
-
Choose workspaces. Allow All my workspaces or Only these workspaces, and choose where the assistant starts.
-
Allow access. Approve the requested access. Most tools ask for full access.
You’re sent back to your AI tool and the Emailit tools appear. The tool refreshes access in the background, so you don’t sign in again each session.
3. Try your first prompts
- “Which Emailit workspace am I connected to?”
- “List my sending domains and tell me which ones aren’t verified.”
- “Show my last five bounced emails and explain why they bounced.”
- “In Acme Client, create an audience called Beta testers and add jane@example.com.”
- “Draft a welcome campaign for Beta testers, but don’t send it.”
The assistant asks before it sends email, deletes data or changes anything that can’t be undone. Keep your tool’s approval prompts on and read each action before you allow it.
Sends through MCP follow the same rules and credit costs as the API. Until your workspace has production access, you can only send to workspace members’ account emails.