What you need
- A Google account with access to your website in Search Console.
- A HyperGSC account.
- OpenClaw installed with an agent runtime that supports outbound MCP tools, and terminal access to the Gateway you use.
1. Connect your website in HyperGSC
- Sign in to HyperGSC and open Settings.
- Connect the Google account that has access to your website in Search Console.
- Your first 250 discovered properties connect automatically across your Google accounts. Disable individual sites under Sites if you do not want to share them.
Search Console calls each website a property. Signing in to HyperGSC with Google is separate from connecting Search Console, so complete this step even if you already signed in with Google.
2. Add HyperGSC to OpenClaw
On the machine where your OpenClaw Gateway runs, stop the Gateway before running the commands below. Keep it stopped through sign-in and the connection probe; these CLI operations require exclusive access to local state.
bash
openclaw mcp add hypergsc --url https://hypergsc.com/mcp --transport streamable-http --auth oauth
openclaw mcp login hypergscOpen the authorization link, sign in to HyperGSC and approve access. Return to the terminal after the callback completes. This connects an external server to OpenClaw; it does not require running an MCP server yourself.
bash
openclaw mcp doctor hypergsc --probeThe probe should connect and list the server’s capabilities. A saved entry alone does not prove tool access works. Once the probe finishes, start the Gateway again, then start a new agent turn and run the connection check below.
3. Check the connection
Send this in OpenClaw:
Use HyperGSC to list my connected Search Console websites.The assistant should list the websites you enabled in HyperGSC. Choose one of the returned properties, then try your first report:
Use HyperGSC for [my property]. Show my top 5 pages by clicks for the latest complete 7 days available. Include the property, exact dates, search type, country and device filters, clicks, impressions, CTR and average position. State any row limits or missing data. Do not invent results if a tool call fails.Replace [my property] with the exact property returned by the connection check. Open the tool result to check the website, dates and filters. Recent Search Console data can be delayed or incomplete; use complete days for comparisons.
If something does not work
- The mcp command is missing? Check your OpenClaw version against the linked CLI reference.
- Authorization is required? Stop the Gateway, run openclaw mcp login hypergsc again and complete the browser callback. Start the Gateway again before retrying your agent turn.
- The server is saved but no tools appear? Stop the Gateway before running openclaw mcp doctor hypergsc --probe. Check tool filters and confirm the selected runtime supports MCP tools, then start the Gateway again before retrying your agent turn.
- Sign-in runs on a remote Gateway? Follow OpenClaw’s documented remote callback or manual code flow if your browser cannot reach its loopback address.
- Your website is missing? Check the connected Google account in HyperGSC Settings, refresh sites and make sure the property is enabled under Sites.
- No rows or different totals? Match the website, dates, search type, country, device and grouping with Search Console. Check that the dates fall within your plan’s history.
- A tool is unavailable or a quota is reached? Ask which reports your HyperGSC plan supports and how much allowance remains. Reconnecting does not reset quotas.
