How to Send Email from an AI Agent with MCP
Connect Claude Code, Cursor or Codex to Inboxjot, choose what the agent can do, and send your first email from a prompt.
Arik Chakma
Connect Claude Code, Cursor or Codex to Inboxjot, choose what the agent can do, and send your first email from a prompt.
Your AI agent can send email, look up deliveries and draft campaigns in Inboxjot. You connect it once to the Inboxjot MCP server. MCP (Model Context Protocol) is a standard way for AI tools to use outside services. The server runs at https://mcp.inboxjot.com, so you install nothing.
This example uses Claude Code. Other tools have their own setup pages, linked after the steps.
Add the server
Run this command in your terminal.
claude mcp add --transport http inboxjot https://mcp.inboxjot.comOpen the MCP list
Start Claude Code and run /mcp.
Select inboxjot
Choose the inboxjot server in the list.
Sign in
Sign in to Inboxjot in your browser.
You sign in with your Inboxjot account, so you do not copy an API key into the agent.
Setup pages for other tools: Cursor, Codex, VS Code, GitHub Copilot, Devin, Windsurf and Pi.
When you sign in, you choose a workspace and the access that the agent gets. You have three choices:
Each area has a read scope and a write scope. A scope is one permission, such as emails:write. The areas are emails, contacts, campaigns, automations, templates, domains, webhooks and settings.
Inboxjot refuses a tool call when the agent does not have its scope. The MCP page of the dashboard shows every connected tool. You can revoke a tool there at any time.
Ask the agent in your own words. For example:
Send a test email to me@example.com from hello@yourdomain.com.The sender address must be on a domain that you verified in Inboxjot. The email then shows on the Emails page with each delivery event. The tool call also shows in Logs, next to your API requests.
| Task | What the agent does |
|---|---|
| Send email | Sends one email to up to 50 recipients, from your own HTML or from a template. |
| Look up deliveries | Finds an email by recipient or subject and reads its status. It also reads sending totals for a date range. |
| Manage contacts | Adds, changes and deletes contacts. It also reads your segments, topics and contact properties. |
| Draft campaigns | Writes a campaign, changes it and renders a preview. |
| Send a test campaign | Sends the current campaign to up to 5 addresses, with "[Test]" before the subject. |
| Write templates | Creates and changes the templates that your code sends. |
| Read domains | Lists your sending domains and the DNS records that still need to verify. |
Before the agent writes a campaign or a template, it reads two things from Inboxjot:
As a result, the email carries your brand and not an invented one. It also keeps its layout when you open it in the editor.
Campaigns and templates are live documents. The agent and your team can edit the same campaign at the same time. Each change from the agent shows under its name, with a short summary of the change. If a person changes the same block first, the change of the person wins. The agent then reads the block again and works from the new text.
The agent cannot send a campaign to your audience. A campaign that the agent writes stays a draft until a person schedules it. The agent can send a test campaign only to a few addresses that you give it.
The server also tells the agent to ask you before it sends anything. Each send counts toward the emails in your plan. Inboxjot refuses addresses on your suppression list, such as addresses that hard bounced.