Cline | Stoaken Integrations

What it does

Cline 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.
The Cline extension (VS Code or another supported editor), or Cline CLI.
Optional: an API key from Settings > API keys.

Setup

Cline keeps MCP servers in its own settings, not in your project, so npx stoaken init --client cline writes nothing and prints these steps.

In the Cline panel click MCP Servers, then the Remote Servers tab.
Server Name stoaken, Server URL https://www.stoaken.com/mcp, Transport Type Streamable HTTP.
Add Server. If it asks you to authenticate, sign in in the browser.

Cline CLI: cline mcp add stoaken https://www.stoaken.com/mcp --transport http --yes, then cline mcp > Authorize OAuth.

Configuration

With an API key, use Configure > Configure MCP Servers to open Cline's settings JSON (it lives in the editor's storage, not the repo):

{
  "mcpServers": {
    "stoaken": {
      "type": "streamableHttp",
      "url": "https://www.stoaken.com/mcp",
      "headers": { "Authorization": "Bearer <API key>" }
    }
  }
}

Set "type": "streamableHttp": without it Cline falls back to the legacy SSE transport. Cline's docs describe no variable expansion here, so the key is stored as written. Keep autoApprove to read tools.

Try it

"Using Stoaken, export the Default theme as CSS into src/styles/tokens.css."
"List my Stoaken Brands."

Troubleshooting

Won't connect: check the transport is Streamable HTTP, not SSE.
Start a sign-in again: delete the server and add it again.
Auth errors with a key: check the Authorization header and that the key isn't revoked.

Limits

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