What it does
While Bolt builds, it can read your Brands and tokens and export them as code, so the app uses your real tokens. It can also propose 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 bolt.new account.
Setup
Bolt adds MCP servers in its own UI; there is no project file. npx stoaken init --client bolt just prints these steps.
- From the Bolt homepage chatbox: + > Connectors > Manage connectors.
- Custom MCP server. Name
Stoaken, URLhttps://www.stoaken.com/mcp, Transport type HTTP. - Authentication: MCP OAuth, then Connect and sign in.
- In a project: + > Connectors and turn Stoaken on.
Configuration
Nothing to write. Bolt turns every tool on by default; in the connector's Edit screen turn off the propose_* tools if this project should only read tokens. Tool choices apply to all projects.
Try it
- "Using Stoaken, get the resolved tokens for the Default theme and style this page with them."
- "Export my Default theme as Tailwind 4 and use it in this project."
Troubleshooting
- Offline: connector > Edit > Refresh connection.
- API key instead of OAuth: Bolt's docs don't say which header its API key option sends; Stoaken needs
Authorization: Bearer. Use MCP OAuth.
Limits
- No tool approves or publishes a release.
- Each enabled connector adds context and token use; turn Stoaken off in projects that don't need it.
- The connector is for Bolt while it builds, not the app it builds; export the tokens into the app's code.