Skip to main content
HyperGSC publishes a hosted Model Context Protocol server so compatible AI assistants can use your selected Search Console data. For Claude and Claude Desktop, use the HyperGSC connector in Claude’s directory. Follow the Claude setup guide to complete browser sign-in. For clients that ask for a remote server URL, use:
See the guides for ChatGPT, Claude, Codex, or Cursor. HyperGSC’s AI tools page includes additional client instructions.

​
What the connection exposes

The server provides tool schemas for search analytics, period comparisons, URL inspection, sitemaps, SEO diagnostics, and research. Your account’s plan, usage, Google access, and authorization scopes determine which requests can execute. Search Console access is read-only. Optional research writes store records in HyperGSC and require separate projects:write consent.

​
A reliable first sequence

  1. Connect and authorize the MCP client.
  2. Call get_capabilities to read current account and tool availability.
  3. Call list_properties and choose an exact enabled site_url.
  4. Run a small report.
  5. Read the response metadata before summarizing it.
Refresh discovery after account or server changes. The catalog can include tools that are currently unavailable to your account.

​
For custom integrations

The transport is Streamable HTTP. Use an MCP client that handles initialization, protocol negotiation, tool discovery, and calls. Discovery resources include:

​
HTTP API boundary

HyperGSC also exposes an HTTP API description and OpenAPI document. Those routes support the dashboard and require browser sessions and request protection where indicated. Use MCP with browser OAuth for agent integrations. Dashboard HTTP routes use their documented browser-session requirements. Continue with authentication, the tool reference, or errors and limits.