How do I

Connect an AI tool

Let Claude Code, Cursor or another AI tool read your tokens, export them and propose changes for review, from your project.

Set it up

  1. In your project’s folder, run npx stoaken init in a terminal.
  2. Choose Sign in with browser, or Paste an API key made in Settings › Developer access (API keys).
  3. Pick the Brand this project is for.
  4. Pick your AI tool. The CLI adds Stoaken to that tool’s settings and tells you what to do next there (in Claude Code, type /mcp).
  5. Commit stoaken.config.json. The sign-in stays in .stoaken/credentials.json, which is git-ignored. .stoaken/SKILL.md describes the tools: point your AI tool at it.

Tip: The tool acts as you: it sees only the Brands you see, with your role on each. To add Stoaken to a tool by hand, see the AI agents guide.

What to ask

  • “What themes and modes does Acme have?”
  • “Show me the colour tokens in the Default theme, mode by mode.”
  • “Which tokens are deprecated, and what should I use instead?”
  • “Export the Default theme as Tailwind 4 into src/theme.css.”
  • “Propose raising spacing.lg to 24px as a minor release.” (Editors and up, on the Light or Team plan.)

Not sure? In Claude Code, type /mcp__stoaken__get_started: it lists your Brands, your role and what you can do. Other tools can ask for the get_started tool.

Good to know: A change an agent proposes waits in the Command Center for a person to approve. No agent can approve or publish.

If it’s stuck

  • Stoaken doesn’t accept the key: it may be revoked or mistyped. Make a new one in Settings › Developer access (API keys) and run npx stoaken init again.
  • The CLI says “Your Stoaken sign-in ended.”: run npx stoaken init and sign in again.
  • A change is refused on the Free plan: agents can read and export, but proposing needs the Light or Team plan. See Billing, or make the change in the app.
  • It says you’ve hit the limit: that’s 30 changes an hour for one key. Wait, or ask for all the edits in one go.
  • It says you don’t have the role for that: changing tokens needs Editor on the Brand, webhooks need Brand Admin and members need workspace Admin. Ask a Brand Admin for access (a workspace Admin can see who has which role in Organization > Members).
  • There are no Brands to pick: create one in the app, or ask an Admin to invite you, then run init again. Wrong account? Run init again and choose Sign in with browser (sign out of the other account in the browser first), or Paste an API key from the right account.
  • A proposal went through but nothing changed: it’s waiting for review in the Command Center.

With CLI 0.6.0 or later, npx stoaken status checks the project’s setup and says what to fix. More fixes are in the troubleshooting tables for the CLI and AI agents.

Was this page useful?

Looking for the API, CLI or AI agents? They’re in the developer docs.