Decantr AI MCP server

Help AI build like it belongs here.

Agent-neutral UI change control for codebases edited by AI.

Website · Get started · Documentation · Discord

Decantr checks the UI change an AI coding agent actually made against the components, styles, interaction rules, and source boundaries already owned by your project. It reports a small set of source-anchored findings without replacing your stack or generating the change itself.

Check your current UI change

No account, setup, or adoption step is required:

npx @decantr/cli@3.11.3 verify

CHANGED UI          PROJECT AUTHORITY       VERIFY              RESULT
What the agent  →   What your app        →  Compare the      →   Pass, attention,
actually edited     already owns            current change       or not proven

Bare verify is read-only. It resolves the current Git change, selects exactly one changed UI app only when that choice is provable, and returns at most three consequential findings with source and repair targets.

From one check to a governed loop

Changed-UI Assurance is the zero-setup entry point. Teams can deepen it into an authority-aware workflow when they need durable task context and CI evidence.

1. Observe project-owned UI authority and state what is unknown.
2. Prepare compact, change-scoped context for any coding agent.
3. Verify the resulting diff against project authority and available evidence.
4. Report typed, reproducible evidence for people, agents, and CI.

npx @decantr/cli@3.11.3 scan
npx @decantr/cli adopt --yes       # one-time attachment
npx @decantr/cli task /feed "add saved actions"
npx @decantr/cli verify --full
npx @decantr/cli ci init           # one-time CI setup

In a monorepo, install once at the workspace root and select the app consistently:

pnpm add -D -w @decantr/cli
pnpm exec decantr scan --project apps/web
pnpm exec decantr adopt --project apps/web --yes
pnpm exec decantr task /feed "add saved actions" --project apps/web
pnpm exec decantr verify --project apps/web

scan and bare verify are read-only. adopt is the explicit one-time write boundary. Use verify --full for Project Health and its evidence or baseline options.

What Decantr treats as UI authority

Routes are evidence, not the product ontology. Decantr can reason about routes, layouts, reusable components, stories, overlays, flows, design-system packages, runtime states, and exact source files.

It evaluates authority on independent axes:

• selected app and production surface authority;
• topology completeness and implementation taskability;
• component inventory and styling authority;
• available runtime evidence.

Shortened. The full README is on GitHub.