JetBrains (Junie, AI Assistant) | Stoaken Integrations

What it does

Junie 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.
A JetBrains IDE with Junie, or Junie CLI (they share the same MCP configuration).
Optional: an API key from Settings > API keys (user file only, see below).

Setup

npx stoaken init --client jetbrains

This writes .junie/mcp/mcp.json in the project, keeping other servers. In the IDE, Settings > Tools > Junie > MCP Settings lists stoaken and its status. In Junie CLI run /mcp, select stoaken, choose Authorize and sign in in the browser.

AI Assistant (not Junie): Settings > Tools > AI Assistant > Model Context Protocol (MCP), add { "mcpServers": { "stoaken": { "url": "https://www.stoaken.com/mcp" } } }. Its docs describe no sign-in or headers for remote servers, so we can't say it authenticates; use Junie.

Configuration

.junie/mcp/mcp.json (project, can be committed) or ~/.junie/mcp/mcp.json (all projects):

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

Junie has no secret storage or variable expansion for MCP configs, so a key would sit in the file as plain text, and with an API key init writes nothing. Put it in your user file, never the repo:

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

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

Authorization required: Junie CLI /mcp > stoaken > Authorize. Sign-in from the IDE plugin isn't documented yet; if it fails, use the API key in your user file.
Status shows an error: hover the status icon in MCP Settings for the message.
Too many tools: Junie uses at most 100 tools across all servers.

Limits

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