Skip to main content
Humic ships a built-in MCP connector for Claude. Once connected, you can ask Claude to read, edit, export, and publish your design tokens — on Claude web, desktop, mobile, and in Claude Code. Setup takes about a minute: paste one URL, sign in, click Authorize. That’s the whole thing.
You don’t need to install anything. The connector runs on Humic’s servers — there is no package, download, or configuration file involved.

​
Before you start

  • A Humic account that’s a member of at least one design system.
  • Claude — a paid plan (Pro or higher) for custom connectors on claude.ai and Claude Desktop, or Claude Code in your terminal.

​
Step 1 — Copy your connector URL

Open Humic, go to Settings → Connect to Claude, and copy the URL shown there:
That URL is the same for everyone — it’s your sign-in that decides what Claude can see.

​
Step 2 — Add it to Claude

  1. Open Claude and go to Settings → Connectors.
  2. Click Add custom connector.
  3. Paste the URL from Step 1 and click Add.
  4. Claude opens a browser window to Humic — continue to Step 3.

​
Step 3 — Sign in and authorize

A browser window opens with Humic’s sign-in page:
  1. Sign in with your email — the same one-time code flow you use for the Humic dashboard.
  2. Click Authorize.
Done. Claude is now connected to your Humic account. No tokens to paste, no keys to manage.
Try it right away — ask Claude:
  • “List my Humic design systems”
  • “Show me the color tokens in Acme”
  • “Create a token color.brand.primary that references {color.blue.500}”
  • “What’s changed since the last published version of Acme?”
  • “Export Acme as Tailwind”

​
What Claude can do

Claude acts as you — it sees exactly the design systems you’re a member of, with your role. If you’re a viewer, Claude can read but not edit. Everything it changes shows up live in the Humic dashboard. Some things are deliberately not available through Claude and stay in the dashboard: managing members and roles, generating or revoking API keys, approving access requests, and organization settings. Those are decisions we keep in human hands.

​
Disconnecting

Go to Settings → Connect to Claude in Humic. Under Connected apps you’ll see every AI client you’ve authorized — click Disconnect to revoke its access immediately. You can reconnect any time by authorizing again.

​
Troubleshooting

Custom connectors require a paid Claude plan. On Claude for Work (Team/Enterprise), an admin may need to enable custom connectors for your organization first. On mobile, connectors can’t be added directly — add Humic on claude.ai or Claude Desktop and it syncs to your phone.
Claude sees the design systems of the Humic account you authorized with. If you signed in with a different email than usual, disconnect (in Claude: Settings → Connectors → Remove; in Humic: Connected apps → Disconnect) and connect again with the right account. Also check that you’re actually a member of the design system in Humic.
Your Humic role applies to Claude too. Viewers are read-only — ask a design system admin to make you an editor if you need Claude to make changes.
The sign-in happens on humic.dev and needs cookies. If your browser blocks third-party cookies aggressively or you’re in a private window, open the authorization link in a regular window and try again.
Someone may have clicked Disconnect in Humic, which revokes access for that client. Just add the connector again — it’s the same one-minute flow.

​
Using a different AI client?

The connector is standard MCP over Streamable HTTP with OAuth, so any MCP client that supports remote servers can use the same URL: https://humic.dev/api/mcp. For coding agents without MCP support, see AI Agents for the CLI-based workflow.