Connect Amp to Google Search Console

How to connect Google Search Console to Amp

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

2. 2

   Put the token in your environment

   Amp expands ${VAR_NAME} inside header values, so the token does not have to live in a settings file you might sync or commit.

   shellCopy

   echo 'export GSC_PAP_TOKEN="paste-your-token-here"' >> ~/.zshrc
   source ~/.zshrc

3. 3

   Add the server to Amp's settings

   User settings live in ~/.config/amp/settings.json and workspace settings in .amp/settings.json. The key is amp.mcpServers, written with the dotted prefix inside the JSON object.

   jsonCopy

   {
     "amp.mcpServers": {
       "gsc-pap": {
         "url": "https://mcp.gscpap.com/mcp",
         "headers": {
           "Authorization": "Bearer ${GSC_PAP_TOKEN}"
         }
       }
     }
   }

4. 4

   Or add it from the CLI

   The CLI writes the entry for you. It has no flag for a header, so add the headers block to settings afterwards, or use the remote form in the gotchas below, which keeps the bearer token in a file of its own.

   shellCopy

   amp mcp add gsc-pap https://mcp.gscpap.com/mcp

5. 5

   Approve it if it came from the workspace, then ask

   A server defined in .amp/settings.json needs approval before it runs: amp mcp approve gsc-pap. Then ask Amp "list my Search Console sites, then show the top 10 queries by clicks for the last 28 days". The first call is list_sites, since every other tool needs the exact property URL.

   shellCopy

   amp mcp approve gsc-pap

Amp MCP setup: common issues

• ·The settings key is amp.mcpServers, with the prefix as part of the key name. A bare mcpServers object will not be read.
• ·Workspace servers are not trusted automatically. Until amp mcp approve runs, the server is configured and inert.
• ·The CLI cannot attach a header. For a token-authenticated server, either edit settings after amp mcp add, or use the remote definition form: amp mcp remote add GscPap https://mcp.gscpap.com/mcp --auth bearer --bearer-token-file /path/to/token --personal
• ·A url entry is treated as local configuration even when the server is on another machine, which is only a naming quirk, not a limitation.
• ·"Missing or invalid bearer token" usually means the environment variable was empty when Amp started. Check it in the shell you launch Amp from.

Frequently asked questions