Zed

What it does

Zed'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.
• Zed with the Agent Panel.
• Optional: an API key from Settings > API keys (user settings only, see below).

Setup

npx stoaken init --client zed

This writes .zed/settings.json, keeping your other settings. Trust the project when Zed asks (in Restricted Mode project settings and their MCP servers don't load). Because the entry has no Authorization header, Zed asks you to sign in with the standard MCP OAuth flow.

You can also add it in Settings > AI > MCP Servers > Add Server > Add Remote Server.

Configuration

.zed/settings.json (project) or your user settings (zed: open settings file). No secret:

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

Zed's docs describe no variable expansion in headers, so with an API key init writes nothing. Add it to your user settings, never the repo:

{
  "context_servers": {
    "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."
• "List my Stoaken Brands and the themes in each."

Troubleshooting

• No green dot: open Settings > AI > MCP Servers; hover the server for the error.
• Nothing loads from .zed/settings.json: the project is in Restricted Mode; click the warning in the title bar and trust it.
• init left the file alone: your settings file has comments. Add the entry by hand.
• Tool calls ask every time: that's agent.tool_permissions; allow mcp:stoaken:<tool> for read tools only.

Limits

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