https://app.mailsoftly.com/mcp



Yes. Mailsoftly is an email marketing and automation platform that AI agents can operate end to end. Connect Claude, ChatGPT, Claude Code, Cursor, VS Code or any MCP client to the hosted server at app.mailsoftly.com/mcp, sign in with OAuth, and the agent gets 139 documented tools for contacts, lists, segments, templates, campaigns, automations, forms, landing pages, reports and domain authentication. Agents and apps you build yourself use the REST API with an API key, including a transactional email endpoint for one-to-one messages, plus webhooks in both directions.
Drafting and building are open from the first minute. Sending is a separate permission a person grants on the consent screen, and every account's first campaigns pass a short content review, so email an agent prepares reaches the inbox instead of spam. The MCP server and the API are included on every plan. Mailsoftly starts free with your Google or Microsoft account, and paid plans start at $19 per month for 1,000 contacts ($15 on annual billing).
Mailsoftly is listed in the Claude directory. Press Connect, sign in, and Claude can build lists, draft campaigns, set up automations and read results.
Connect Claude →Mailsoftly is in the ChatGPT app directory. Connect it, approve the permissions, and ChatGPT works in your account with the same tools and rules as every other client.
Add Mailsoftly to ChatGPT →Any assistant that supports remote MCP servers with OAuth connects with one URL. It registers itself, sends you to Mailsoftly to sign in, and gets a token scoped to what you approved.
About the MCP server →Add the server over HTTP, then run /mcp inside Claude Code to sign in.
claude mcp add --transport http mailsoftly https://app.mailsoftly.com/mcp
Add the server to your MCP config and approve the sign-in when Cursor opens it.
.cursor/mcp.json
{"mcpServers":{"mailsoftly":{"url":"https://app.mailsoftly.com/mcp"}}}Agent mode picks up servers from the workspace MCP file and starts the OAuth sign-in on first use.
.vscode/mcp.json
{"servers":{"mailsoftly":{"type":"http","url":"https://app.mailsoftly.com/mcp"}}}Register the server, then log in once to grant the scopes you want.
codex mcp add mailsoftly --url https://app.mailsoftly.com/mcp codex mcp login mailsoftly
Add the server over HTTP and authenticate from the CLI when prompted.
gemini mcp add --transport http mailsoftly https://app.mailsoftly.com/mcp
Clients that support remote servers take the URL in their MCP config and run the OAuth sign-in on first use.
mcp config
{"mailsoftly":{"url":"https://app.mailsoftly.com/mcp"}}Menus change between client versions; the server URL does not. Full setup notes are in the MCP documentation.
Every MCP tool maps to a documented endpoint under app.mailsoftly.com/api/v3. Authenticate with an API key in the Authorization header, or with an OAuth token when your agent acts for other Mailsoftly accounts. 300 requests per five minutes.
curl https://app.mailsoftly.com/api/v3/get_contact_lists \ -H "Authorization: $MAILSOFTLY_API_KEY"
Send notifications, confirmations, reminders and one-time links from your agent or app. Use a saved template or a subject and body, pass an idempotency key for safe retries, and follow every message by message_id or a signed status webhook. Mail leaves from your authenticated domain and passes the same suppression checks as everything else.
curl -X POST https://app.mailsoftly.com/api/v3/send_transactional_email \
-H "Authorization: $MAILSOFTLY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"to":"[email protected]","template_id":42,"idempotency_key":"order-1001"}'Point your framework at the OpenAPI spec to generate tools. Each operation declares its permission scope, and tools.json lists every hosted tool with read only and destructive flags so your agent knows what is safe to call.
Open the spec →Push contacts, list changes, tags, form entries and suppressions in through inbound webhooks. Start an automation from any outside event, and let an automation step post data back to your agent.
Integrations overview →Connect Mailsoftly to thousands of apps and agent workflows without writing code, on the same account and the same rules.
See integrations →Prefer a process on your own machine? The open source stdio server builds one tool per live endpoint from the OpenAPI spec and signs in with your API key.
Local server setup →Read and draft scopes are what most agents need. The send permission is its own unchecked box on the consent screen, so an agent can prepare everything while a person presses send.
When a send is held, the tool returns a gate object with the reason, a message the agent can relay word for word, and the exact steps that unlock it. No dead ends, no guessing.
Campaigns go out from your own Google Workspace or Microsoft 365 account or your authenticated domain, and first campaigns get a human content review. Agent email lands like any other.
An agent can write a short HTML body that Mailsoftly places in a responsive layout, start from a saved template, or bring a complete HTML email that is sent exactly as written.
Describe the flow and the agent builds it as a draft: trigger, waits, conditions, emails, tags, webhooks. Activating it takes the send permission and a verified account.
Plan caps apply exactly as in the app, and the response says which limit applies and how to raise it, so the agent tells the user something useful instead of failing.
It is a hosted Model Context Protocol server at app.mailsoftly.com/mcp that exposes your Mailsoftly account as 139 documented tools. Add the URL to any MCP client that supports remote servers, sign in on the Mailsoftly consent screen, and choose the permissions to grant. There is nothing to install and no key to copy. A local stdio server that uses an API key is also available.
Yes. The MCP server and the REST API are included on every plan, including the free plan with 500 contacts and 2,000 emails a month, which starts with your Google or Microsoft account and no credit card. Paid plans start at $19 per month for 1,000 contacts ($15 on annual billing).
Run claude mcp add --transport http mailsoftly https://app.mailsoftly.com/mcp, then run /mcp inside Claude Code and sign in. Claude Code can then create lists, import contacts, build automations and draft campaigns for the product you are working on.
Add the server URL to your MCP config: in Cursor, an entry with url https://app.mailsoftly.com/mcp in .cursor/mcp.json; in VS Code, an entry of type http with the same URL in .vscode/mcp.json. The editor opens the Mailsoftly sign-in the first time the agent uses a tool.
Yes. Mailsoftly is listed in the Claude directory and in the ChatGPT app directory. Both connect to the same hosted server with OAuth sign-in, so the tools, permissions and rules are identical.
Only if a person grants the send permission, which is a separate checkbox on the consent screen and off by default. Without it the agent can do everything else: manage contacts and lists, write and edit drafts, build automations and read reports. Every account's first campaigns also pass a short content review before they go out.
Yes. The REST API has a transactional endpoint for one email to one recipient: notifications, confirmations, reminders and one-time links. Use a saved template or a subject and body, pass an idempotency key so retries never send twice, and track each message by its message_id or a signed status webhook. Transactional email leaves from your authenticated domain, passes the same suppression checks as campaigns, and is available through the API rather than as an MCP tool.
Yes. Use the REST API at app.mailsoftly.com/api/v3 with an API key in the Authorization header, or OAuth when your agent acts for other accounts. The OpenAPI spec declares the permission scope of every operation, tools.json lists every hosted tool with read only and destructive flags, and llms.txt gives agents a plain text map of the docs.
Sign up free, paste one URL into your agent, and build your first campaign in plain language.
Start free with Google Start free with Microsoft 365