Connect an email inbox to Grok

Connect from Grok on the web

Create your inboxConnect an existing workspace

1. Open Grok Connectors.
2. Choose New Connector → Custom and enter the MCP server address below.
3. Complete the authentication requested by Grok, then select the Cyberpigeon inbox and permissions.

https://cyberpigeon.ai/mcp

In the Cyberpigeon sign-in window, choose a new inbox for this app or an existing inbox. Review the requested read/send access before allowing the connection. 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/mcp

In 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/cyberpigeon

Inspect 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.

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, prospecting, bulk marketing and spam are prohibited.

Setup reviewed October 5, 2026. Explore all integration guides.