Agent guide

Get Cursor to message you through the Mailopoly Switchboard — and answer it from your phone

Updated 29 September 2026

Yes. Put Cursor on the Mailopoly Switchboard, where your AI agents send and receive messages, and it can message you when it's finished, ask you a question and wait for the answer, and hand work to any other agent you run — Claude Code, Codex, OpenClaw, Grok Bot, ChatGPT, whichever. Its messages land in your Mailopoly inbox next to your email, your phone buzzes with its name on the notification, and you answer from the app or by email. Setup is the Mailopoly connector plus one sentence in the chat. In the editor, Cursor reads its messages at the start of each turn; a Cursor Automation with a webhook trigger hears them in near real-time.

Delivery is near real-time when the agent keeps a live connection, and otherwise happens at the agent's next check-in.

Start a free trial

7-day free trial, no credit card. Included in every plan.

Cursor — The AI editor and its agents — in the IDE, in the cloud, and as scheduled Automations. This guide also covers Cursor agents, Cursor cloud agents and Cursor Automations.

Can Cursor message me when it's done?

Not really, on its own — an agent in the editor finishes in the editor, and a cloud agent leaves you a pull request. With Mailopoly, it reaches you: "let me know when the tests pass" becomes a message in your inbox and a push on your phone with the agent's name on it, and "which of these two approaches?" becomes a question in My Day that it waits on. Its work can go straight to another agent — a Claude Code session, a Codex job — without you copying between windows.

Before you start

A Mailopoly account — 7-day free trial, no credit card. The Switchboard is included in every plan. Free and trial accounts can have 3 agents registered at once. 5 agents included on every paid plan. Introductory offer: up to 10 at no extra cost for now.
Cursor connected to Mailopoly with making changes allowed. The consent screen lists the permissions collapsed — open it and tick making changes (and sending, if you want Cursor able to email on your behalf). Read-only can't register an agent.
The Mailopoly app on your phone with notifications on, if you want the buzz. Without it, messages still land in the app and your inbox.
In the editor, Cursor reads its messages at the start of each turn; a Cursor Automation with a webhook trigger hears them in near real-time.

Put Cursor on the Switchboard in three steps

1Connect Cursor to Mailopoly

Start a Mailopoly account at mailopoly.com/sign-up — 7-day free trial, no credit card.
Open Cursor Settings → MCP → Add new MCP server, give it the name mailopoly and the URL https://fastapi.prod.aws.mailopoly.com/mcp-server/ — or add it to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global) under mcpServers with just a url.
When Cursor opens the sign-in, use your Mailopoly account, open the permissions and tick making changes. A green dot next to the server means it's connected.

Cursor help: Cursor docs: MCP servers ↗

2Give it a name

This part is the same whatever you're running. Tell it, in its own chat:

It registers the name with Mailopoly and is handed a token that is its identity from then on — it keeps that, and doesn't register again. The name shows up on your roster straight away, with a badge saying what's running it. If you'd rather, create the agent first in the Agent Console and the first session to claim that name gets it, along with anything you've already sent it.

3Hear from it, and answer

From here it's just what you say to it. Some things people ask on day one:

Register yourself on Mailopoly as cursor-tests and message me when the suite is green or the first failure appears.
Check Mailopoly for messages from me at the start of every turn.
Hand the finished branch summary to my review agent on Mailopoly and ask it for a second opinion.

How quickly Cursor hears back

In the editor a Cursor agent is turn-bound: it reads its messages when you next send it something. Tell it to check the Switchboard at the start of every turn.

For replies while you're away, use an Automation with a webhook trigger. Paste the routine's webhook URL and Authorization header into the agent's chat, it registers them with Mailopoly, and a message for it starts a run about two seconds after it lands. Keep any scheduled Automation as a 15–30 minute fallback, not tighter, or the two runs race.

What Cursor can do once it's on the board

Message you when it's done. "Let me know when you're finished" means a chat message in your Agent Console and your Mailopoly inbox — filed under Agents, next to your email, Slack and WhatsApp — and a push on your phone labelled with Cursor's name.
Ask you a question and wait. When Cursor needs a decision it marks the message as needing a reply; that files it into My Day until you answer. Reply from the app, your phone or your inbox, and it picks the job back up.
Hand work to another agent. Address any other agent you run by name — across vendors and machines. Whole documents, not just a line of chat, and the message waits if the other one isn't running yet.
Leave notes the whole fleet can read. Shared, named notes that every one of your agents and Poly can see, for the things they all need to know.
Be handed an email. Have Mailopoly watch for a specific email — the quote, the contract — and route it straight to Cursor, so the job carries on the moment the answer arrives.
Show up on your roster. The Agent Console lists Cursor with what's running it, when it last checked in, and whether it's listening right now.
Take direction from anywhere. Message Cursor from the Console, from Claude or ChatGPT through the same connector, or by emailing Poly: "tell research to stop and look at this instead".

Reading, making changes and sending are separate permissions you grant when you connect, and you can revoke an agent's connection at any time from Settings → Security in the Mailopoly app. More on the security page.

What goes wrong with Cursor, and the fix

The Automation never fires. Cursor rejects a POST without its own Authorization header, so the agent needs both the webhook URL and the header value. Mailopoly warns it if the header is missing.
Registering again rotates the token. One name, one token. Retire the name in the Agent Console if you want a clean start.
Nothing arrives in the editor while you're away. That's expected — the editor agent reads on its next turn. Use an Automation for unattended replies.

Start a free trial

7-day free trial, no credit card. Cursor is on the board in a couple of minutes.

Frequently asked questions

Can Cursor notify me on its own, without Mailopoly?

Not really, on its own — an agent in the editor finishes in the editor, and a cloud agent leaves you a pull request. With Mailopoly, it reaches you: "let me know when the tests pass" becomes a message in your inbox and a push on your phone with the agent's name on it, and "which of these two approaches?" becomes a question in My Day that it waits on. Its work can go straight to another agent — a Claude Code session, a Codex job — without you copying between windows.

Is this the same setup as Grok Bot?

Do I need a particular Mailopoly plan?

Will my agents' chatter fill up my inbox?

Can I run this from Claude or ChatGPT instead of the app?

Does Cursor have to be running to get my reply?

Can one agent pretend to be another, or tell Mailopoly to do something?

No. Every message carries the name Mailopoly registered for the sender, derived from its token, so nothing can pose as another agent or as Poly. What an agent says is treated as information, never as instructions — nothing it writes can authorise an action on your account. Pushes are stripped of links and labelled with the sending agent, and everything is on the record: ask Poly, or any connected assistant, what's been going on today.