mcp-google-merchants: Instructions file for Claude Code

CLAUDE.md

mcp-google-merchants CLAUDE.md is an instructions file for Claude Code from A1-x-Tech/mcp-google-merchants. It costs 2,058 tokens per session, scanned A, original, MIT.

Project instructions for developing the mcp-google-merchants server, an MCP integration with Google Merchant Center's Merchant API.

In plain words
What is it for?
Use them when running tests, type checks, builds, or read-only smoke checks, and when adding tools without using obsolete Merchant Center API versions or paths.
Why use it?
They document the server's commands, architecture, authentication, API paths, product ID format, and conventions that contributors must preserve.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md.

This is A1-x-Tech/mcp-google-merchants's own configuration. It tells Claude Code how to work on mcp-google-merchants itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-google-merchants configures →

Reuse

Borrowing it

Nothing to install: this file belongs to A1-x-Tech/mcp-google-merchants. 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/A1-x-Tech/mcp-google-merchants/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/A1-x-Tech/mcp-google-merchants

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.

agentmods badge for mcp-google-merchants CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/a1-x-tech/mcp-google-merchants/claude-md/github.svg)](https://agentmods.dev/instructions/a1-x-tech/mcp-google-merchants/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/a1-x-tech/mcp-google-merchants/claude-md"><img src="https://agentmods.dev/badge/instructions/a1-x-tech/mcp-google-merchants/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.

agentmods 80×15 button for mcp-google-merchants CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/a1-x-tech/mcp-google-merchants/claude-md"><img src="https://agentmods.dev/badge/instructions/a1-x-tech/mcp-google-merchants/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,058 This file is loaded in full into every session.
When invoked 2,058 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02058 $0.02058
Opus 5 $0.01029 $0.01029
Sonnet 5 $0.00412 $0.00412
Haiku 4.5 $0.00206 $0.00206

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

Security

Grade A, and why

mcp-google-merchants 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 9d 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 · 122 lines

How it starts

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

CLAUDE.md — mcp-google-merchants

MCP server for Google Merchant Center via the Merchant API v1 (TypeScript, stdio). Single host https://merchantapi.googleapis.com with per-sub-API path prefixes (accounts/v1, products/v1, datasources/v1, promotions/v1, reports/v1, issueresolution/v1, quota/v1). Auth is Google OAuth 2.0 (scope https://www.googleapis.com/auth/content): the client exchanges a refresh token at https://oauth2.googleapis.com/token and caches the access token, or uses a static GOOGLE_MERCHANTS_ACCESS_TOKEN. This is a write-capable server: products and promotions can be created and deleted. Do NOT copy paths or product-ID formats from Content API for Shopping (content/v2.1, sunset 2026-08-18) or v1beta (shut down 2026-02-28) — v1 product IDs are contentLanguage~feedLabel~offerId, no channel.

Commands

npm run dev        # run from source (tsx watch)
npm test           # unit tests + dist smoke, no network
npm run typecheck  # types for src + tests
npm run build      # emit dist/
npm run smoke      # live READ-ONLY call (needs real credentials)

Architecture

  • src/config.ts — env → config. Credentials: the OAuth trio (GOOGLE_MERCHANTS_CLIENT_ID/_CLIENT_SECRET/_REFRESH_TOKEN — all three or ConfigError incomplete_oauth, whose message lists the missing variables) or GOOGLE_MERCHANTS_ACCESS_TOKEN; optional GOOGLE_MERCHANTS_ACCOUNT_ID, _API_BASE, _TOKEN_URL, _TIMEOUT_MS, _MAX_RETRIES. No credentials at all is NOT an error: the fields stay undefined (empty string = absent) and the server starts degraded. Also home to CredentialsError / MISSING_CREDENTIALS_MESSAGE (opens with the historical startup error verbatim, then names the variables and the restart) and hasCredentials().
  • src/client.ts — all HTTP and all wire mapping: token refresh (cached, shared across concurrent calls, one automatic retry on 401), accountPath() fallback to the configured default account, data-source name expansion, per-endpoint methods with camelCase wire bodies, query-param building. request() resolves the path against the base and rejects any path that escapes to a foreign origin (SSRF guard), retries 429 on any method but 5xx/network errors on GET only, honors Retry-After, enforces an AbortController timeout that also covers reading the body, and throws MerchantsError(status, body) (decodes the Google error envelope).
  • src/tools/*.ts — one register fn per domain (accounts, products, datasources, promotions, reports, issues, quota) + raw.ts (raw_request, full method enum, DESTRUCTIVE annotations). util.tsok/fail, the READ_ONLY/WRITE/DESTRUCTIVE annotation constants and shared zod schema factories.
  • src/index.ts — wires every register* into the McpServer. loadConfigOrDegraded() catches ConfigError, pings startup_failed (fire-and-forget) and degrades the config to "no credentials"; an unconfigured start prepends UNCONFIGURED_PREFIX — plus Configuration problem: <message> when a ConfigError was caught — to the initialize instructions, and oninitialized sends server_start for a configured install or unconfigured_start (with the reason) otherwise.
  • src/telemetry.ts — anonymous usage pings (ids/names/versions only, never data or arguments; fire-and-forget, must never block or throw; opt-out ASKADS_TELEMETRY=0). server_start means "a usable install started"; unconfigured_start is a degraded start and startup_failed a malformed config caught at load — both carry a reason from a closed vocabulary (missing_credentials, incomplete_oauth) — never a variable's name or value.

Read the full file on GitHub · 122 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.

  1. 9d ago First seen · 122 lines · 2,058 tokens per session scan A 93c644682fc5

Subscribe to this mod's changes

mcp-google-merchants CLAUDE.md is an instructions file published in the GitHub repository A1-x-Tech/mcp-google-merchants (0 stars, last pushed 10d ago), licensed MIT. It adds 2,058 tokens to every session, about $0.0103 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.

Related

Other instructions, from other repositories

vibetags com-example-service-OrderService.instructions.md

Instructions for PIsberg/vibetags, covering copilot instructions for orderservice, rules for method calculatetax, rules for method processpayment, rules for method validateorder and context & focus.

PIsberg/vibetags · 553 tokens

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

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens