Decantr Mcp Server

by decantr-ai

1.4k downloads Not rated yet

GitHub Website

Other

About

# Decantr **AI Frontend Governance for production codebases touched by AI agents.** Decantr is the governance layer between product intent and AI-edited frontend code. It gives coding assistants three things they don't have on their own: typed contracts, route-scoped context, and machine-actionable evidence, so UI…

Explore

- Exposes essence reads, vocabulary resolution, and context reads
- Executes pack compilation and drift checks
- Runs critique, audit, and v2

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name Decantr Mcp Server

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

From the repository

Install the Decantr CLI (@decantr/cli) and run decantr connect cursor from the project workspace to automatically configure the MCP server for Cursor. For other AI assistants, open the project and read DECANTR.md first, then load section context files. The MCP server is also available as the @decantr/mcp-server package for manual setup.

`decantr_project`

Observe local project authority, selected-app discovery, adoption truth, and workspace health without uploading source.

`decantr_contract`

Read and validate the project-owned Decantr contract, inspect drift, or create a compatibility contract skeleton.

`decantr_context`

Prepare discovery-backed UI surface task context, preserve authoritative route capsules, or read existing scaffold, section, page, and execution-pack context.

`decantr_graph`

Read, query, and traverse local graph and source evidence that supports route-scoped UI work.

`decantr_registry`

Legacy-named compatibility access to the official Decantr content corpus, benchmark metadata, and execution packs; not a public registry.

`decantr_verify`

Verify local UI diffs with changed-UI assurance, or return deeper critique, findings, health state, and evidence bundles.

`decantr_repair`

Turn typed verification findings into scoped repair plans, prompts, and health-loop guidance.

`decantr_contract_write`

Explicit workspace-contained write surface for accepting drift or updating the Essence v4 contract.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "decantr mcp server": {
            "decantr": {
                "command": "npx",
                "args": [
                    "-y",
                    "@decantr/mcp-server"
                ]
            }
        }
    }
}

McpServers

{
    "decantr": {
        "command": "npx",
        "args": [
            "-y",
            "@decantr/mcp-server"
        ]
    }
}

AI Frontend Governance for production codebases touched by AI agents.

Decantr is the governance layer between product intent and AI-edited frontend code. It gives coding assistants three things they don't have on their own: typed contracts, route-scoped context, and machine-actionable evidence, so UI changes stay coherent instead of drifting prompt by prompt. The model still writes the code; Decantr defines the contract, context, and verification loop around it.

> AI generates the interface. Decantr proves, with local evidence, whether the outcome stayed aligned.

Pick your path

| Path | Use when | Start with |
| --- | --- | --- |
| Brownfield adoption  ⭐ | Attaching Decantr to an existing Angular/React/Vue/etc. project | decantr scan -> decantr adopt --yes |
| Hybrid operating layer | An attached app wants selected Decantr or project-owned UI law, without source takeover | decantr codify, decantr doctor, decantr task |
| Greenfield content contract | New project, official content-corpus composition as governance context | decantr new my-app --blueprint=<id> --workflow=greenfield |
| Greenfield contract-only | New project or repo that wants Decantr governance but no blueprint/runtime takeover | decantr init --workflow=greenfield --adoption=contract-only |

---

Greenfield Content Contracts

1. Scaffold from a blueprint

npx @decantr/cli new my-app --blueprint=esports-hq
cd my-app

A blueprint is official corpus content: theme, sections, pages, layouts, voice, and personality that compile into Decantr contracts and execution packs. It is reference material for governance, not a public marketplace or runtime takeover. Try esports-hq, agent-studio, or carbon-ai-portal, or run decantr list blueprints --blueprint-set featured to browse the curated set.

> Adapter availability. Greenfield defaults to contract-only governance. The legacy @decantr/css runnable adapters (react-vite, next-app, vanilla-vite, vue-vite, sveltekit, angular, and solid-vite) remain available only when explicitly requested with --adoption=decantr-css. Other targets initialize through generic-web contract-only mode.

2. What just got generated

my-app/
├── decantr.essence.json     # the durable contract: theme, sections, routes, features
├── DECANTR.md               # methodology primer your AI assistant reads first
├── .decantr/context/
│   ├── scaffold.md          # full app overview: topology, voice, personality
│   └── section-*.md         # per-section spec: shell, patterns, spacing
└── src/styles/
    ├── tokens.css           # CSS variables from the theme
    ├── treatments.css       # shared visual treatment classes
    └── decorators.css       # theme-specific decorator classes

Decantr produces the contract. Your AI assistant produces the implementation against it.

3. Hand it to your AI assistant

Open the project in Claude Code, Cursor, Windsurf, or any AI-aware editor. For Cursor, run decantr connect cursor once from the opened workspace; in monorepos use decantr connect cursor --project apps/web. It writes .cursor/mcp.json and .cursor/rules/decantr.mdc, preserving existing MCP servers, so Cursor Agent knows to call Decantr task context before route edits. Other assistants can read DECANTR.md first for the methodology, then load section context files on demand. For route-level work, run decantr task <route> "<intent>" before editing so the assistant gets the active authority block, local law, evidence, and verify command. The split keeps the assistant focused on the right scope at the right time.

4. Make your first change and verify

```bash

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Explore

Setting up with Highlight

From the repository

decantr_project

decantr_contract

decantr_context

decantr_graph

decantr_registry

decantr_verify

decantr_repair

decantr_contract_write

Claude Desktop / Cursor

McpServers

Pick your path

Greenfield Content Contracts

1. Scaffold from a blueprint

2. What just got generated

3. Hand it to your AI assistant

4. Make your first change and verify

More like this

Sequential Thinking

Filesystem

EverArt

Google Drive

`decantr_project`

`decantr_contract`

`decantr_context`

`decantr_graph`

`decantr_registry`

`decantr_verify`

`decantr_repair`

`decantr_contract_write`