Connect SuperMailbox to your CRM
Give each CRM user a secure, OAuth-authorized connection to the mailboxes they choose. Your CRM can find customer conversations, show verified email context, and prepare or send replies through the SuperMailbox MCP server.
How the connection works
Connect a mailbox
The user connects Gmail, Outlook, or another supported mailbox to SuperMailbox. Provider sign-in is a separate step from CRM authorization.
Authorize the CRM
The CRM opens SuperMailbox OAuth in a browser. The user signs in, reviews the client and requested scopes, and approves the connection.
Use MCP tools
The CRM calls the remote MCP server with the user's access token. The user selects an authorized mailbox and the CRM works within that grant.
Connection settings
Use an MCP client or SDK that supports remote Streamable HTTP and OAuth authorization discovery. It should handle the browser authorization flow and send the resulting access token with MCP requests.
- MCP server URL
https://api.supermailbox.app/mcp- Authorization
- OAuth 2.0 · Authorization Code · PKCE S256
- Scopes
openid email mail.accounts.read mail.messages.read mail.send
Request only the access your workflow needs. A CRM that reads customer correspondence and sends replies can request:
Find and verify a conversation
- Call list_mail_accounts to let the user select an available mailbox. Treat canSend as a hint; sending is checked again when the action runs.
- Use search_emails or search_threads_by_recipient to find candidates. Recipient search returns metadata only; fetch the chosen thread and verify it before linking it to a CRM record.
- Search results can be bounded or incomplete. Respect coverage and completeness fields; an incomplete or empty partial result does not prove that no matching message exists.
- Account, message, and thread IDs are opaque and belong to the current user's grant. Resolve and validate them under that same user's connection.
Prepare and send replies safely
- Show the selected mailbox, recipient, and reply content in the CRM before the user confirms a send.
- send_email and reply_to_email return a queued operation. Poll get_mail_action with the same operation ID and required scopes until it reaches a final status.
- A queued receipt is not proof of delivery. If a send is uncertain, check that same operation; never retry it automatically with a new operation ID.
Security and access control
- Use the OAuth authorization-code flow with PKCE S256 through the MCP client's supported discovery flow. Keep client secrets and tokens on the server; never expose them to browser code or logs.
- Create a separate connection for each CRM user. Do not share one user's token or opaque mailbox identifiers with another user.
- Ask for mail.send only when the CRM needs to send. Users can revoke the CRM's SuperMailbox connection from their connected-app settings.

