MCP | Fragments

Local, in the loop

npx @usefragments/cli mcp --stdio

Zero network. It reads the manifest and the compiled rules the hooks use.

Local MCP tools
Tool	Ask	Answer
`search`	"three stats in a row"	StatStrip pattern with its shape and exemplar
`get`	Button	intents, members, props, do, dont, exemplar
`check`	a file path or source	findings for it, same engine as the save hook
`tokens`	color accent	the tokens matching, with the prefix

Add it to Claude Code with claude mcp add fragments -- npx @usefragments/cli mcp --stdio, or to Cursor in .cursor/mcp.json. init offers both.

Hosted, at the gate

https://app.usefragments.com/api/mcp with OAuth. It serves the pinned contract of a bound repository to agents that do not have the checkout: design_system/list_primitives, list_tokens, conform, prove_compliant. prove_compliant runs the check, applies deterministic repairs, and checks again until clean or until it reports what it could not repair.

Next steps

The loopWire the local server from init.
AgentsWhat each editor hook sends and receives.
The gateThe hosted endpoint serves a bound repository.