> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hypergsc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# HyperGSC MCP server overview

> Connect AI assistants to HyperGSC's hosted Google Search Console MCP server and understand discovery, tools, authorization, and the dashboard API boundary.

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](https://claude.ai/directory/hypergsc). Follow the [Claude setup guide](https://docs.hypergsc.com/integrations/claude.md) to complete browser sign-in.

For clients that ask for a remote server URL, use:

```text theme={null}
https://hypergsc.com/mcp
```

See the guides for [ChatGPT](https://docs.hypergsc.com/integrations/chatgpt.md), [Claude](https://docs.hypergsc.com/integrations/claude.md), [Codex](https://docs.hypergsc.com/integrations/codex.md), or [Cursor](https://docs.hypergsc.com/integrations/cursor.md). 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:

* [Protected resource metadata](https://hypergsc.com/.well-known/oauth-protected-resource/mcp)
* [OAuth authorization server metadata](https://hypergsc.com/.well-known/oauth-authorization-server)
* [Agent authentication walkthrough](https://hypergsc.com/auth.md)
* [Client setup instructions](https://hypergsc.com/agent-setup/prompt.md)

## HTTP API boundary

HyperGSC also exposes an [HTTP API description](https://hypergsc.com/api/docs.md) and [OpenAPI document](https://hypergsc.com/api/openapi.json). 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](https://docs.hypergsc.com/mcp/authentication.md), the [tool reference](https://docs.hypergsc.com/mcp/tool-reference.md), or [errors and limits](https://docs.hypergsc.com/mcp/errors-and-limits.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.