Cursor | Stoaken Integrations

What it does

Cursor's agent reads your Brands and tokens, exports them as code and proposes token changes for a person to approve. The tools are listed at /docs/mcp.

Before you start

A Stoaken account with at least Viewer on a Brand. On the Free plan agents are read only.
Cursor desktop.
Optional: an API key from Settings > API keys.

Setup

npx stoaken init --client cursor

This writes .cursor/mcp.json, keeping any other servers. Then open Cursor Settings > MCP, enable stoaken and click Connect to sign in. Cursor registers itself with Stoaken's sign-in automatically (dynamic client registration with PKCE).

Configuration

.cursor/mcp.json (project) or ~/.cursor/mcp.json (all projects). No secret, safe to commit:

{
  "mcpServers": {
    "stoaken": { "url": "https://www.stoaken.com/mcp" }
  }
}

With an API key instead of the browser sign-in:

{
  "mcpServers": {
    "stoaken": {
      "url": "https://www.stoaken.com/mcp",
      "headers": { "Authorization": "Bearer ${env:STOAKEN_API_KEY}" }
    }
  }
}

Set STOAKEN_API_KEY in your shell profile; envFile isn't supported for remote servers.

Try it

"Using Stoaken, export the Default theme as CSS into src/styles/tokens.css."
"Which Stoaken tokens are deprecated, and where does this repo still use them?"

Troubleshooting

Red dot / no tools: open Settings > MCP and check the server's log; click Connect again.
401 with an API key: Cursor didn't see STOAKEN_API_KEY. Set it system-wide and restart Cursor.
Edited the file but nothing changed: toggle the server off and on in Settings > MCP.

Limits

No tool approves or publishes a release.
Writes count towards a per-key limit; Free plan is read only.