AI: agent rules, MCP, skill and llms.txt

AI coding tools write better interfaces when they know what already exists and how it was meant to be used. Notchset tells them in four ways, starting with the one that needs no setup at all.

Rules for your agent (opt-in)

Installing a component never writes agent files into your project. When you want your agent to know Notchset, add the rules once: .notchset/AGENTS.md (library rules and a routing table of every component with its install command) and .cursor/rules/notchset.mdc pointing Cursor at it.

npx shadcn@latest add https://notchset.dev/r/notchset-ai.json

Claude Code: add one line to your CLAUDE.md so it always reads the rules:

@.notchset/AGENTS.md

Every component's page also has a Markdown version for agents at /md/<id>.md (for example https://notchset.dev/md/button.md), and https://notchset.dev/llms.txt lists them all.

MCP server

The server exposes search_components, get_component, list_components, get_setup, and, once you sign in, get_pro_source and get_profile. Results include when to use each item, and when not to, so the agent picks the right one. get_component takes build: "base" or "radix" to match your components.json style, and returns that build's install command, file paths, npm and registry dependencies and tokens. Free items also come with their source and CSS. The install command itself brings everything, so agents should install rather than copy source.

claude mcp add --transport http notchset https://notchset.dev/api/mcp

{
  "mcpServers": {
    "notchset": {
      "url": "https://notchset.dev/api/mcp",
      "headers": { "Authorization": "Bearer ${NOTCHSET_TOKEN}" }
    }
  }
}

The Authorization header is optional. With a Pro key, get_component also returns the source and CSS of the Pro items your plan covers.

Sign in from Claude and ChatGPT

You don't need to paste a key. Add the server URL below, and searching and docs work right away. When you ask for a Pro item's source, the app asks you to sign in to Notchset. After you approve, it gets the Pro source your plan covers. The connection is read only. It shows up as an MCP key in your account, and you can revoke it there at any time.

https://notchset.dev/api/mcp

• Claude (web, Desktop, mobile): Settings → Connectors → Add custom connector, then paste the URL.
• ChatGPT: Settings → Apps & Connectors → Create (developer mode), then paste the URL and choose OAuth.
• Claude Code: run the command above, then /mcp to sign in.

The connection uses standard MCP authorization (OAuth 2.1 with PKCE). Registration happens on its own, through Client ID Metadata Documents or Dynamic Client Registration, so other MCP clients that support sign-in can connect too.

Agent skill

The skill teaches Claude Code and compatible agents the workflow and the design, motion and copy rules, plus a review checklist they run before handing work back.

npx shadcn@latest add https://notchset.dev/r/notchset-skill.json

It installs into .claude/skills/notchset/ in your project, so everyone on the team gets it.

llms.txt

For tools without MCP, point them at plain text:

• /llms.txt: setup plus every item with a one-line description
• /llms-full.txt: full docs for every item in one file
• /md/<id>.md: one item's agent guide, including source and CSS for free items

A good first prompt

Add a Notchset Run Button and Data Table to our agent runs page, wired
to our runs API. Read their docs at notchset.dev first and keep
the phone layout working.