Connect Mailbridge to your agent.
Codex is the clearest supported path today. Other clients may work if they support remote MCP with bearer-token authentication.
Before you connect
Prepare Mailbridge once.
You need a Mailbridge account, the Gmail addresses you want to use and an MCP credential. The token is generated and shown only once.
-
01
Open your account
Sign in to the Mailbridge app.
-
02
Connect Gmail
Add each Gmail account you want available.
-
03
Create a credential
Copy the token and keep it somewhere secure.
Choose where you’ll use it.
Start with the verified Codex flow, or use the connection details with another compatible client.
Codex
Add Mailbridge.
These are the currently verified client instructions.
-
1
Make the token available
Set
MAILBRIDGE_MCP_TOKENin the environment that starts Codex. Use a secret manager or secure prompt rather than saving the token in source control or shell history. -
2
Add the remote server
Run this command in your terminal:
codex mcp add mailbridge \ --url https://mailbridge.aide.tools/mcp \ --bearer-token-env-var MAILBRIDGE_MCP_TOKEN -
3
Check the configuration
Run
codex mcp listto confirm Mailbridge is listed, then restart Codex after changing its environment or configuration.
Other clients
Use the connection details.
- Transport
- Streamable HTTP
- Server URL
- https://mailbridge.aide.tools/mcp
- Authorization
- Bearer <your token>
Some clients only support OAuth for remote MCP servers. Those clients cannot connect to Mailbridge yet. Browser-based clients must also send an origin allowed by Mailbridge. Add named clients here only after their connection flow has been tested end to end.
Confirm the connection.
Ask your client to list your connected mailboxes. Once they appear, you can work across them in the same request.