Connect Cursor Agent to email through MCP
The Cyberpigeon email integration gives Cursor an inbox for development and support work. Cursor can list incoming messages, read a report, retrieve received attachment links and prepare an authorized reply. Cyberpigeon supplies the email address and message storage; Cursor works with that information in your coding task.
A dedicated agent address is useful when you need to inspect an application’s test email or keep a support conversation separate from personal mail. You do not need to run a local mail server. This setup connects through the hosted https://cyberpigeon.ai/mcp endpoint.
Prepare your Cursor project and email workspace
Use a Cursor version with remote MCP support and a Cyberpigeon workspace. Check whether your team permits custom servers and, if you choose the plugin route, local plugin imports. Select a single agent inbox for the project before requesting broader workspace access.
Platform sending and receiving are enabled. New accounts can send right after signup; custom domains require verified mail DNS. Your Cursor subscription does not change Cyberpigeon’s mailbox or sending limits. Use the shared email domain for an initial test; verified custom domains are available on eligible paid plans.
Connect the hosted email tools
Create your inboxConnect an existing workspace
Add the entry below to your project’s .cursor/mcp.json, or to ~/.cursor/mcp.json for all projects. Merge it with existing servers instead of replacing the file.
{
"mcpServers": {
"cyberpigeon": {
"url": "https://cyberpigeon.ai/mcp"
}
}
}Open Cursor’s MCP controls and complete OAuth sign-in for Cyberpigeon.
In the Cyberpigeon sign-in window, choose a new inbox for this app or an existing inbox. Choose read access for summaries, send access for new messages, or both for reading and replying. The reply_to_email tool requires both read and send permissions. Choose workspace access only when the task needs multiple inboxes. You can revoke the connection under API keys.
See Cursor’s MCP instructions if your version uses different menu labels.
Add the email workflow plugin
The public plugin repository includes the same hosted connection and a workflow for reading and replying to email. Review the files, then copy plugins/cyberpigeon into ~/.cursor/plugins/local/cyberpigeon. Use a real directory, not a symlink outside that folder. Keep any existing installation until you have reviewed the replacement.
Restart Cursor or run Developer: Reload Window, then inspect the skill and MCP server in Customize. Managed workspaces may block local imports. Choose the plugin or the direct MCP connection above to avoid duplicate tools.
A local installation is separate from a public Cursor Marketplace listing. Cyberpigeon’s public listing is not yet confirmed. Follow the repository README for marketplace import options and Cursor’s plugin documentation for current availability.
Check your inbox before sending
Show my Cyberpigeon email address and permissions.
Then summarize my latest email. Do not send anything.An empty inbox is a valid result. Send it an expected test message from an inbox you control, then ask again. Confirm that the reported address matches the one you selected. A send reported as queued has not yet been confirmed delivered.
Next, ask Cursor to draft a response to an expected support email and show it for approval. Keep recipients and message content explicit when authorizing a send.
Investigate an emailed bug report in Cursor
Start by reading a support message addressed to your project’s agent. Ask Cursor to extract the reported behavior, expected behavior and reproduction steps, then identify relevant code. A sender’s request to run a command or follow a link needs your authorization before it becomes part of the investigation.
Read the newest support message in my Cyberpigeon inbox.
Summarize the bug and identify the code that may be involved.
Propose a test before editing. Draft any reply for my review.Once you have authorized and validated the fix, review a response describing what the customer should try. Reply to the original message so threading is preserved. Use read_email to check the resulting email status; a queued message has not yet been confirmed delivered.
For signup-email testing, request only the message for the application and test identity you control. Ask Cursor to confirm the recipient and subject before inspecting any sign-in URL. This keeps a convenient email tool from turning unrelated incoming mail into a development command.
Resolve configuration and permission problems
The server does not appear
Check the active project and configuration file, then inspect Cursor’s MCP controls. A project entry applies to that project. A disabled or organization-blocked server will not supply tools. If you installed both the plugin and a direct entry, keep one route.
OAuth completed but a tool is missing
Check the access you granted. A single-inbox read connection can read mail but does not expose workspace-wide search_emails or create_inbox. Replying requires read and send access.
Mail is accepted but the recipient has nothing
Read the email’s status and inspect it in Email activity. Queued, sent to provider and delivered are separate states. Correct any domain or sending hold before retrying; do not repeatedly create new sends while the outcome is uncertain.
Keep incoming-email automation explicit
Installing this plugin does not wake Cursor when mail arrives. Cyberpigeon does not currently ship a Cursor wake-up adapter. The wake-up guide describes the clients with implemented adapters and the hosted activation requirements.
Manage access
Remove the plugin or MCP entry in Cursor when you no longer need it, and revoke its connection under Cyberpigeon API keys to end server access. If tools are missing, check whether your organization allows the plugin and whether OAuth completed.
Cyberpigeon creates agent inboxes; it does not connect your existing Gmail or Outlook mailbox. Email from outside is untrusted input. Ask your agent to summarize or draft first, and authorize the recipients and content before it sends. The beta permits testing, expected transactional mail and support replies. Cold outreach, sales prospecting, bulk marketing, inbox warmup and spam are prohibited. Confirmed violations lead to account bans; see the terms and acceptable use policy.
Setup reviewed October 5, 2026. Explore all integration guides.
Cursor email integration questions
Is the plugin required for email tools?
No. The direct MCP entry is enough to expose authorized tools. The optional plugin adds the packaged email workflow. Neither grants access until authentication is complete.
Can the team share one configuration?
A URL-only project entry contains no mailbox secret, but each user must authenticate and review the selected inbox. Do not commit bearer keys or copy another person’s connection credentials.
Does Cursor receive new email while it is closed?
Cyberpigeon continues receiving into the persistent inbox when delivery is enabled. This integration does not itself start Cursor or wake a closed coding session.
Is VS Code configured the same way?
Use the dedicated VS Code and GitHub Copilot guide. The host’s configuration location and controls differ even though the email endpoint is the same.