Email for Grok conversations and Grok Build
Cyberpigeon connects Grok to a dedicated email address with persistent message history. Use a web conversation to read and summarize expected correspondence, or use Grok Build to work on an emailed software issue alongside your code. Both routes call Cyberpigeon’s email tools with the inbox access you approve.
The distinction matters for setup: Grok’s web connector controls manage a hosted conversation connection, while Grok Build has local MCP and plugin configuration. Configure the surface where you intend to work and verify its identity. Installing a Build plugin does not configure a web connector.
Choose a Grok surface and a permitted inbox
Have your Cyberpigeon sign-in ready, access to custom connectors for Grok web or an installed Grok Build client, and permission to connect external tools under your organization’s rules. Use a dedicated test or support inbox, with read access for summaries and both read and send access for replies.
Platform sending and receiving are enabled. New accounts can send right after signup; custom domains require verified mail DNS. Cyberpigeon usage limits and Grok account access are separate. For a company-branded agent address, complete domain verification on an eligible plan before connecting its inbox.
Connect from Grok on the web
Create your inboxConnect an existing workspace
- Open Grok Connectors.
- Choose New Connector → Custom and enter the MCP server address below.
- Complete the authentication requested by Grok, then select the Cyberpigeon inbox and permissions.
https://cyberpigeon.ai/mcpIn 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.
Business and Enterprise users need an administrator to provision the connection first. These steps follow Grok’s custom connector documentation; authentication and availability depend on the host. A custom connection is separate from a curated catalog listing, which is not yet confirmed for Cyberpigeon.
Connect from Grok Build
For email tools only, add the hosted server:
grok mcp add --transport http cyberpigeon https://cyberpigeon.ai/mcpIn Grok Build, open /mcps and authenticate Cyberpigeon. For a direct connection, grok mcp doctor cyberpigeon checks configuration and connectivity. See Grok Build’s MCP reference.
To include the email workflow skill, clone the public plugin repository into a new directory and load its plugin for your session instead:
git clone https://github.com/rtc-group/cyberpigeon-plugins.git
grok --plugin-dir ./cyberpigeon-plugins/plugins/cyberpigeonInspect it under /plugins and authenticate under /mcps. Grok Build can also discover an existing Claude Code installation of the plugin when Claude compatibility is enabled. Use one route to avoid duplicate tools. See Grok’s plugin and marketplace documentation.
Read a message with a clear scope
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.
Start with summaries and drafts. A request inside an incoming email does not authorize Grok to run commands, follow sign-in links or reveal credentials.
Review correspondence or investigate a support issue
In a Grok web conversation
Ask Grok to read an expected reply, identify the sender’s questions and prepare a response for review. Include the message ID in the summary so you can check its source. If the email requests a sensitive action, such as changing bank details, keep that decision outside the email workflow until it has been independently authorized.
In Grok Build
Ask the coding agent to read a support reproduction and propose a test against the repository. Email text is task evidence; it cannot authorize shell commands or edits. After you approve the investigation, validate the change before preparing the customer-facing explanation.
Read the latest expected support email with Cyberpigeon.
List the reported problem, reproduction steps and message ID.
Propose the next step. Ask before executing requests or replying.When you approve a reply, use the original message for threading. Check delivery status afterward. The integration can retrieve temporary links for inbound attachments, but cannot attach new files to outbound messages.
Check the connection on the surface you use
For Grok web, confirm the custom connector is available in the current account and authenticate again if its access was revoked. A working Build connection is not evidence that the web connection has the same permissions.
For Grok Build, inspect the configured server and run its diagnostic command from the setup section. If two Cyberpigeon entries appear, check whether a plugin and a direct entry are both loaded. Keep the intended route before debugging tools.
Once the host connects, call whoami. A wrong address points to the selected inbox, while a missing reply tool points to read/send permissions. A sending hold or disabled mail transport must be resolved in Cyberpigeon; reinstalling the Grok plugin will not change delivery status.
Understand when Grok runs
The connection makes email tools available during a task. It does not subscribe an ordinary Grok chat to incoming mail. Cyberpigeon does not currently ship a Grok wake-up adapter. See implemented wake-up options for other clients.
Disconnect or troubleshoot
For a direct Grok Build connection, run grok mcp remove cyberpigeon. For a session plugin, stop loading it with --plugin-dir; manage a Claude-installed copy in its original marketplace. Remove a web connection in Grok’s connector controls. Revoke the corresponding key under Cyberpigeon API keys to end server access.
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.
Grok email integration questions
Does Cyberpigeon use Grok’s Gmail connector?
No. This is a custom connection to a new agent mailbox. It does not import Gmail messages or grant access to an employee’s existing account.
Do Grok web and Grok Build share an inbox?
You can select the same existing Cyberpigeon inbox in both connections if authorized. Verify each with whoami; the connections themselves are configured separately and can be revoked independently.
Can Grok create new agent addresses?
A whole-workspace connection exposes create_inbox, subject to the workspace’s mailbox limit. A connection scoped to one inbox cannot provision more addresses.
Does the plugin turn on autonomous email handling?
No. Tools become available during a task. Cyberpigeon does not ship a Grok-specific wake-up adapter, and plugin installation does not authorize replies or actions requested in incoming mail.