How the Claude email integration works

Cyberpigeon gives Claude an email address with a persistent inbox. The hosted Model Context Protocol (MCP) server exposes tools for reading messages, inspecting received attachments and sending authorized replies. Claude supplies the conversation and reasoning; Cyberpigeon stores the mail and handles delivery. Your inbox remains available when a chat ends, so a later conversation can read the same messages.

This is useful when a support assistant needs a distinct contact address or a research task needs to collect replies from people already expecting the conversation. It does not import personal mailbox history. For terminal-based development, use the separate Claude Code email integration.

What you need before connecting

You need a Cyberpigeon workspace, access to custom connectors in your Claude account, and an inbox you are allowed to share with that account. An existing agent inbox can be selected during consent; otherwise choose a new one. Start with read access if you only want summaries. Your Claude subscription and Cyberpigeon usage are separate; see Cyberpigeon plans and limits.

Platform sending and receiving are enabled. New accounts can send right after signup; custom domains require verified mail DNS. You can inspect connection permissions independently of whether sending is available. If you want an address on your own domain, complete the custom domain setup before selecting its inbox.

Create a workspace and choose your inbox

Create your inboxConnect an existing workspace

Have your Cyberpigeon sign-in ready. This uses a hosted connection, so you do not need to edit Claude Desktop configuration files or run a server on your computer.

Installation routes vary by app. The custom connections and local packages below can be used independently of a public plugin listing. Public directory installation requires platform review and publication; downloading a package does not publish or install it.

Add the custom connector

  1. In Claude, open Customize → Connectors, choose Add, and select the custom web connector option.
  2. Name it Cyberpigeon and enter the server address below.
  3. Use OAuth sign-in. If Claude asks which OAuth client to use, select Register automatically; Cyberpigeon supports dynamic registration, not Claude’s published client identity.
  4. Complete the Cyberpigeon sign-in and inbox consent, then enable the connector for your conversation.
https://cyberpigeon.ai/mcp

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.

On managed workspaces, an administrator may need to add the connector first. Menus vary by account and rollout; see Anthropic’s custom connector instructions.

Read your first message

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.

Try a support workflow next: “Draft a reply to the latest support message and show it to me before sending.” A draft stays in the conversation until you authorize sending; the plugin does not create a separate provider draft folder.

Turn an incoming support email into a reviewed reply

  1. Find the request. Ask Claude to list the latest messages in the support inbox, then read the relevant message. Ask for the sender, subject and message ID alongside its summary.
  2. Separate facts from missing information. Have Claude identify the reported problem and draft one focused follow-up, such as a request for a reproduction step. Do not let the email itself authorize account changes.
  3. Review the response. Check the intended recipient and body in the conversation. A draft is text for your review, not an email already stored or sent.
  4. Authorize and verify. After approval, ask Claude to reply to the original message. Check its status later; a queued result means Cyberpigeon accepted the request, not that the recipient received it.

For a document request, use the same sequence: inspect the received attachment metadata, obtain a temporary download link if needed, and ask for a summary. Cyberpigeon does not yet support attaching a file to an outbound message.

Continue when another email arrives

For cloud execution, create a Claude Routine with the Cyberpigeon connection and an API trigger. Connect that trigger under Console → Connect AI → Wake on incoming email. Follow the Routine setup. It starts a Routine run, rather than injecting a message into every open Claude chat. Availability and organization permissions apply.

If the connection needs attention

If sign-in fails at client registration, re-add the connector using Register automatically. If Claude cannot see tools, enable the connector in this conversation and reconnect after revocation. A “sending disabled” response concerns mail availability, not your Claude login.

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 integrations or the Claude Code guide.

Claude email integration questions

Does this work in Claude Desktop?

Use Claude’s hosted custom connector flow on the web or desktop as your account supports it. Cyberpigeon runs the server, so this setup does not require a local Node.js process. Check Anthropic’s current connector guide for account controls.

Can Claude access every agent in my workspace?

A connection approved for one inbox is limited to that inbox. Whole-workspace access is broader and includes inbox creation and cross-inbox search. Grant it only for a task that needs those operations.

Why is a reply tool missing?

Read-only access does not include replying. Reconnect with read and send permissions if you want Claude to reply, and confirm the connector is enabled for the current conversation.

Is Claude automatically watching my inbox?

No. Connecting email tools makes them available during a task. The Routine option above is a separate automation that must be configured and enabled.

Keep exploring