Model Context Protocol
Model Context Protocol (MCP) is how you plug external tools and data sources into Raycast AI. Once a server is connected, its tools become available to AI Chat, Quick AI, and AI Commands alongside everything Raycast already knows about you and your installed extensions.
MCP works in both directions: you can connect MCP servers to Raycast, and on Mac and Windows you can also let other AI apps on your computer use Raycast as an MCP server.
Install MCP Servers
To add a new MCP server, search for the Install MCP Server command or use the Install New Server action in the Manage MCP Servers command then fill out the form. Give the server a name & icon, select the transport & connection details, optionally a description.
Press Install MCP Server (⌘↵ / Ctrl↵) and Raycast saves the config, starts the connection, and pulls in the tool list automatically. Stdio servers run as soon as they're installed; HTTP servers with OAuth will prompt you to Sign In before any tools become available.
If a stdio command relies on something on your PATH, restart Raycast after updating your environment variables so the new values are picked up.
Configuration Fields
- Name & Icon: How the server appears in lists, mentions, and the Action Panel.
- Transport: Standard Input/Output or HTTP. iOS is always HTTP.
- Command (stdio): The executable to run, e.g.
npxor a path to a binary. - Arguments (stdio): Passed to the command. Accepts a space‑separated string or a JSON array.
- Environment (stdio): Key/value pairs injected into the server's environment, e.g. API tokens.
- URL (HTTP): The server's MCP endpoint.
- HTTP Headers (HTTP): Key/value pairs sent on every request.
- OAuth Type (HTTP): Dynamic if the server supports OAuth Dynamic Client Registration, Static if you need to provide your own credentials.
- Client ID / Client Secret / Scopes (HTTP, Static OAuth only): Pre‑registered OAuth credentials and the scopes to request.
- Callback Type / Callback URL (HTTP, Static OAuth only): Choose whether the provider redirects to an HTTPS callback or straight to the Raycast App. Use Copy Callback URL and register that exact URL in your provider's OAuth app settings before signing in. Changing the callback type on an existing server means signing in again.
- Custom Instructions: Optional guidance for how Raycast AI should use the server (see Using MCP Servers).
- Description: Optional shown in the details pane.
Transports
Raycast supports two ways of talking to an MCP server:
- Standard Input/Output: A local process that Raycast launches and pipes JSON‑RPC over stdin/stdout. Good for anything you'd run from the terminal:
npx, a Python script, a compiled binary. - HTTP: A remote endpoint that speaks MCP over HTTP (including the Streamable HTTP variant). Good for hosted services, and the only transport available on iOS.
Authentication
For HTTP servers that require OAuth, Raycast handles the full flow. Dynamic OAuth uses Dynamic Client Registration with PKCE: select Sign In and Raycast registers itself as a client. Static OAuth uses a Client ID (and optional Secret) you provide, which services like Slack require. Tokens are stored encrypted, per server.
On Desktop, the Logout Server action in the Manage MCP Servers command clears saved tokens for an HTTP server without removing it.
Bundled with Extensions
Some Store extensions include their own MCP server rather than asking you to fill out the Install MCP Server form yourself. Installing one of these extensions installs and connects its server automatically, and it then shows up in Manage MCP Servers alongside any servers you added manually.
Popular MCP Servers
The MCP Servers tab in Settings suggests popular servers you can connect to, including GitHub, Linear, PostHog, and Shape. Tap Connect to start the OAuth flow, or Set Up for servers that need an access token, and Raycast prefills the form for you. Once connected, the popular MCP server will move to the connected servers list.
Manage MCP Servers
Search Manage MCP Servers in Raycast to see every installed server with its status, tool list, and details in one place. Each server is either Running (connected and serving tools), Stopped (installed but not connected), or in an Error state. The details pane shows the full output from the server or transport.
From this command, you can start a new chat with the selected server or open the Action Panel for more options: Add Server, Refresh, Start, Stop, Restart, Logout, and Uninstall.
Using MCP Servers
Every server gets a @-mention name, just like AI Extensions. In AI Chat or Quick AI, type @ and enter the server's name to scope a question to it — type @linear what's assigned to me? to ask the Linear MCP server directly.
Raycast also adds an Ask command for each installed server to Root Search (e.g. Ask Linear), prefilling Quick AI with that mention.
Custom Instructions
Each server has an optional Custom Instructions field. Use it to steer how Raycast AI works with that server, for example "default my Linear queries to the Platform team." The AI reads these instructions whenever it considers using the server's tools.
Permissions
MCP tools follow the same Permissions setting as AI Extensions. By default, Raycast approves read-only tools on its own and asks you about the rest. Learn more under Permissions on the AI Extensions page.
Raycast MCP Server
Raycast can also act as an MCP server itself. This lets AI apps on your computer, like Claude Code or ChatGPT, use Raycast's built-in AI Extensions, so you can work with your Notes, snippets, settings, and more from the app you're already using.
The Raycast MCP Server is available with Raycast Pro. Try Pro for free for 7 days.
Connect an App
- Open Settings → MCP → Raycast MCP Server.
- Turn on the Raycast MCP Server switch.
- Open the Connect App menu and choose Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, GitHub Copilot, or VS Code.
To connect any other app, choose Other App… from the Connect App menu to open the Connect Another App dialog, select Copy Configuration, and paste the configuration into that app's MCP settings. The configuration includes a token unique to that app.
The Raycast MCP Server is off by default on each device. It only listens on your own computer, at http://127.0.0.1:8267/mcp, so only apps on that computer can reach it. Each connected app gets its own token.
Shared Extensions
Shared Extensions controls which Raycast AI Extensions connected apps can use:
- Available Extensions: Applications (Mac only), Automations, Browser, Calculator, Calendar, Clipboard, Contacts, Dictation, Extension Development, File Search, Focus, Manual, Memory, Notes, Organizations, Quicklinks, Send Feedback, Settings, Snippets, Store, and Weather.
- Automations: Off by default. Turn it on to share it with connected apps.
- Resources: Shared Snippets, Quicklinks, and Notes are also offered to connected apps as MCP resources.
Extensions that are disabled in Raycast, restricted by your organization, or not available on your platform aren't available to connected apps.
Connected Apps
Connected Apps lists every app you've connected. Each app's token can be revoked on its own, without affecting other connected apps. Built-in apps you've already connected don't appear in the Connect App menu.
Raycast doesn't ask for confirmation when a connected app calls a tool. Instead, it passes tool annotations to the connected app and relies on that app's own approval prompts. Check the tool-approval settings in each app you connect.