What is gsc-mcp-server CLAUDE.md?

Repository instructions for coding agents working on Klartika’s fork of a Google Search Console server, including its local and deployed server arrangements.

Use them when changing, running, authenticating, or deploying this server so fork-specific behavior stays separate from the unchanged upstream code.

They explain the repository’s rules, authentication setup, important files, and the file that must not be edited.

How Klartika/gsc-mcp-server configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Klartika/gsc-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Klartika/gsc-mcp-server/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/Klartika/gsc-mcp-server

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/klartika/gsc-mcp-server/claude-md/github.svg)](https://agentmods.dev/instructions/klartika/gsc-mcp-server/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/klartika/gsc-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/klartika/gsc-mcp-server/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/klartika/gsc-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/klartika/gsc-mcp-server/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,320 This file is loaded in full into every session.

When invoked 1,320 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.01320	$0.01320
Opus 5	$0.00660	$0.00660
Sonnet 5	$0.00264	$0.00264
Haiku 4.5	$0.00132	$0.00132

Measured 8d ago against content hash ef9d71ff122b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

gsc-mcp-server CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 129 lines

How it starts

The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

Context for AI coding assistants (Claude, Cursor, Copilot, etc.) working in this repo.

This is Klartika's fork. Read AGENTS.md before changing anything — it carries rules that keep this fork rebaseable on upstream, and breaking them is easy to do by accident while following the sections below.

The most important one: never edit gsc_server.py. All fork behaviour lives in gsc_remote/.

What this is

Two servers in one repo:

Upstream's local (stdio) server — gsc_server.py, a single ~1,700-line file built with FastMCP. Unmodified. The sections below describe it.
This fork's remote server — gsc_remote/, an OAuth 2.1-protected HTTP transport where each user signs in with their own Google account. This is what is actually deployed. See AGENTS.md for its layout and docs/OPERATIONS.md for running it.

Per-request credentials reach upstream's unchanged tools through a runtime monkeypatch of get_gsc_service() bound to a ContextVar — that is the single seam between the two, and tests/remote/credentials_test.py guards it.

Running locally

uv sync
uv run python gsc_server.py

Auth

Two modes, tried in order:

OAuth (default): Place client_secrets.json in the repo root. On first run, a browser window opens for Google login. Token saved to token.json (gitignored), auto-refreshes when expired.
Service account: Set GSC_CREDENTIALS_PATH to the path of your service account JSON key file.

Set GSC_SKIP_OAUTH=true to force service account mode and skip OAuth entirely.

Key environment variables

These are upstream's, for the local server. The remote server's are a different set entirely — see DEPLOY.md.

Variable	Default	Description
`MCP_TRANSPORT`	`stdio`	Set to `sse` for remote/Docker/network use
`MCP_HOST`	`127.0.0.1`	Host to bind when `MCP_TRANSPORT=sse`
`MCP_PORT`	`3001`	Port to bind when `MCP_TRANSPORT=sse`
`GSC_DATA_STATE`	`all`	`all` = matches GSC dashboard; `final` = confirmed data only (2–3 day lag)
`GSC_ALLOW_DESTRUCTIVE`	`false`	Set `true` to enable `add_site`, `delete_site`, `delete_sitemap`
`GSC_CREDENTIALS_PATH`	—	Path to service account JSON key file
`GSC_OAUTH_CLIENT_SECRETS_FILE`	`client_secrets.json`	Path to OAuth client secrets file
`GSC_SKIP_OAUTH`	`false`	Set `true` to skip OAuth and use service account only

Read the full file on GitHub · 129 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

8d ago First seen · 129 lines · 1,320 tokens per session scan A ef9d71ff122b

Subscribe to this mod's changes

gsc-mcp-server CLAUDE.md is an instructions file published in the GitHub repository Klartika/gsc-mcp-server (0 stars, last pushed 21d ago), licensed MIT. It adds 1,320 tokens to every session, about $0.0066 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

gsc-mcp-server: Instructions file for Claude Code