Connect your inbox to Raycast AI
from the command bar
Triage, search and send mail from the launcher you already reach for. Read, search, send, reply, forward, schedule and organize mail across every inbox you have connected.
Run the Install MCP Server command in Raycast, set Transport to HTTP, paste https://mcpemails.com/api/mcp, install it, then click Sign In to authorize with mcpemails.
How Raycast connects: OAuth, no API key
Raycast 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.
The one value you need
Everything on this page is a way of getting this URL into Raycast.
| 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 Raycast 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. Gmail connects with one-click Google sign-in; 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.
Run Install MCP Server
Run the Install MCP Server command, or Manage MCP Servers if you already have some.
Enter the server
Enter a name, set Transport to HTTP, and paste https://mcpemails.com/api/mcp.
Install and sign in
Press Install MCP Server, then click Sign In to authorize with mcpemails. Approve the scopes you want Raycast to hold.
Official Raycast documentation for remote MCP servers: https://manual.raycast.com/ai/model-context-protocol
Wondering which mailbox to connect first? See the provider compatibility matrix
What trips people up in Raycast
Sign In is a separate step from Install
Installing the server and authorizing it are two actions in Raycast, and the server is listed after the first one. A freshly installed but unauthorized server produces tool calls that fail with a 401, which reads like a broken server rather than an unfinished setup. Click Sign In.
A launcher is fast, which cuts both ways
The whole point of Raycast is that an action happens two keystrokes after the thought. That is excellent for search and triage, and it is why sending deserves a second look here more than in a slower client. Either leave send:email off this connection, or turn on human approval so a send waits for a person.
Nothing arrives on its own
The server is request and response only, with no webhooks and no push. Raycast sees mail when you ask it to look, which is the right shape for a launcher: you open it, you ask, you get an answer. It does mean this is not a notifier, and a standing "tell me when X arrives" is not something the connection can do.
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.
Raycast and email, answered
How do I connect email to Raycast?
Run the Install MCP Server command, set Transport to HTTP, paste https://mcpemails.com/api/mcp, install it, then click Sign In and authorize with mcpemails. Raycast AI then has tools for reading, searching, sending, replying, forwarding, organizing and scheduling mail.
Do I need an API key for Raycast?
No. Raycast runs the OAuth flow through its Sign In action, so nothing secret is typed into the command. A bearer key is available for other clients that cannot do that.
Which mailboxes can Raycast reach this way?
Gmail over Google sign-in, iCloud, Fastmail, Yahoo, Zoho and Yandex with an app-specific password, and any other mailbox that speaks IMAP and SMTP on the standard ports. The client sees them all through the same connection: your agent calls inbox_list first to discover every connected mailbox and its id, so there are no UUIDs to paste anywhere.
Can Raycast send email without me seeing it?
Only if you let it. Sending is gated on the send:email scope, so a key or 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.
Put your inbox in the command bar
One server, one sign-in. One inbox free forever, no card required.