Ask Mistral's assistant about your mail and have it act on it. Read, search, send, reply, forward, schedule and organize mail across every inbox you have connected.
In Le Chat, open Connectors, click + Add Connector, choose the Custom MCP Connector tab, paste https://mcpemails.com/api/mcp as the Server URL, click Connect and sign in to MCPEmails.
When you enter the Server URL, Le Chat detects how the server authenticates. Mistral asks OAuth servers to answer an unauthenticated request with 401 and a WWW-Authenticate header, and this server does, pointing at its OAuth metadata, so Le Chat runs OAuth 2.1 instead of asking for a bearer token. 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 Le Chat.
| 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.
At chat.mistral.ai, open the Connectors page from the sidebar, click + Add Connector and select the Custom MCP Connector tab. Adding one is an administrator feature; on a Free, Pro or Student plan the account owner is the administrator.
Fill in Connector name with a unique name without spaces or special characters (for example MCPEmails), paste https://mcpemails.com/api/mcp into Server URL, and optionally add a Description.
Click Connect. Le Chat detects OAuth and opens the MCPEmails sign-in; approve the scopes you want it to hold. If an Authentication Method field appears, choose OAuth 2.1 and leave any client ID and secret empty.
In a conversation, click the + icon or type /, select Tools and turn on the MCPEmails connector. Then ask it to list your inboxes.
Official Le Chat documentation for remote MCP servers: https://docs.mistral.ai/le-chat/knowledge-integrations/connectors/mcp-connectors
Wondering which mailbox to connect first? See the provider compatibility matrix
Mistral has renamed Le Chat to Vibe, and its documentation files connectors under Work. The address is still chat.mistral.ai and the Connectors page and its labels are the same, so the steps above apply whichever name you see.
Custom MCP Connectors are an administrator-only feature. On Free, Pro and Student plans the account owner is the administrator, so you can add it yourself. In a Team or Enterprise workspace, ask a workspace admin to add the connector; it then shows up in the organization list for members to turn on in their own chats. Organization admins can also switch MCP Connectors off for a workspace.
Le Chat asks before a connector acts, with Continue, Always allow and Decline. To pre-authorize a function for good, open Connectors, My Connectors, the connector card, Functions, and turn on its Always allow toggle. Allowing the read tools saves clicks. Leave the send, reply and forward tools on manual approval, or leave send:email off this connection entirely.
Open Connectors in Le Chat, click + Add Connector, choose the Custom MCP Connector tab, paste https://mcpemails.com/api/mcp as the Server URL and click Connect. Sign in to MCPEmails, then turn the connector on in a chat from the + menu under Tools.
No. Le Chat runs the OAuth flow with dynamic client registration, so nothing secret is typed into the connector form. A bearer key is available for other clients that cannot do that.
Mistral says connectors are available to all Le Chat users. On Free, Pro and Student plans the account owner is the administrator who can add a Custom MCP Connector. On Team and Enterprise plans a workspace admin adds it for the organization.
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. Your agent 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, and Le Chat asks for approval before a connector acts unless you chose Always allow for that function. 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 connector, one sign-in. One inbox free forever, no card required.