# Standards by Applied Form MCP server

> Lints rendered web pages against design system tokens in a real browser to ensure conformance across multiple widths and accessibility rules.

- Repository: https://github.com/Applied-Form/standards
- Page: https://hostedmcp.org/servers/applied-form/standards
- Transport: stdio
- Stars: 0
- License: Apache-2.0
- Latest version: 5.0.0

## Install

### Claude Code

```sh
claude mcp add standards -- npx -y @appliedform/standards
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "standards": {
      "command": "npx",
      "args": [
        "-y",
        "@appliedform/standards"
      ]
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "standards": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@appliedform/standards"
      ]
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"standards","type":"stdio","command":"npx","args":["-y","@appliedform/standards"]}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "standards": {
      "command": "npx",
      "args": [
        "-y",
        "@appliedform/standards"
      ]
    }
  }
}
```

### Codex

```sh
codex mcp add standards -- npx -y @appliedform/standards
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.standards]
command = "npx"
args = ["-y", "@appliedform/standards"]
```

### Gemini CLI

```sh
gemini mcp add -s user standards npx -- -y @appliedform/standards
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "standards": {
      "command": "npx",
      "args": [
        "-y",
        "@appliedform/standards"
      ]
    }
  }
}
```

## Tools (9)

- `standards_lint`: Measure a page against the design system in a real browser and return every violation with the fix. Pass html for a draft, or url for something already served. This is the loop: draft, lint, apply the fixes, lint again.
- `standards_fix`: Apply the fixes Standards can make on its own to a draft, measured in a real browser, and return the fixed HTML with a report: rules fixed, patches applied and refused, and what still fails, by element. No model is called, and a fix that makes any rule worse is not applied. Pass html; what remains needs a change to the markup.
- `standards_rules`: Every rule the gate enforces: what it requires, why, how to fix it, and which WCAG criteria it touches. Filter by group to keep the answer small.
- `standards_tokens`: The values the system permits: colours, spacing scale, type scale, voices, floors, ratios, and what it declares absent. Ask for this instead of guessing a value.
- `standards_contrast`: Measure a foreground against a background: the WCAG 2 ratio, the floor required at that size and weight, whether it passes, and the APCA reading as an advisory.
- `standards_brand`: Derive a complete palette from a hue and a paper colour, measured against every floor, or refuse it with the reasons. Use this instead of inventing a palette.
- `standards_move`: The recipe for a named compositional move: its cells, layers, voices and ground. One move is active per artefact; ask for the one you need rather than reading all of them.
- `standards_system`: Read a design system authored elsewhere (a Standards pack tokens.json) into this one, reporting what it stated, what had to be derived, and what could not be carried across.
- `standards_drift`: Measure what a design system actually is on pages that were not built to this one, and how far they have drifted from it: the palette, spacing step and type scale in use, plus how many values are indistinguishable duplicates. Use this to learn somebody else's system before working in it, rather than guessing from a screenshot.

## FAQ

### How can I use Standards with an AI agent like Claude Code or Cursor?

You can generate the necessary configuration by running the command `npx standards mcp-config`.

### Can the tool automatically fix design system violations?

Yes, the `standards fix` command applies fixes to the page and writes a new file named page.fixed.html.

### What happens if I try to disable mandatory accessibility rules?

The tool will refuse the configuration and exit with code 2, as certain rules like contrast and target size are mandatory.

### Does it check against a stylesheet or the actual rendered output?

It reports what the browser actually drew based on computed values, rather than just what is written in the stylesheet.
