Connect LibreChat to Google Search Console

How to connect Google Search Console to LibreChat

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. Every person who will use the server does this for their own Google account, which is what keeps one install from mixing two people's properties.

2. 2

   Add the server to librechat.yaml

   Open your librechat.yaml and add an entry under mcpServers. Write the type out rather than letting LibreChat infer it. The key you choose becomes part of every tool name, so keep it short and do not rename it later: renaming changes each tool key and breaks agents that were saved against the old ones.

   yamlCopy

   mcpServers:
     gscpap:
       type: streamable-http
       url: https://mcp.gscpap.com/mcp
       title: Google Search Console
       description: Search Console, GA4 and PageSpeed, read-only.
       requiresOAuth: false
       headers:
         Authorization: "Bearer ${GSCPAP_TOKEN}"
       timeout: 120000
       initTimeout: 30000

3. 3

   Decide whose Search Console it reads

   The block above uses one token from your environment, which means everybody on the install reads the same person's properties. For a shared install you want the other shape: customUserVars asks each user for their own token through the UI and substitutes it into the header. Note the braces, because this is the easiest thing to get wrong here. ${VAR} with one brace and a dollar is an environment variable read on the server; {{VAR}} with two braces is the per-user value.

   yamlCopy

   mcpServers:
     gscpap:
       type: streamable-http
       url: https://mcp.gscpap.com/mcp
       requiresOAuth: false
       headers:
         Authorization: "Bearer {{GSCPAP_TOKEN}}"
       customUserVars:
         GSCPAP_TOKEN:
           title: GSC PAP token
           description: From app.gscpap.com, shown once when you connect.
           sensitive: true
       timeout: 120000

4. 4

   Give the slow tools room

   LibreChat's default request timeout is 30 seconds, and a few of these tools legitimately take longer because they are waiting on Google rather than on us. On our own traffic pagespeed_insights averages about 16 seconds and a bulk URL inspection costs roughly as long as the slowest page in the batch, which can be 50. Left at the default, the quick tools work and the slow ones fail, which reads like an unreliable server rather than a timeout. 120000 is comfortable.

5. 5

   Restart LibreChat and check the connection

   LibreChat reads librechat.yaml at startup, so the new server will not appear until you restart. Then open the tool picker: with the shared-token shape the server connects at startup and the tools are there. With customUserVars it will show as not connected until you fill the token in, because a per-user server has no app-level connection to make, and that is expected rather than a failure.

6. 6

   Ask the first question

   Attach the server to an agent or pick it in the chat tool menu, then ask something that names a property. The agent will call list_sites first if it does not know your properties yet.

   textCopy

   Using Search Console, compare the last 28 days with the previous 28 for example.com. Which five queries lost the most clicks, and what position did each move to?

LibreChat MCP: common issues

• ·Leave out type and LibreChat infers it from the URL, and an https URL means sse. GSC PAP has no SSE endpoint, so the connection fails for a reason the error will not name. Always write type: streamable-http.
• ·${GSCPAP_TOKEN} and {{GSCPAP_TOKEN}} are different things. One brace with a dollar is an environment variable resolved on the server; two braces is a per-user value from customUserVars. Use the wrong one and LibreChat sends the literal text as your token, which comes back 401.
• ·requiresOAuth is auto-detected at startup, and our endpoint does advertise OAuth. With a static Authorization header set requiresOAuth: false, or LibreChat may start an OAuth flow instead of using the header you configured.
• ·The default timeout is 30000 ms and initTimeout is 10000. Both are low for this server: the first is shorter than some Google calls take, and the second is tight for a cold start.
• ·LibreChat's reference documents an oauth block whose required keys include client_id and client_secret, while the same page says Dynamic Client Registration is used when no client id and secret are given. We have not taken that path to a verified state, so the configurations here use a token. GSC PAP does implement DCR, which is how the Claude.ai connector works.
• ·serverInstructions: true asks the server for usage guidance to inject into the agent's context. GSC PAP does not send instructions in the handshake today, so the option adds nothing. Leave it out rather than wondering why it changed nothing.
• ·Keep the /mcp path on the URL. https://mcp.gscpap.com without it is not an MCP endpoint, and a GET to the endpoint answers 405 by design, which is correct behaviour rather than a fault.
• ·Rate limits are per user, 60 tool calls a minute and 1,000 an hour. On a shared install with one shared token, everybody draws on the same allowance; with per-user tokens each person gets their own.

Frequently asked questions