All integrations

Integration · LM Studio

Connect LM Studio to Google Search Console

5 steps · about 5 minutes

By the GSC PAP team · Updated

LM Studio runs language models on your own machine, and since version 0.3.17 it can also act as an MCP client for both local and remote servers. Adding GSC PAP means a model running on your laptop can read your Search Console, GA4 and PageSpeed data.

The appeal is that the model stays local while the data stays yours: GSC PAP reads Google's APIs on your behalf with read-only scopes, and the analysis happens on hardware you own.

The honest caveat is in the model, not the connection. Tool calling across a server with this many tools asks a lot of a small local model, so this works much better on a model with solid tool-use support. See the issues below before you judge the setup.

How to connect Google Search Console to LM Studio

  1. 1

    Check your LM Studio version

    Remote MCP servers arrived in 0.3.17. On an older build the config file exists but a URL-based server will not connect, so update first if you are behind.

  2. 2

    Sign in to GSC PAP and copy your token

    Go to gscpap.com, click "Sign in with Google" and approve the read-only access. Choose which sites to grant, then copy the bearer token from the connect page. It is shown once, and you can mint more at app.gscpap.com/account/tokens.

  3. 3

    Open mcp.json

    In LM Studio, open the Program tab in the right-hand sidebar, then Install, then Edit mcp.json. The file opens in LM Studio's own editor, so you do not have to hunt for it on disk.

  4. 4

    Add the GSC PAP server

    Paste the entry below and replace YOUR_TOKEN with your token. If mcp.json already has servers in it, copy only the gsc-pap entry into the existing mcpServers object rather than pasting a second wrapper.

    json
    {
      "mcpServers": {
        "gsc-pap": {
          "url": "https://mcp.gscpap.com/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_TOKEN"
          }
        }
      }
    }
  5. 5

    Load a tool-capable model and ask

    Load a model that supports tool use, start a chat, and ask something narrow to begin with: "Call list_sites and show me the result." Narrow beats open-ended here, because naming the tool removes the hardest part of the job for a local model. Once that works, move up to "show my top 10 queries by clicks for the last 28 days".

LM Studio MCP setup: common issues

  • ·Remote servers need LM Studio 0.3.17 or newer. Older builds only start local MCP servers.
  • ·The model has to support tool calling, and small quantized models are often unreliable at choosing between many tools. If the model answers in prose instead of calling a tool, name the tool in your prompt.
  • ·A long tool list costs context. On a model with a small context window, ask one question at a time rather than requesting a full report.
  • ·"Missing or invalid bearer token" is a token problem, not a model problem. Replace it from app.gscpap.com/account/tokens.
  • ·mcp.json holds a live token, so do not copy it into a shared repo or a gist when you ask for help.

Frequently asked questions

Can LM Studio connect to a remote MCP server?

Yes, since version 0.3.17 LM Studio supports both local and remote MCP servers. A remote one is configured in mcp.json with a url, and custom headers such as Authorization are supported, which is what a hosted server like GSC PAP needs.

Where is LM Studio's mcp.json?

You open it from inside the app: the Program tab in the right-hand sidebar, then Install, then Edit mcp.json. It opens in LM Studio's built-in editor.

Does my Search Console data go to a local model only?

The model runs on your machine, so the conversation does. The data itself comes from Google through GSC PAP, which reads your Search Console and Analytics with read-only scopes and does not sell, share or train on it. So the path is Google to GSC PAP to your machine.

Which local model should I use for this?

One with real tool-use support and enough context for a tool list. Reliability at choosing the right tool among many is where small models struggle, so if your model hesitates, name the tool in the prompt and keep each question to one thing.

Other integrations

All integrations

Claude Desktop

Connect Claude Desktop to Google Search Console without creating a Google Cloud project. Sign in with Google, paste one config block, restart Claude.

6 steps · 6 min read

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.

5 steps · 5 min read

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.

3 steps · 3 min read

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.

4 steps · 4 min read

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.

4 steps · 4 min read

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.

5 steps · 5 min read

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.

4 steps · 5 min read

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.

3 steps · 4 min read

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.

5 steps · 5 min read

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.

4 steps · 4 min read

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.

3 steps · 3 min read

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.

4 steps · 5 min read

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.

5 steps · 5 min read

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.

5 steps · 5 min read

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.

5 steps · 4 min read

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.

5 steps · 6 min read

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.

5 steps · 5 min read

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.

5 steps · 5 min read

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.

5 steps · 5 min read

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.

5 steps · 5 min read

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.

5 steps · 5 min read

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.

5 steps · 5 min read

Raycast

Add Google Search Console to Raycast AI as an HTTP MCP server. Dynamic OAuth means no token to paste, and HTTP servers work on Raycast for iOS too.

5 steps · 4 min read

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.

5 steps · 5 min read

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.

6 steps · 6 min read

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.

6 steps · 6 min read

Done. Your AI client now has access to your Search Console data.

Got stuck? Email support@gscpap.com with the error and we will revise the guide.