# @createsomething/ground-mcp [Health: Active]

**Category:** 🤖 Coding Agents  
**Repository:** https://github.com/createsomethingtoday/create-something-monorepo  
**GitHub Stars:** 1  
**npm Downloads (last month):** 1008  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/createsomething-ground-mcp

## Description
Evidence-first code analysis for agents in TypeScript, JavaScript, and Svelte codebases.

## Tools
Capabilities this server exposes over MCP:

- **ground_compare** — Compare two files for similarity. You need to do this before you can claim they're duplicates.
- **ground_count_uses** — Count how many times a symbol is used. You need to do this before you can claim it's dead code. Distinguishes between runtime usages and type-only usages (TypeScript generics, type annotations, etc.). Type-only usages count as valid usage for types/interfaces.
- **ground_check_connections** — Check if a module is connected to other code. Understands Cloudflare Workers (routes, crons, bindings). You need to do this before you can claim it's orphaned.
- **ground_find_duplicate_functions** — Find duplicate functions across files AND within files. Catches inter-file duplicates (same name, different files) and intra-file duplicates (different names, similar implementation in same file). Research shows same-file clones have ~18% higher bug propagation risk. Supports cross-package detection in monorepos. Loads .ground.yml for ignore patterns.
- **ground_claim_dead_code** — Claim that code is dead (unused). Blocked if you haven't counted uses first, or if it's actually used.
- **ground_claim_orphan** — Claim that a module is orphaned (nothing connects to it). Blocked if you haven't checked connections first, or if it's actually connected.
- **ground_suggest_fix** — Get suggestions for fixing a duplication. Works best in the CREATE SOMETHING monorepo - suggests where to move shared code and gives you a beads command.
- **ground_check_environment** — Check for environment safety issues. Detects Workers-only APIs (caches, env.KV) reachable from Node.js entry points, or Node.js APIs in Workers code. Traces the import chain to show exactly how problematic APIs are reached.
- **ground_find_orphans** — Find orphaned modules in a directory. Scans all TypeScript/JavaScript files and identifies those with no incoming connections (nothing imports them) and no architectural connections (not a Worker entry point, not a package.json bin entry).
- **ground_find_dead_exports** — Find exports in a module that are never imported elsewhere in the codebase. Helps identify unused API surface.
- **ground_build_graph** — Build a symbol graph of all imports/exports in a directory. Use this first for repo-wide dead export analysis - much faster than find_dead_exports with broad scope.
- **ground_query_dead** — Query the symbol graph for dead exports. Run ground_build_graph first. Automatically filters out framework conventions (SvelteKit load/GET/POST, hooks, etc.) unless raw=true.
- **ground_analyze** — Batch analysis: returns duplicates, dead exports, orphans, and environment issues in one call. Reduces agent round-trips. Each finding includes confidence scores and structured fix actions.
- **ground_diff** — Incremental analysis: only report NEW issues since a baseline. Compares against git base branch or saved baseline. Agents shouldn't re-process known issues.
- **ground_verify_fix** — Verify that a fix was applied correctly. Checks if the claimed issue no longer exists without re-running full analysis.
- **ground_find_drift** — Find design system drift (violations of Canon design tokens). Detects hardcoded colors, spacing, typography, and Svelte 4 patterns that should use design tokens. Use 'extensions' to filter by file type for accurate CSS-only analysis.
- **ground_adoption_ratio** — Calculate Canon design token adoption ratio. Shows overall health and per-category breakdown. Thresholds: 90%+ healthy, 70-89% warning, <70% critical.
- **ground_suggest_pattern** — Suggest Canon design tokens to replace hardcoded values. Given a file with violations, suggests which tokens to use.
- **ground_mine_patterns** — Mine patterns to discover implicit design tokens. Analyzes CSS values across Svelte files to find repeated patterns that should become Canon tokens.
- **ground_explain** — Explain why a file has a special context (AI-native traceability). Returns context name, reason, and matched patterns for files excluded from violation checks.
- **ground_desire_paths** — Analyze desire paths - what tools agents tried to use that don't exist. Reveals opportunities for new tool development based on actual agent behavior patterns. Returns unknown tool attempts, failure patterns, and suggestions for new tools.

## Claude Desktop Quick Installation
Install path inferred — verify against the README before running it. Uses `npx` (confidence: medium):

```json
"mcpServers": {
  "ground-mcp": {
    "command": "npx",
    "args": ["-y","@createsomething/ground-mcp"]
  }
}
```

## Documentation

## What @createsomething/ground-mcp does

@createsomething/ground-mcp focuses on evidence-first analysis of TypeScript, JavaScript, and Svelte codebases. Its purpose is to give an MCP-connected agent a way to inspect software projects and base its responses on evidence from the code being analyzed.

The package belongs to the CREATE SOMETHING monorepo, a pnpm workspace containing platform packages, product surfaces, services, client packages, and experimental projects. The repository identifies deployable MCP servers and related workers as part of the services lane. That context makes this package a fit for agent workflows centered on understanding an existing codebase.

Use it when the agent needs to reason about a supported frontend or JavaScript-family repository. The language coverage includes TypeScript and JavaScript projects, as well as Svelte codebases.

## How it works

The server exposes code-analysis functionality through the Model Context Protocol. An MCP-compatible agent can use that capability as part of a broader coding workflow, while the evidence-first focus keeps analysis tied to the repository under examination.

Its supported scope is the codebase itself: TypeScript, JavaScript, and Svelte source.

## Setup and configuration

The source package is maintained in the CREATE SOMETHING monorepo. Working from that repository requires Node.js 20 or newer and pnpm 9 or newer. A basic source checkout and workspace installation is:

```bash
git clone https://github.com/createsomethingtoday/create-something-monorepo.git
cd create-something-monorepo
pnpm install
```

For repository worktrees, the project provides `pnpm bootstrap:worktree`. This command uses the repository’s pinned Node and pnpm toolchain and performs the workspace installation. The monorepo also provides lane-specific commands, including `pnpm build:services`, `pnpm check:services` where available through lane workflows, and broader root commands such as `pnpm build`, `pnpm check`, and `pnpm test`.

The package is associated with the services portion of the workspace. Follow the repository’s lane-oriented development and verification commands when building or checking service packages.

## Limitations and notes

The documented analysis scope is limited to TypeScript, JavaScript, and Svelte codebases. The package’s role is code analysis, not a general description of every service or product in the monorepo.

The repository contains many unrelated packages, including MCP hubs, shared MCP primitives, authorization support, design-system packages, and applications. Those components provide context for the wider workspace but should not be treated as capabilities of @createsomething/ground-mcp itself.

The monorepo recommends reading `AGENTS.md`, consulting `docs/` for architecture and policy, and using lane-specific commands instead of broad recursive commands when working locally.

_Full upstream README: https://allmcps.com/mcp/createsomething-ground-mcp/readme_