CLI

Bridge an MCP client that only speaks stdio to your Breno workspace with the CLI's serve mcp command and a scoped token.

Report a problem with this page

The Breno CLI (in the repository at apps/cli, built as the brainers binary) can run a local MCP server over stdio that forwards every request to your Breno endpoint with your token. Use it for clients that can launch a program but cannot connect to a remote server.

Configure#

The bridge needs a token and an endpoint:

Setting	Flag	Environment variable
Token	`--token`	`BRENO_MCP_TOKEN`
Endpoint	`--url`	`BRENO_MCP_URL`

The token must start with sirmx_mcp_; the command refuses anything else and tells you to create one in Connect AI. The endpoint defaults to your profile's API address followed by /mcp/external. Override it with --url, for example https://<your-breno-host>/mcp.

Run it#

Start the bridge

export BRENO_MCP_TOKEN=sirmx_mcp_…
brainers serve mcp

Add it to a client#

Most stdio clients take a command, arguments and environment in a JSON file:

A stdio client's server entry

{
  "mcpServers": {
    "breno": {
      "command": "brainers",
      "args": ["serve", "mcp"],
      "env": { "BRENO_MCP_TOKEN": "sirmx_mcp_…" }
    }
  }
}

Restart the client. The nine tools appear as they would over the remote endpoint. See MCP server.

Good to know#

The bridge adds nothing: your token's scopes and access are exactly what they are on the remote endpoint.
Revoke the token in Connect AI and the bridge stops working at once.
Logs go to standard error, so they never mix with the protocol stream.