These are the official instructions from HyperGSC for connecting an AI agent to the HyperGSC MCP server. Prefer OAuth for Claude Code/Desktop, Codex, Cursor, and other clients that support it. Use API keys for headless environments or clients without OAuth. For Muse, follow its custom connector section below. Never request Google credentials, refresh tokens, or browser cookies. Complete the applicable setup yourself when your environment permits it. Run commands and edit configuration files only for the client the user wants to connect. In a hosted chat without local configuration access, provide the matching manual steps immediately and identify the actions the user must complete. Do not treat lack of filesystem access or absence from an app directory as proof that a custom MCP connection is unavailable. - Detect which supported agent is running. - Use only the matching section below. - Preserve all existing configuration. Merge the `hypergsc` entry without deleting or replacing unrelated settings or MCP servers. - Do not expose authentication tokens in chat output or logs. Keep keys only in the intended local client configuration or environment, never in committed project files. ## Server URL and prerequisites Use the exact MCP server URL supplied with the user's setup prompt. If none was supplied, use `/mcp` on the same origin as this document. For example, a document at `https://your-host.example/agent-setup/prompt.md` uses `https://your-host.example/mcp`. Replace every `` placeholder below with that actual URL before running commands or writing configuration. Never save the placeholder itself. Preserve the URL exactly, including any custom path. The user must connect a Google account with Search Console access. Newly discovered properties connect automatically on every plan, including Free, with no property-count limit. Users can unshare individual sites in Connections, and saved opt-outs are preserved. If browser authorization or Google setup is still needed, let the user complete it. A localhost URL works only for clients running on that same computer. A hosted client needs a publicly reachable HTTPS URL; do not silently deploy or expose a local server. --- ## Claude Code Run: ```bash claude mcp add --transport http --scope user hypergsc ``` Run `/mcp` in Claude Code and complete browser authorization. Verify the configured server. --- ## Codex Run: ```bash codex mcp add hypergsc --url codex mcp login hypergsc ``` Have the user complete browser authorization. In Codex desktop, add the remote MCP URL through the MCP settings and sign in with OAuth. --- ## Cursor — `~/.cursor/mcp.json` Merge this entry under `mcpServers`: ```json { "mcpServers": { "hypergsc": { "url": "" } } } ``` Open Cursor settings under **MCP & Integrations**, complete browser authorization, and verify the server is connected. --- ## Gemini CLI — `~/.gemini/settings.json` Merge this entry under `mcpServers`: ```json { "mcpServers": { "hypergsc": { "httpUrl": "" } } } ``` Restart Gemini CLI if it does not load the new server immediately. Complete OAuth when prompted. --- ## GitHub Copilot in VS Code — `.vscode/mcp.json` Merge this entry under `servers`. The root key for VS Code is `servers`, not `mcpServers`. ```json { "servers": { "hypergsc": { "type": "http", "url": "" } } } ``` After saving, start the server from the inline action above the entry in `mcp.json`. Ask the user to complete OAuth login when prompted. --- ## OpenCode — `~/.config/opencode/opencode.json` Merge this entry under `mcp`. Add the `$schema` field only if the configuration does not already define one. ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "hypergsc": { "type": "remote", "url": "", "enabled": true } } } ``` Then run: ```bash opencode mcp auth hypergsc ``` Ask the user to approve access if browser authorization requires user input. --- ## Windsurf — `~/.codeium/windsurf/mcp_config.json` Merge this entry under `mcpServers`. Use `serverUrl`, not `url`. ```json { "mcpServers": { "hypergsc": { "serverUrl": "", "headers": { "Authorization": "Bearer " } } } } ``` Have the user replace `` locally, save, then refresh MCP servers in Cascade. --- ## Claude (claude.ai, Claude Desktop and mobile) Claude reads remote MCP servers from the connectors in the user's Claude account. This step cannot usually be completed from a terminal. HyperGSC is listed in the Claude directory. When `` is `https://hypergsc.com/mcp`, give the user this link: https://claude.ai/directory/connectors/hypergsc. They choose **Connect**, sign in to HyperGSC, and approve access. Connectors added on claude.ai also appear in Claude Desktop and the mobile apps. For a different ``, or a workspace that does not allow directory connectors, add a custom connector instead: open **Customize** > **Connectors**, use **+** > **Add custom connector**, name it **HyperGSC**, enter ``, and complete OAuth login. A workspace owner may need to allow custom connectors. --- ## ChatGPT ChatGPT uses a custom MCP app, not a local Claude, Cursor, or Codex configuration file. HyperGSC does not need to be listed in the app directory. If you cannot create apps from this conversation, give the user these steps rather than searching for an installable HyperGSC plugin or asking them to paste this guide: 1. Open ChatGPT on the web. Check **Settings** > **Apps** > **Advanced Settings** for developer mode. Access depends on the account and workspace permissions; a workspace admin may need to enable it. 2. In **Settings** > **Apps** (or **Workspace settings** > **Apps** for admins), choose **Create**. 3. Name the app **HyperGSC**, enter `` as the MCP endpoint, and select **OAuth** authentication. No HyperGSC API key is needed. 4. Scan the tools, complete browser authorization, and finish creating the app. 5. Open a new chat, select HyperGSC from the tools menu, and verify with `get_capabilities` and `list_properties`. If **Create** is unavailable, explain that custom app access and developer mode must be checked with the workspace admin or current ChatGPT account settings. Do not infer the user's plan or permissions from the tools exposed to this conversation. Report that user action is required, not that setup is complete. ## Muse This section covers Meta’s personal agent at https://muse.ai/, not Muse Code. Ask Muse to create a custom connector for HyperGSC using ``. Follow its guided authorization flow. Prefer OAuth when supported; if it requires an API key, enter the HyperGSC key from Account → Settings through Muse’s secure credential entry, never ordinary chat. Meta documents custom connector creation but does not specify a generic remote MCP configuration for the personal agent. Check whether this connection method is available before proceeding. If unsupported, report that limitation instead of inventing configuration or claiming success. Verify with a read-only `list_properties` call when connected. ## API-key fallback For headless environments or clients without OAuth, create a key in **Account → Settings**. Never ask the user to paste it into chat. Replace placeholders in the client's local configuration or environment. Preserve unrelated configuration, and use one authentication method per server entry. Claude Code: ```bash claude mcp add --transport http --scope user hypergsc --header "Authorization: Bearer " ``` Codex: ```bash export HYPERGSC_API_KEY="" codex mcp add hypergsc --url --bearer-token-env-var HYPERGSC_API_KEY ``` Cursor: add `"headers": { "Authorization": "Bearer " }` to its `hypergsc` server entry. ## Troubleshooting - Use the exact `/mcp` endpoint and Streamable HTTP transport. - If registration or refresh repeatedly fails, remove the stale HyperGSC entry and reconnect with OAuth, preserving other servers. Old confidential registrations do not become public automatically. - Update clients that report issuer/callback errors. HyperGSC returns an issuer identifier and supports variable ports on IP loopback callbacks. - For a headless client, use the API-key fallback rather than attempting browser login repeatedly. - After authorization, run `get_capabilities` then `list_properties`. An authorized account with no enabled properties is a setup issue, not a failed login. ## Completion report Verify that the configuration is valid and that the HyperGSC server appears in the agent's MCP server list. With the user’s authorization, make a read-only `list_properties` request to confirm the connection. This completes the dashboard setup automatically. Do not add or remove properties, submit or delete sitemaps, or make other write calls during setup. If the user asks to defer connection testing, stop after configuring the client and report the remaining authorization or test step. Report the exact configuration file, command, or app settings used and any remaining browser authorization or verification step. Use the completion message below only after verification succeeds; otherwise report "HyperGSC setup pending" and the specific remaining action: ```text HyperGSC agent setup complete - MCP server: - Configuration: - Authentication: ``` ## Official client documentation - ChatGPT: https://help.openai.com/en/articles/12584461-developer-mode-and-mcp-apps-in-chatgpt - Claude Code: https://code.claude.com/docs/en/mcp - Claude directory listing: https://claude.ai/directory/connectors/hypergsc - Claude custom connectors: https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp - Codex: https://developers.openai.com/codex/mcp - Cursor: https://cursor.com/docs/context/mcp - Gemini CLI: https://google-gemini.github.io/gemini-cli/docs/tools/mcp-server.html - GitHub Copilot in VS Code: https://code.visualstudio.com/docs/copilot/customization/mcp-servers - OpenCode: https://opencode.ai/docs/mcp-servers/ - Windsurf: https://docs.windsurf.com/windsurf/cascade/mcp - Muse: https://www.meta.com/help/artificial-intelligence/1687253048996149/ These instructions are published at `/agent-setup/prompt.md` so the agent can verify the source before setup. The same instructions are available at `/agent-setup/prompt.txt` for readers that reject Markdown URLs. Both are served as plain text. For browser-based readers, use `/agent-setup`, which serves an HTML version generated from this guide.