Connect Zed to Google Search Console

How to add Google Search Console to Zed

1. 1

   Sign in to GSC PAP and copy your token

   Go to gscpap.com and click "Sign in with Google." Approve the read-only access it asks for. The connect page then shows your bearer token once, so copy it now. If you lose it, create a new one at app.gscpap.com/account/tokens; your other tokens keep working.

2. 2

   Add gsc-pap as a remote MCP server

   Open Settings > AI > MCP Servers, click Add Server, and choose Add Remote Server. Zed writes what you enter to your settings file. To edit that file directly, run zed: open settings file from the command palette and add the entry below under context_servers, with your token in place of YOUR_TOKEN. If context_servers already exists, add only the gsc-pap entry.

   jsonCopy

   {
     "context_servers": {
       "gsc-pap": {
         "url": "https://mcp.gscpap.com/mcp",
         "headers": {
           "Authorization": "Bearer YOUR_TOKEN"
         }
       }
     }
   }

3. 3

   Check the status and ask a question

   Go back to Settings > AI > MCP Servers. The dot next to gsc-pap turns green, with the tooltip "Server is active", once Zed connects. Then open the Agent Panel and ask: "Use gsc-pap to list my Search Console sites." Naming the server helps the model pick its tools. By default, Zed asks for approval before it runs a tool.

Zed context server troubleshooting

• ·Put url and headers directly on the gsc-pap entry, as shown above. Zed's docs do not use a nested transport object for remote servers.
• ·Keep the Authorization header. When a remote server has no Authorization header, Zed starts the MCP OAuth sign-in flow instead of sending a token.
• ·If the dot is not green, hover over it to read the status, then run zed: open log from the command palette and look for lines that mention gsc-pap.
• ·A "Missing or invalid bearer token" error means the token is wrong or was revoked. Create a new one at app.gscpap.com/account/tokens.

Frequently asked questions