Concept illustration: teammates compare two graphite code-shaped pieces on an inspection table before making a claim.

Ground 0.5.4 / Free and open source

Give the agent evidence.

Check the code before recording a finding. Ground gives your agent evidence for TypeScript, JavaScript, and SvelteKit code claims.

Choose your install

An MCP tool for your existing agent client.

Concept illustration / Compare before claiming

01 / Connect

Put the check
beside the agent.

Choose one client. Install Ground, check the source, then inspect the finding.

Version 0.5.4 · Choose the configuration for your client.

Claude CodeRegister Ground for the current user
claude mcp add --scope user --transport stdio ground -- npx --yes -p @createsomething/[email protected] ground-mcp
Cursor or WindsurfPaste into the client MCP configuration
{"mcpServers":{"ground":{"command":"npx","args":["--yes","-p","@createsomething/[email protected]","ground-mcp"]}}}
Codex CLIRegister Ground as a local MCP server
codex mcp add ground -- npx --yes -p @createsomething/[email protected] ground-mcp
npmWorks with any MCP client
npm install -g @createsomething/[email protected]

Persistent MCP sessions reuse parsed source and dependency graphs after checking current files and resolution settings. Restart your MCP server after upgrading. CLI commands stay uncached by default; use --cache to opt in or --no-cache to disable reuse.

02 / Verify

Check first.
Then claim.

Ground requires a check before its claim tools can record a code finding.

  1. 01Check first

    Compare the files or count the uses.

  2. 02Then claim

    Attach the finding to what was checked.

  3. 03Blocked otherwise

    Stop an unsupported conclusion before it spreads.

# A claim without a prior comparison
ground claim duplicate utils.ts helpers.ts "same validation logic"
Claim blocked: compare these files first.

# Check first, then retry the claim
ground compare utils.ts helpers.ts

Ground gates its own claim tools; it cannot stop an agent from answering outside them. An unused export in the checked scope still needs review for public APIs, external consumers, and dynamic loading before removal.

03 / Evidence

Inspect what
backs the finding.

Code checks, measured performance, and release calibration. Each has a defined scope.

Explore the tool reference Verification, patterns, and claims

Verify

  • ground_compareSee how similar two files actually are
  • ground_count_usesCount detected uses in the checked scope
  • ground_check_connectionsSee whether a module is connected
  • ground_check_environmentCatch runtime APIs in the wrong environment

Find problems

  • ground_find_duplicate_functionsFind copy-pasted code
  • ground_find_orphansFind files with no detected connection
  • ground_find_dead_exportsFind exports with no imports in the checked scope
  • ground_find_driftFind divergence from an owned pattern

Understand patterns

  • ground_adoption_ratioMeasure token or pattern adoption
  • ground_suggest_patternSuggest from the code already present
  • ground_mine_patternsDiscover repeated structures

Report findings

  • ground_claim_duplicateReport a verified duplicate
  • ground_claim_dead_codeReport verified dead code
  • ground_claim_orphanReport a verified orphan

Your next code claim

Put evidence
before the answer.

Install Ground in one agent client, run a real verification, and preserve the checked inputs with the finding.

Install Ground from npm
Inspect the source ↗ Read the Kickstand audit ↗ Explore Agent Foundation ↗ Explore the product family ↗

Ground gates its own claim tools. The codebase operator reviews the finding and decides what to change.