Integration · Raycast
Connect Raycast to Google Search Console
5 steps · about 4 minutes
By the GSC PAP team · Updated
Raycast is a launcher with an AI that can call Model Context Protocol tools, which makes it the shortest path between a keystroke and an answer about your traffic. No editor, no terminal: hit the hotkey and ask what your top queries were this week.
Two things make this one worth setting up. Raycast supports OAuth Dynamic Client Registration, and GSC PAP implements it, so there is no token to copy or store. And HTTP is the only MCP transport on Raycast for iOS, which means a hosted server is the kind that works on your phone.
Everything here is in Raycast's own UI. There is no config file to edit.
How to connect Google Search Console to Raycast
- 1
Sign in to GSC PAP once
Go to gscpap.com, click "Sign in with Google" and approve the read-only access, then choose which properties to authorize. Nothing needs copying: the authorization for Raycast happens inside Raycast in step 4.
- 2
Open the install flow
Search for the Install MCP Server command, or open Manage MCP Servers and choose Install New Server. The MCP Servers tab in Settings lists suggested servers only, so a custom one goes through the install command.
- 3
Fill in the server
Give it a name such as GSC PAP and an icon. Set the transport to HTTP, not Standard Input/Output, since there is no local process. Put the endpoint in the URL field. For OAuth Type choose Dynamic, which lets Raycast register itself as a client. Then press Install MCP Server.
texthttps://mcp.gscpap.com/mcp - 4
Sign in to finish
An HTTP server with OAuth shows a Sign In prompt after installing, and no tools are available until you use it. Signing in sends you through the GSC PAP consent screen. Once it completes, the tools appear.
- 5
Ask from the launcher
Open Raycast AI and ask: "List my Search Console sites, then show the top queries by clicks for the last 28 days." This is where Raycast earns its place next to an editor: a weekly check becomes a hotkey rather than a tab.
Raycast MCP setup: common issues
- ·Pick HTTP as the transport. Standard Input/Output is for local processes and cannot reach a hosted server.
- ·Dynamic is the right OAuth Type here. Static is for servers that need you to bring your own Client ID, Secret, Scopes and callback registration, which GSC PAP does not.
- ·No tools appear until you complete the Sign In prompt. An empty tool list right after install usually means that step is still waiting.
- ·If you would rather use a bearer token than OAuth, the HTTP Headers fields take key and value pairs that are sent with every request, so Authorization and Bearer YOUR_TOKEN work there.
- ·On iOS, HTTP is the only transport available, so a hosted server is the only kind that works. This is a point in favour of a remote server rather than a local one.
Frequently asked questions
Can Raycast connect to a remote MCP server?
Yes. Choose the HTTP transport when installing a server, enter the MCP endpoint in the URL field, and optionally add HTTP headers that are sent with every request. OAuth is supported in both Dynamic and Static forms.
Do I need a token to add an MCP server to Raycast?
Not for a server that supports OAuth Dynamic Client Registration, which GSC PAP does. Choose Dynamic as the OAuth Type and Raycast registers itself, then prompts you to sign in. The header fields are there if you prefer a bearer token.
Does this work in Raycast for iOS?
Yes, and it is the transport that does: HTTP is the only MCP transport on iOS. A hosted Search Console server therefore works on the phone, where a local stdio server cannot.
Other integrations
All integrationsClaude Desktop
Connect Claude Desktop to Google Search Console without creating a Google Cloud project. Sign in with Google, paste one config block, restart Claude.
Cursor
Connect Google Search Console to Cursor through a hosted MCP server. Sign in with Google, paste one token into mcp.json, and skip the Google Cloud project.
Claude Code
Add Google Search Console to Claude Code with one claude mcp add command. Hosted and read-only: no Google Cloud project, no OAuth credentials, no Python.
Codex CLI (OpenAI)
Add Google Search Console, GA4 and PageSpeed data to OpenAI's Codex CLI with one TOML block and a bearer token. You never create a Google Cloud project.
VS Code (GitHub Copilot)
Connect Google Search Console to GitHub Copilot in VS Code with one .vscode/mcp.json entry, then ask agent mode about GSC. You skip Google Cloud setup.
Gemini CLI (Google)
Query Google Search Console (GSC) from your terminal with Gemini CLI. Register GSC PAP as an MCP server in settings.json, with no Google Cloud project.
Windsurf (Devin Desktop)
Give Windsurf, now Devin Desktop, your Google Search Console data. Add GSC PAP as a remote MCP server with one bearer token and no Google Cloud project.
Zed Editor
Bring Google Search Console into Zed's AI assistant as an MCP context server. You add one settings.json block and a token, with no Google Cloud setup.
JetBrains IDEs
Connect Google Search Console to IntelliJ, PyCharm, WebStorm and other JetBrains IDEs via AI Assistant's MCP settings, without a Google Cloud project.
Continue (extension)
Continue MCP setup for Google Search Console: add one mcpServers entry with a bearer token in VS Code or JetBrains. You do not need a Google Cloud project.
Claude.ai (browser)
Add Google Search Console to Claude.ai as a custom connector. Paste one URL and approve access. No token to copy, no config file, no Google Cloud project.
Direct HTTP (curl, custom agents)
Call the GSC PAP MCP server from curl or your own agent. It is JSON-RPC over HTTP with a bearer token, so you need no MCP client or Google Cloud project.
opencode
Add Google Search Console to opencode as a remote MCP server. One config block with your token, no Google Cloud project, no local server to run.
Cline
Add Google Search Console to Cline in VS Code or the Cline CLI as a remote MCP server. One token, no Google Cloud project, read-only access.
Warp
Add Google Search Console to Warp's agent as a remote MCP server. Paste one JSON block with your token, press Start, and ask about your traffic in the terminal.
LM Studio
Give a local model your Search Console data. Add GSC PAP to LM Studio's mcp.json as a remote server, with one token and no Google Cloud project.
ChatGPT
Add Google Search Console to ChatGPT as a custom MCP server. What the setup looks like, and the plan requirement that decides whether you can do it at all.
Goose
Add Google Search Console to Goose as a streamable_http extension. One block in config.yaml with your token, no Google Cloud project, read-only access.
Google Antigravity
Add Search Console to Google Antigravity as a custom MCP server. It handles dynamic client registration, so the setup is a URL and a sign-in, with no token.
Roo Code
Add Google Search Console to Roo Code in VS Code as a streamable-http MCP server. One block with your token, no Google Cloud project, read-only.
Kilo Code
Add Google Search Console to Kilo Code as a remote MCP server. It can negotiate OAuth for you, or take a bearer token. No Google Cloud project either way.
Amp
Add Google Search Console to Amp as a remote MCP server, in settings or with one CLI command. No Google Cloud project, read-only scopes.
Kiro
Add Google Search Console to Kiro as a remote MCP server. One entry in mcp.json, the token read from an approved environment variable, read-only access.
GitHub Copilot CLI
Add Google Search Console to GitHub Copilot CLI with one command or one JSON entry. Remote HTTP transport, your token in a header, read-only access.
n8n
Give an n8n AI Agent your Search Console data through the MCP Client Tool node, and schedule the SEO report you keep meaning to write.
LibreChat
Add GSC PAP to librechat.yaml as a streamable-http MCP server, and give every user on your install their own Search Console access rather than a shared one.