Connect Goose to Google Search Console

How to connect Google Search Console to Goose

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

2. 2

   Open Goose's config file

   Goose keeps its settings in YAML. config.yaml holds the provider, the model and the extensions.

   shellCopy

   # macOS, Linux
   ~/.config/goose/config.yaml
   
   # Windows
   %APPDATA%\Block\goose\config\config.yaml

3. 3

   Add GSC PAP as a streamable_http extension

   Add the block below under the existing extensions key, next to developer and the other built-ins, and replace YOUR_TOKEN with your token. Note the field names: the URL goes in uri, not url, and the type must be streamable_http.

   yamlCopy

   extensions:
     gsc-pap:
       type: streamable_http
       name: gsc-pap
       enabled: true
       uri: "https://mcp.gscpap.com/mcp"
       headers:
         Authorization: "Bearer YOUR_TOKEN"
       env_keys: []
       envs: {}
       timeout: 300

4. 4

   Optional: load only the tools you need

   GSC PAP exposes 36 tools, and every tool description costs context in each session. Goose can filter the list per extension with available_tools: name the ones you want and only those load. Leave it out or empty to load all of them. A reporting setup rarely needs more than a handful.

   yamlCopy

       available_tools:
         - list_sites
         - search_analytics_query
         - compare_periods
         - find_quick_wins
         - find_content_decay

5. 5

   Start a session and ask

   Open a Goose session and ask: "Using gsc-pap, list my Search Console sites, then show the top 10 queries by clicks for the last 28 days." The first call is list_sites, because every other tool needs the exact property URL that returns.

Goose extension setup: common issues

• ·The key is uri, not url. A remote extension with url is silently incomplete and will not connect.
• ·SSE is not supported. If you are migrating an older extension that used it, change the type to streamable_http.
• ·Keep the token out of a config file you sync or share. Goose has env_keys and envs on the extension for exactly that, and secrets.yaml for file-based secret storage.
• ·"Missing or invalid bearer token" is a token problem. Mint a new one at app.gscpap.com/account/tokens; your other tokens keep working.
• ·Goose runs autonomously by default. That is worth knowing in general, though nothing GSC PAP exposes can change your Search Console property: its Google scopes are read-only.

Frequently asked questions