bl mcp
Serve the Blaxel MCP server to a coding agent, signed in with your bl login
Synopsis
Serve the hosted Blaxel MCP tools over stdio using your existing bl login.
Run bl login before starting your agent. bl setup configures local MCP targets;
no token is stored in agent configurations and no separate MCP OAuth is needed.
Without a usable login, the connection still initializes, with an empty tool
list and instructions to run bl login, then restart or reconnect the agent.
The default workspace is pinned when the bridge starts resolving credentials:
the current bl workspace, —workspace or BL_WORKSPACE. A tool’s workspace
argument can intentionally select another authorized workspace. This pin is
not a restriction on the user’s authority.
Tokens refresh in memory only. bl logout removes local credentials, affecting
future requests, but does not revoke refresh grants or work already in flight.
BL_API_KEY and BL_CLIENT_CREDENTIALS override stored credentials and are not
removed by bl logout. Environment inheritance varies between agent clients.
The HTTPS origin comes from the stored workspace environment (prod or dev),
not inherited BL_API_URL or BL_ENV. Redirects are refused for both MCP requests
and token exchanges.
Examples
Options
Options inherited from parent commands
SEE ALSO
- bl - Blaxel CLI - manage and deploy AI agents, sandboxes, and resources
Last modified on October 9, 2026
