All integrations

Integration · Cline

Connect Cline to Google Search Console

5 steps · about 5 minutes

By the GSC PAP team · Updated

Cline is an autonomous coding agent that runs inside VS Code and JetBrains, and also as a CLI. It speaks Model Context Protocol, so it can call GSC PAP and read your Search Console, GA4 and PageSpeed data while it works on the pages that data is about.

That combination is the useful part: the agent that edits a page can first ask which queries it ranks for, then check whether the change moved anything a week later.

This guide covers both the editor extension and the CLI. Either way GSC PAP is a remote server reached over a URL, so there is nothing to install and no Google Cloud project to create.

How to connect Google Search Console to Cline

  1. 1

    Sign in to GSC PAP and copy your token

    Go to gscpap.com, click "Sign in with Google" and approve the read-only access. Pick the sites you want to expose, then copy the bearer token the connect page shows once. You can mint more later at app.gscpap.com/account/tokens, scoped to a subset of your sites if you want a narrower one for a client project.

  2. 2

    Open Cline's MCP settings

    In VS Code or JetBrains, click the MCP Servers icon in the Cline sidebar, open the Configure tab and choose Configure MCP Servers, which opens the settings file. For the CLI the file lives in your home directory, and the CLINE_MCP_SETTINGS_PATH environment variable overrides the location if you keep it elsewhere.

    shell
    # Cline CLI settings file
    ~/.cline/data/settings/cline_mcp_settings.json
  3. 3

    Add the GSC PAP server

    Paste the block below and replace YOUR_TOKEN with the token from step 1. The type matters: set it to streamableHttp. If you leave the type out, Cline falls back to the legacy SSE transport and the connection will not come up.

    json
    {
      "mcpServers": {
        "gsc-pap": {
          "type": "streamableHttp",
          "url": "https://mcp.gscpap.com/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_TOKEN"
          },
          "disabled": false,
          "autoApprove": []
        }
      }
    }
  4. 4

    Or add it from the command line

    The CLI can write the same entry for you, which is handy on a second machine. Keep the token in an environment variable rather than in your shell history if you can.

    shell
    cline mcp add gsc-pap https://mcp.gscpap.com/mcp \
      --transport http \
      --header "Authorization: Bearer $GSC_PAP_TOKEN" \
      --yes
  5. 5

    Ask a Search Console question

    Open a Cline task and ask: "Use gsc-pap to list my sites, then show the top 10 queries by clicks for the last 28 days." Cline asks for approval before each tool call unless you have listed the tool in autoApprove. Read-only tools such as list_sites and search_analytics_query are reasonable candidates for that list; nothing in GSC PAP can change your property either way.

Cline MCP setup: common issues

  • ·Set "type": "streamableHttp". Omitting it selects the older SSE transport, and the server will appear in the list but never connect.
  • ·The Remote Servers tab in the extension asks for a name, URL and transport but has no field for a header, so a token-authenticated server has to go through the settings file or the CLI.
  • ·A 401 with "Missing or invalid bearer token" means the token is wrong or revoked, not that the transport is wrong. Mint a new one at app.gscpap.com/account/tokens.
  • ·If the server shows no tools after connecting, restart the Cline extension host; the tool list is fetched once at connect time.
  • ·Keep cline_mcp_settings.json out of any repo. It holds a live token.

Frequently asked questions

Does Cline support remote MCP servers?

Yes. A remote server is configured with a url instead of command and args, and it accepts a headers object for authentication. Set type to streamableHttp for a modern HTTP server; without it Cline uses the legacy SSE transport.

Where is Cline's MCP config file?

For the CLI it is cline_mcp_settings.json under ~/.cline/data/settings/, and CLINE_MCP_SETTINGS_PATH can point somewhere else. In the editor extensions you reach the same file through the MCP Servers icon, then the Configure tab, then Configure MCP Servers.

Is it safe to auto-approve Search Console tools in Cline?

GSC PAP only asks Google for read-only scopes, so no tool it exposes can change a property, submit a sitemap or remove a URL. Auto-approving its read tools saves a confirmation per call without giving the agent a way to break something. Approval is still worth keeping for servers that can write.

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

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

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.

5 steps · 5 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.