Connect GitHub Copilot CLI to Google Search Console

How to connect Google Search Console to Copilot CLI

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. Choose which properties to authorize, then copy the bearer token the connect page shows once. Additional tokens, each scoped to a subset of your sites, are at app.gscpap.com/account/tokens.

2. 2

   Add it with one command

   The default transport is stdio, so --transport http is required for a remote server. --header can be repeated if a server needs more than one.

   shellCopy

   copilot mcp add --transport http \
     --header "Authorization: Bearer YOUR_TOKEN" \
     gsc-pap https://mcp.gscpap.com/mcp

3. 3

   Or write the entry yourself

   User-level servers live in ~/.copilot/mcp-config.json. A project can define its own in .mcp.json or .github/mcp.json. Set type to http, which is the Streamable HTTP transport; sse is the legacy one and is deprecated.

   jsonCopy

   {
     "mcpServers": {
       "gsc-pap": {
         "type": "http",
         "url": "https://mcp.gscpap.com/mcp",
         "headers": {
           "Authorization": "Bearer YOUR_TOKEN"
         },
         "tools": ["*"]
       }
     }
   }

4. 4

   Decide which tools to expose

   tools accepts * for everything, or a comma-separated list of names. GSC PAP has 36 tools, and a terminal session rarely needs all of them, so naming five keeps the model's context lean.

   jsonCopy

         "tools": [
           "list_sites",
           "search_analytics_query",
           "compare_periods",
           "find_quick_wins",
           "batch_inspect_urls"
         ]

5. 5

   Ask a Search Console question

   Start Copilot CLI and ask: "List my Search Console sites, then show the top 10 queries by clicks for the last 28 days." If you deploy from this terminal, the natural follow-up is whether the URLs you shipped are indexed, which batch_inspect_urls answers for up to 2,000 at a time.

Copilot CLI MCP setup: common issues

• ·--transport http is not optional. The default is stdio, and a remote server added without it will not connect.
• ·This is a different config from Copilot in VS Code. Connecting one does not connect the other.
• ·When a project file and the user file both define gsc-pap, the higher-priority source wins. For a one-off session, --additional-mcp-config adds servers without touching either.
• ·Keep the token out of .mcp.json and .github/mcp.json if the repository is shared. The user-level ~/.copilot/mcp-config.json is the safer home for it.
• ·"Missing or invalid bearer token" means the token is wrong or was revoked, not that the transport is wrong. Mint a new one at app.gscpap.com/account/tokens.

Frequently asked questions