Developer tools support remote MCP servers, each with its own command or file. Add Mailpro to create templates, test lists and real sends while you code your integration.
Claude Code (Anthropic) and Codex (OpenAI) run from the command line; Cursor and VS Code with GitHub Copilot are editors. All of them can call a remote MCP server and sign in with OAuth.
For a developer integrating Mailpro, it saves time: instead of reading the documentation and then writing a test script, you ask the assistant to create the test list, the template and the send, in the real account.
For your own application in production, the Mailpro API remains the right way; the MCP server is for the assistant that helps you write it.
| Claude Code | claude mcp add --transport http mailpro <server address> |
|---|---|
| Cursor | .cursor/mcp.json (project) or ~/.cursor/mcp.json (global) |
| VS Code | “MCP: Add Server” command, .vscode/mcp.json file |
| Codex | codex mcp add mailpro --url <server address> |
| Sign-in | OAuth with automatic registration in all four tools |
It creates and edits the email template in Mailpro while you write the code that sends it.
A test list, dummy contacts, tags: in a single request.
It sends the test email to your address, just as your application will.
Which lists, which custom fields, which verified senders: it reads the account before you code.
Claude Code: claude mcp add --transport http mailpro <server address>, then in the session /mcp › Authenticate.
Cursor: in .cursor/mcp.json, {"mcpServers": {"mailpro": {"url": "<server address>"}}}; Cursor offers the OAuth sign-in on first use.
VS Code: “MCP: Add Server” command › HTTP, or in .vscode/mcp.json under the servers key (not mcpServers).
Codex: codex mcp add mailpro --url <server address> then codex mcp login mailpro.
Replace <server address> with the server address shown in your Mailpro account, on the AI Assistants (MCP) page. The list of the 51 tools and their parameters is on the developer portal.
The server added in the Codex command line also works for the editor extension and the desktop app.
The configuration file can go into version control; the OAuth tokens stay on each machine.
Connect the assistant to a test Mailpro account during development: test sends don't get mixed up with your campaigns.
On the Mailpro side, the rules are the same for every assistant: by default, each send waits for your approval, or goes out directly within a daily cap; a log keeps track of everything, and one click suspends all sends. The details.
No: your application in production calls the Mailpro API. The MCP server is for the assistant that helps you during development.
No: VS Code reads .vscode/mcp.json with the servers key; Cursor reads .cursor/mcp.json with the mcpServers key.
No: all four tools sign in with OAuth, using your Mailpro account.
All questions: AI assistants FAQ.
Create a free Mailpro account, connect your assistant from the AI Assistants page of your account, and stay in control of every send.
