Connect ChatGPT to Google Search Console

How to connect Google Search Console to ChatGPT

1. 1

   Check that your workspace can add a custom MCP server

   In a Business workspace, only admins and owners can create and publish a connection, and Workspace settings then Members shows who those are. On Enterprise and Edu, admins can grant the permission to selected members through role-based access control. The permission is named "Create plugins with MCPs". If you are not an admin and you do not have that permission, this is a request to send rather than a setting to find.

2. 2

   Sign in to GSC PAP

   Go to gscpap.com and click "Sign in with Google." Approve the read-only access and choose which of your properties to authorize. For a connector you do not need to copy a token: GSC PAP implements OAuth 2.0 with Dynamic Client Registration, so ChatGPT registers itself and sends you through the consent screen instead.

3. 3

   Add the server from Plugins

   In the current experience you add a custom MCP server from Plugins directly, and you do not need to switch on Developer Mode first. Select the plus button, then "Add custom MCP server". Enter a name, such as GSC PAP, and optionally a description. Under Connection, paste the endpoint below. Then configure authentication as OAuth, review the risk warning, tick "I understand and want to continue", and select "Create as a plugin".

   textCopy

   https://mcp.gscpap.com/mcp

4. 4

   Authorize and let it scan the tools

   ChatGPT opens the GSC PAP consent screen. Approve it, and ChatGPT reads the tool list from the server. On the legacy Apps flow the same step is a "Scan Tools" button followed by Create, and the result shows up as a draft under Workspace settings then Apps then Drafts, labelled Dev. Either way, wait for the scan to finish before testing: a connection that looks live with an empty tool list is usually a scan that has not completed.

5. 5

   Test it, then publish it for the workspace

   Install the plugin, start a new conversation, type @ and pick it. Ask something narrow first, such as "list my Search Console sites", then move on to "show my top queries by clicks for the last 28 days". When it behaves, an admin or owner publishes it from Workspace settings then Apps then Drafts. On Enterprise and Edu, Configure Actions lets you choose which tools the workspace may use and Configure Access limits who sees it.

ChatGPT custom MCP servers: what to know first

• ·Custom MCP connections are a Business and Enterprise/Edu feature on ChatGPT web. On Free, Plus or Pro the option is not there, whatever a third-party blog post says.
• ·Only admins and owners can publish a connection to the whole workspace, even when a member was allowed to create and test it.
• ·ChatGPT needs a refresh token to keep a connection alive, and it looks for offline_access in the authorization server's discovery metadata. GSC PAP advertises it and issues refresh tokens. If a different MCP server loses access after a while, that is usually the reason.
• ·A local server started with npx or uvx cannot be used here. The endpoint has to be reachable over public HTTPS, which a hosted server already is.
• ·The risk warnings in this flow are about servers that can take write actions. Nothing GSC PAP exposes can change a property, submit a sitemap or remove a URL, because it only ever asks Google for read-only scopes.
• ·Treat the tool list as something to review. A custom connector is a tool an assistant will use on your company's data, and the review step exists for a reason.

Frequently asked questions