Google Search Console, Bing and GA4 in Continue

Continue loads MCP servers from config.yaml or from block files in .continue/mcpServers, including remote servers over Streamable HTTP. GSC Magic connects with an access token sent as a request header.

Last updated: 2026-10-30

In short

Create an access token in the GSC Magic dashboard, add a streamable-http server for https://mcp.gscmagic.com/mcp with an Authorization: Bearer header under requestOptions in Continue's config, switch to agent mode, and Continue can query your Search Console, Bing and GA4 data.

Set up in 3 steps

  1. Create a GSC Magic account, connect Google, then create an access token under Connect → Access tokens.
  2. Save the snippet below as .continue/mcpServers/gsc-magic.yaml in your workspace, or add the mcpServers entry to your config.yaml.
  3. Switch Continue to Agent mode and ask it to list your Search Console properties.
.continue/mcpServers/gsc-magic.yaml 
name: GSC Magic
version: 0.0.1
schema: v1
mcpServers:
  - name: GSC Magic
    type: streamable-http
    url: https://mcp.gscmagic.com/mcp
    requestOptions:
      headers:
        Authorization: Bearer gsm_YOUR_TOKEN
Start free

Good to know

  • Do not commit a file that contains your token. Continue can read it from a secret instead: Authorization: Bearer ${{ secrets.GSC_MAGIC_TOKEN }}.
  • On Free your agent can only read. On Pro and Agency write tools are available, and the owner can switch write mode off in Settings in one click.

What to ask once connected

  • "List my Search Console properties and the one with the most clicks last 28 days."
  • "Which queries sit in positions 4–10 with the most impressions? Suggest title changes."
  • "Compare clicks this month with last month by page and tell me what moved."
  • "Which URLs in my sitemap are not indexed, and what does the inspection say?"
  • "How many sessions came from ChatGPT, Perplexity and Claude last month, and to which pages?"

More in 25 SEO prompts for AI agents; the full tool list is on the tools page.

Troubleshooting

The tools never show up in chat.

Continue only uses MCP tools in Agent mode. Switch modes and make sure the selected model supports tool use.

The server loads but calls fail with 401.

The header must sit under requestOptions → headers. Check the indentation, then replace the token if it expired or was revoked.

The block file is ignored.

A standalone file in .continue/mcpServers needs the name, version and schema lines at the top, as in the snippet.

Questions about Continue

Can I reuse a JSON config from Cursor or Claude Desktop?

Continue picks up JSON MCP files placed in .continue/mcpServers, but the YAML block above is the clearest way to set the transport and the header.

Other clients

Claude · ChatGPT · Claude Code · Cursor · Windsurf · VS Code · Any MCP client · Gemini CLI · Zed · Cline · n8n · LibreChat · goose · Warp · Raycast · OpenClaw · Hermes Agent · Grok