Client Command Reference

BuilderStudio does not ship a dedicated CLI. You connect existingMCP clients — Claude Code, Cursor, or Codex — to the workspace MCP gateway over Streamable HTTP. Every client uses the same endpoint and the same bearer key, so the only thing that changes between clients is how each one stores the connection. Create the key first in Dashboard setup, then register it below.

1Server name: builderstudio2Endpoint:    https://builder.studio/api/mcp3Transport:   Streamable HTTP4Auth header: Authorization: Bearer builder_YOUR_KEY_HERE

Claude Code

Add BuilderStudio as an HTTP MCP server. The header carries your workspace key:

1claude mcp add --transport http builderstudio "https://builder.studio/api/mcp" \2  --header "Authorization: Bearer builder_YOUR_KEY_HERE"

Cursor

Add the server to .cursor/mcp.json in your project (or the global Cursor config). Cursor sends the headers block on every request:

1{2  "mcpServers": {3    "builderstudio": {4      "url": "https://builder.studio/api/mcp",5      "headers": {6        "Authorization": "Bearer builder_YOUR_KEY_HERE"7      }8    }9  }10}

Codex

Codex reads the bearer token from an environment variable for Streamable HTTP servers, so the raw key never lands in your Codex config file. Export it, then register the server pointing at that variable:

1export BUILDERSTUDIO_API_KEY="builder_YOUR_KEY_HERE"2codex mcp add builderstudio \3  --url "https://builder.studio/api/mcp" \4  --bearer-token-env-var BUILDERSTUDIO_API_KEY

If you prefer editing config directly, the same connection in Codex's TOML config looks like this:

1[mcp_servers.builderstudio]2url = "https://builder.studio/api/mcp"3bearer_token_env_var = "BUILDERSTUDIO_API_KEY"

After connecting

1. 1

   Restart the client

   Restart Claude Code, Cursor, or Codex after adding the server. The BuilderStudio tools should then appear in the client's MCP tool list.

2. 2

   Confirm the tools loaded

   Ask the agent to list your BuilderStudio canvases. A successful list_canvases call confirms the endpoint, key, and scopes are wired up. See the full surface in the Visual tool map.

3. 3

   Point the agent at real work

   Reference BuilderStudio by name and name the target workflow, for example: “Use the BuilderStudio workspace to find the launch-image workflow, run it with this brief, and return the generated image URL.”