Add one URL under Connectors on grok.com and Grok can read, search, send, reply, forward, schedule and organize mail across every inbox you have connected.
Go to grok.com/connectors, click New Connector, select Custom, paste https://mcpemails.com/api/mcp as the MCP server URL, then sign in to MCPEmails when Grok asks and approve the scopes. On Grok Business and Enterprise, a team admin adds the server in the cloud console first.
Grok runs the standard MCP OAuth flow against this server. It registers itself with RFC 7591 dynamic client registration, so there is no client ID to create, and authorizes with authorization code plus PKCE using S256. No client secret is ever transmitted, and the token carries only the scopes you approve on our consent screen. The access token it receives lasts an hour and refreshes itself; it is listed in Dashboard, API Keys as OAuth: followed by the client name, which is where you revoke the connection.
Everything on this page is a way of getting this URL into Grok.
| Field | Value |
|---|---|
| MCP server URL | https://mcpemails.com/api/mcp |
| Transport | Streamable HTTP (MCP 2025-06-18) |
| Authentication | OAuth 2.1, authorization code with PKCE. No API key. |
Four steps. The first two are the same for every client, the rest are specific to this one.
Sign up at mcpemails.com, no card required, then go to Dashboard, Inboxes, Connect Inbox. Outlook and Microsoft 365 connect with Sign in with Microsoft; Gmail, iCloud, Fastmail, Yahoo, Zoho and Yandex take an app-specific password; anything else connects over plain IMAP and SMTP. The free plan holds one inbox, forever.
Go to grok.com/connectors while signed in to Grok.
Click New Connector, then select Custom. Paste https://mcpemails.com/api/mcp as the MCP server URL.
Complete the authentication Grok asks for: it sends you to MCPEmails, where you sign in and approve the scopes you want Grok to hold. Grok then discovers the tools the server exposes.
Start a chat and ask something like "which inboxes do I have?" or "summarize my unread mail". Grok uses a connector's tools when your question relates to it.
Official Grok documentation for remote MCP servers: https://docs.x.ai/grok/connectors
Wondering which mailbox to connect first? See the provider compatibility matrix
On Grok Business and Enterprise plans, members cannot add the server themselves until a team admin provisions it. The admin signs in to console.x.ai, selects the team, opens Grok Business, Connectors, clicks + Add Connector, selects Other and enters https://mcpemails.com/api/mcp. That needs Team Read-Write permissions. Each member then connects their own MCPEmails account on grok.com/connectors.
xAI documents adding a custom connector only at grok.com/connectors, with no steps for the iOS or Android apps. Add the connector from a browser.
The consent screen lets you hand Grok read:email and search:email alone. That is enough for triage, summarising and finding things, and it removes every irreversible action from the table while you decide how much further you want to go. If you do grant send:email, an inbox owner can turn on human approval so each send waits for a person.
Go to grok.com/connectors, click New Connector, select Custom, paste https://mcpemails.com/api/mcp, then sign in to MCPEmails and approve the scopes. Grok then has tools for reading, searching, sending, replying, forwarding, organizing and scheduling mail.
No. Grok runs the OAuth flow when you add the connector, so nothing secret is pasted into Grok. A bearer key is available for other clients that cannot do that.
No. Grok's built-in Gmail and Outlook connectors reach those two providers. MCPEmails is a custom connector that reaches Outlook, Microsoft 365, Gmail, iCloud, Fastmail, Yahoo, Zoho, Yandex and any IMAP mailbox through one connection, with scopes you choose and optional human approval on sends.
Outlook.com and Microsoft 365 over Sign in with Microsoft, where a work account may need an IT admin to approve the app once; Gmail, iCloud, Fastmail, Yahoo, Zoho and Yandex with an app-specific password; and any other mailbox that speaks IMAP and SMTP on the standard ports. Grok sees them all through the same connection: it calls inbox_list first to discover every connected mailbox and its id, so there are no UUIDs to paste anywhere.
Only if you let it. Sending is gated on the send:email scope, so a token without that scope cannot send at all. On top of that, an inbox owner can require human approval in the dashboard, which holds every send, reply, forward, draft send and scheduled send until a person releases it.
No. Every message is fetched live from your provider for the request that asked for it and handed straight to your client. Only the encrypted OAuth token or app password is kept, so future calls can authenticate. Deleting the inbox in the dashboard, or revoking access at your provider, ends the connection at once.
One URL, one sign-in. One inbox free forever, no card required.