Connect Kiro to Google Search Console

How to connect Google Search Console to Kiro

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 properties you want to expose, then copy the bearer token shown once on the connect page. You can create more, scoped to fewer sites, at app.gscpap.com/account/tokens.

2. 2

   Put the token in your environment

   Keeping it out of mcp.json matters here, because the workspace file is the one that tends to end up in a repository.

   shellCopy

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

3. 3

   Open the right mcp.json

   A workspace config lives at .kiro/settings/mcp.json and a user-level one at ~/.kiro/settings/mcp.json. If both exist Kiro merges them, and the workspace file takes precedence. For a token that should follow you across projects, use the user-level file.

   shellCopy

   # workspace
   .kiro/settings/mcp.json
   
   # user, all workspaces
   ~/.kiro/settings/mcp.json

4. 4

   Add the GSC PAP server

   Paste the entry below. Saving the file reconnects the server, so there is nothing to restart.

   jsonCopy

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

5. 5

   Approve the variable, then ask

   If Kiro warns about the variable instead of expanding it, add GSC_PAP_TOKEN to the "Mcp Approved Env Vars" setting. Then ask: "List my Search Console sites, then show me the queries ranking between 5 and 20 with a CTR under 2%."

Kiro MCP setup: common issues

• ·Kiro expands only environment variables you have approved. An unexpanded ${GSC_PAP_TOKEN} reaching the server looks exactly like a bad token, so check "Mcp Approved Env Vars" first.
• ·The url has to be HTTPS. Plain HTTP is only allowed for localhost, which does not apply to a hosted server.
• ·Workspace settings win over user settings when both define gsc-pap. If a change to the user file does nothing, look for .kiro/settings/mcp.json in the project.
• ·Saving mcp.json reconnects the server by itself. If a tool list looks stale, save the file again rather than restarting the IDE.
• ·Keep the token in the environment, not in a workspace mcp.json that a repository will carry.

Frequently asked questions