![\"GoDD](\"https://unpkg.com/@autodevjapan/godd-mcp-alpha@latest/assets/godd-mcp-alpha-icon.png?v=cb453fa6bce1d316857cf3ab220fad32c980f0165cf82ecd54fb5d7ceec0a691\"){kind=icon}
\n\n \n
Govern AI development from intent to verified, shippable code.
\n\nOfficial site · Docs · Plans · Get started
\n\n[🇺🇸 English](#english) | [🇯🇵 日本語](#日本語) | [🇷🇺 Русский](#русский)\n\n---\n\n## English\n\n**Say what you want in plain language. GoDD runs the whole cycle — plan → implement → test → review → document → ship.** It works inside Cursor, Claude Code, Codex, Kimi CLI, and Antigravity over the Model Context Protocol.\n\n### Why GoDD\n\n- **~2,000–5,000 tokens per call instead of ~80,000+.** Prompts are delivered **on demand** — only the one you invoke enters context. Always-on rule files burn your context window before you even type.\n- **Your AI stops guessing.** Every prompt is built on seven proven xDD methodologies (Spec / Acceptance-Test / Test / Domain / Neo-Model / Docs / Issue-Driven Development), so it plans, tests, and documents like a senior engineer.\n- **One command does the whole job.** `/dev`, `/review`, `/ship` each run a complete cycle — not a single step you have to babysit.\n- **It knows your stack.** `godd-a init` profiles your language, framework, and tooling, and delivered prompts adapt to it.\n- **No migration.** One server registers with every client you already use.\n\n### Install\n\n```bash\nnpm install -g @autodevjapan/godd-mcp-alpha\ngodd-a install # auto-detect your MCP clients and register with each\ngodd-a init # generate a project profile\n```\n\nThen type `/` in your client and pick a GoDD prompt — or just ask (\"run dev\", \"do a review\").\n\n### Requirements\n\nNode.js 22+ · an MCP client (Cursor / Claude Code / Codex / Kimi CLI / Antigravity) · a license key.\n\nThe server validates your license online at every startup — there is no offline grace period.\n\n### Docker startup\n\nAt server startup, GoDD checks whether the Docker daemon responds. On Windows and macOS, if it does not, GoDD checks whether Docker Desktop is already running before requesting a launch; it does not start a second instance. If process state cannot be confirmed, it skips the launch. Linux uses systemd/service to start Docker. The MCP server continues if Docker is unavailable. On Windows, Docker status-check helpers and MCP-managed child processes use hidden-console mode.\n\n**Breaking Registry change (#2986):** responses must declare a content generation. `CLIENT_GENERATION_MISSING` means the server migration is incomplete; ask the Registry operator to finish it. `CLIENT_GENERATION_MALFORMED` means the generation metadata is invalid; `CLIENT_GENERATION_SPLIT` means a response mixes generations. These errors stop delivery. `GENERATION_DIGEST_ABSENT` is a separate, nonfatal diagnostic for delivery from the last-known-good cache. Failed MCP prompt requests now return a protocol error, and are not counted as usage.\n\n### Optional compatibility reporting with anonymous aggregates\n\n**Explicit participation only:** the public route, policy and operational-log disclosure are verified. Delivery is available only after the reporting-enabled native artifacts and their packaged four-target gate are verified and promoted. Older prepared binaries keep delivery disabled.\n\nReporting is off unless you set `GODD_NATIVE_HANDSHAKE_REPORTING=railway-aggregate-v2` after reading the [privacy policy](https://getgodd.dev/legal/privacy). The [version 2 reporting policy](https://native-handshake-diagnostics-production.up.railway.app/legal/native-handshake-reporting-v2) discloses Railway operational logging of IP, User-Agent, URL and request metadata; the transport is not anonymous. Old anonymous-v1 consent is not reused. On a startup compatibility rejection, GoDD sends only its reason code, the stable npm version, and the OS family to a fixed HTTPS endpoint, once, with at most 1.5 seconds waiting for the reporting subprocess, plus binary preparation and cleanup. No license, identity, path, digest, or command is sent. The server keeps daily counts for 30 UTC days; production collection requires verified dedicated ingress and disclosure. Counts are reports from volunteers, not user counts or a rejection rate. Unset the variable and restart GoDD to withdraw consent. Individual reports cannot be identified for deletion. Reporting failures never change startup behavior.\n\n### Everything else\n\nThe full tool list, CLI reference, and troubleshooting live on the **[documentation site](https://www.getgodd.dev/en/docs)**.\n\nThe Stage 1 Rust archive admission reader is available for bounded OOXML\npackage diagnostics. `godd-native office-package-admission --path