Connect your inbox to Perplexity
as a custom connector
Ask Perplexity about your own mail next to the web. Read, search, send, reply, forward, schedule and organize mail across every inbox you have connected.
On a Perplexity Pro, Max or Enterprise plan, open Plugins, select Add custom, then Connector and Add MCP connector. Choose Remote, paste https://mcpemails.com/api/mcp as the MCP Server URL, pick OAuth for Authentication, click Add, then click the connector card to sign in to MCPEmails.
How Perplexity connects: OAuth, no API key
Perplexity's custom remote connectors support OAuth 2.0 with discovery, and MCPEmails publishes its endpoints at /.well-known/oauth-authorization-server. Perplexity registers itself with RFC 7591 dynamic client registration, so there is no Client ID or Client Secret to create, and authorizes with authorization code plus PKCE using S256. The token carries only the scopes you approve on our consent screen. The access token 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.
The one value you need
Everything on this page is a way of getting this URL into Perplexity.
| 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. |
How to connect Perplexity to your inbox
Four steps. The first two are the same for every client, the rest are specific to this one.
Create a free account and connect a mailbox
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.
Open Add custom in Perplexity
On perplexity.ai, open Plugins in the sidebar and select Add custom, then Connector, then Add MCP connector. If you still see the older menu, go to Customize, Connectors instead.
Enter the server
Select Remote, enter a Name such as MCPEmails, and paste https://mcpemails.com/api/mcp as the MCP Server URL. Set Authentication to OAuth and Transport to Streamable HTTP. Perplexity discovers our OAuth endpoints and registers itself, so there is no Client ID or Client Secret to fill in.
Add it and sign in
Check the acknowledgement box and click Add. Then click the connector card to start authentication, sign in to MCPEmails and approve the scopes you want Perplexity to hold.
Pick it for your question
Start a new query and type @MCPEmails, or click the + icon in the search box, open Connectors and sources and select MCPEmails. Then ask about your mail, for example which messages came in today.
Official Perplexity documentation for remote MCP servers: https://www.perplexity.ai/help-center/en/articles/13915507-adding-custom-remote-connectors
Wondering which mailbox to connect first? See the provider compatibility matrix
What trips people up in Perplexity
Free accounts do not get custom connectors
Perplexity offers custom MCP servers on Pro, Max and Enterprise plans. On Enterprise, members can only add their own custom connectors once an admin turns on Allow members to add custom connectors, which is off by default. An admin can also add MCPEmails once for the whole organization.
Adding the connector is not the same as using it
Some surfaces only call a connector you select for that chat, with the connector picker or an @ mention. If Sources or Focus is set to Web, Academic or Social only, Perplexity does not call connected apps, answers from the web and looks as if it cannot see your inbox. Check both before suspecting the connection.
Set it up on the web, not on mobile
Perplexity notes that a connector can be available on the web but not yet on mobile. Add MCPEmails at perplexity.ai in a browser. If authorization never finishes, allow pop-ups and cross-site cookies for perplexity.ai, since an ad blocker can stop the OAuth window.
Limits worth knowing
- Requests are rate limited to 100 per minute, 1,000 per hour and 10,000 per day per key, plus your plan ceiling on billable actions.
- The server is request and response only. There are no webhooks and no server-initiated events, so new mail never wakes your agent by itself. To react to arriving mail, poll on a schedule.
- Mail is fetched live from your provider on every call and never stored. Only the encrypted OAuth token or app password is kept, so a revoked token or a changed mailbox password ends access immediately.
Perplexity and email, answered
How do I connect email to Perplexity?
Open Plugins, select Add custom, then Connector and Add MCP connector. Choose Remote, paste https://mcpemails.com/api/mcp as the MCP Server URL, set Authentication to OAuth, click Add, then click the connector card and sign in to MCPEmails. In a query, type @MCPEmails or select it under Connectors and sources.
Which Perplexity plan do I need?
Custom MCP connectors are available on Pro, Max and Enterprise. On Enterprise, an admin either adds the connector for the organization or allows members to add their own.
Do I need an API key for Perplexity?
No. Perplexity runs the OAuth flow when you click the connector card, and MCPEmails supports dynamic client registration, so there is no Client ID, Client Secret or key to paste. A bearer key is available for other clients that cannot do OAuth.
Which mailboxes can Perplexity reach this way?
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. Perplexity 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.
Can Perplexity send email without me seeing it?
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.
Is my email stored on your servers?
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.
Search your inbox like you search the web
One connector, one sign-in. One inbox free forever, no card required.