# AINDF

A read-only MCP server over a single AINDF design-system bundle. Agents browse components, slots and presets, then validate screens against those contracts.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 28
- Author: 0design
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/0design/ai-native-design-framework/tree/HEAD/packages/aindf-kit
- Updated: 2026-10-11
- HTML: https://affpapa.org/en/nevibecode/mcp/aindf

## What it does

The `aindf mcp` process speaks MCP over stdio and serves one design-system bundle. That bundle comes from `aindf bundle`, which seals a content hash (`bundleSha256`) so screens stay pinned to one revision. Run `bundle` first; there is nothing for the server to hand out otherwise.

Seven tools are exposed read-only: `list-by-facet`, `slot-accepts`, `applicable-modifiers`, `get-preset`, `get-ds`, `get-component` and `validate-screen`. Each ships with a `title` plus MCP hints such as `readOnlyHint`, so the client can tell that nothing gets written. Validation runs against closed contracts: props are fixed, a slot accepts a limited set of components, tokens only point downward through the layers.

Two more tools, `submit-screen` and `request-extension`, belong to an endpoint with staging, need an author token, and stage drafts that nobody has accepted yet. A local run has neither, so your agent hands back a `ScreenSpec` or tells you what is missing. The package carries no design system of its own, and a builder receipt is not a signature.

## Requirements
- Needs: Node.js (commands run via npx)

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add aindf-kit -- npx -y @ai-native-design-framework/kit
```

### Codex

**Platform CLI**
```bash
codex mcp add aindf-kit -- npx -y @ai-native-design-framework/kit
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "aindf-kit": {
            "command": "npx",
            "args": [
                "-y",
                "@ai-native-design-framework/kit"
            ]
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "aindf-kit": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "@ai-native-design-framework/kit"
            ]
        }
    }
}
```

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add aindf-kit npx -y @ai-native-design-framework/kit
```

## When to use it
- see which components a given slot will take
- validate a screen against the bundle before building
- pull a component contract with its template and props
- find which modifiers apply to a role
- check which design-system revision a screen is pinned to

## Example prompts
- List the components in this bundle that accept the `actions` slot
- Run `validate-screen` on `settings.screen.json` and show me what fails
- Which modifiers can I apply to the button here?

## Similar
- [Next AI Draw.io](https://affpapa.org/en/nevibecode/mcp/next-ai-drawio.md) — MCP server · ★ 36398
- [tldraw](https://affpapa.org/en/nevibecode/mcp/tldraw.md) — MCP server · ★ 51091
- [Figma-Context-MCP](https://affpapa.org/en/nevibecode/mcp/figma-context-mcp.md) — MCP server · ★ 16062
- [Agent-Native Assets](https://affpapa.org/en/nevibecode/mcp/agent-native-assets.md) — MCP server · ★ 7506
- [Remove AI Watermarks](https://affpapa.org/en/nevibecode/mcp/remove-ai-watermarks.md) — MCP server · ★ 6114
- [Dembrandt](https://affpapa.org/en/nevibecode/mcp/dembrandt.md) — MCP server · ★ 3821

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md