Catch drift in the pull request, the Figma file and the agent.

Every integration reads the same tokens from your repo, so a value gets the same answer everywhere.

Install on GitHub

GitHub App

The core. It scans your repos and comments on pull requests.

  • Scans on install, on every push to your default branch and on every pull request.
  • One comment per pull request, updated on each push, about only what it changed.
  • Fix pull requests for exact matches when you tick the box. It never pushes to your branches.
  • Reads code, Code Connect files and your deployed Storybook. Never builds or runs your code.
The Paritrix comment on a pull request: token adoption, six hardcoded values with suggested tokens, a fix checkbox and components in sync

Figma plugin

Drift starts in the file too. See it where designers work, and in Dev Mode.

Coming to Figma Community

Paritrix Lint in Figma: 96% of values bound to variables, with unbound fills, unbound numbers and a detached instance listed

Lint

Values not bound to a variable and detached instances; click a row to jump to the layer. No account needed.

Paritrix Code drift in Figma: the Button component drifts in paritrix-demo because its Danger variant has no matching prop value

Code drift

Every repo that ships the selected component: in sync or drifting, and why.

Paritrix in Figma Dev Mode: the ProductCard component to use and the repo token for each fill, padding, gap and radius

Dev Mode

The code component to use and the repo token for each fill and size.

It reports in Figma; fixes happen in code. Code drift and Dev Mode use an API token.

MCP connector

Claude Code and Codex

The agent uses your tokens while it writes, before any pull request exists.

Remote: your repos' health, component drift and tokens from paritrix.com. Add it by URL, then sign in with GitHub in the browser; no token to paste.

Claude on claude.ai using the Paritrix connector: paritrix-demo's health is 46%, fix the Button drift first, then the 16 exact token matches

Claude Code, remote

claude mcp add --transport http paritrix https://paritrix.com/api/mcp

Then type /mcp, pick paritrix, Authenticate. Your browser opens paritrix.com: sign in with GitHub, Allow.

Claude on the web and desktop

Settings, Connectors, Add custom connector, then paste

https://paritrix.com/api/mcp

Then Connect. Also listed in the Claude directory.

Codex, ~/.codex/config.toml

[mcp_servers.paritrix]
url = "https://paritrix.com/api/mcp"

Then codex mcp login paritrix.

Local, no account, on npm

claude mcp add paritrix-local -- npx -y @paritrix/mcp

Nothing leaves your machine. Reads paritrix.config.json in your repo.

  • check_code
  • check_file
  • suggest_token
  • list_tokens
  • design_rules
  • repo_health
  • component_drift

Slack digest

A Monday reminder for the channel that owns the design system.

  • Health per repo with the week's change.
  • Pull requests scanned and the hardcoded values they added, with the AI-assisted share.
  • Safe fixes waiting, with links to the report and the repos.

Settings, Automation: paste a Slack incoming-webhook URL and tick Send every Monday, or send a test digest now.

The Paritrix weekly digest in a Slack channel: health per repo with the week's change, pull requests scanned, the AI-assisted share and safe fixes waiting

Sign-in and API tokens

Connectors sign in with GitHub and appear in Settings, Connected apps, where you can revoke them. The Figma plugin's code drift and Dev Mode use a personal API token from Settings, API tokens: shown once, revocable, expires after 90 days, limited to the repos you can see.

Sign in

Get your first health score today.

Install on GitHub