Borealis Docs

Connect agents through MCP

The hosted MCP service lets compatible clients discover and call Borealis tools through the public product boundary.

Connect a client

Use a client that supports remote Streamable HTTP MCP and OAuth discovery.

  1. Add a remote MCP server with URL https://mcp.borealishq.io/mcp.
  2. Start the client’s connection flow and follow the Borealis sign-in and consent screens.
  3. Select the appropriate organisation context and inspect the tools available to your account.
  4. Start with a read operation, such as context_get or sandbox_list, before requesting mutations.

Client configuration formats differ, so use your client’s remote-server setup rather than a configuration snippet for another product.

Use the correct credentials

MCP has its own OAuth audience and uses the borealis.mcp scope. Its identity issuer is https://identity.borealishq.io. Let the client’s discovery and authorisation flow obtain the correct credential.

Do not paste an API access token into the MCP connection and assume it will work. Tool access still depends on the underlying operation’s permissions and organisation context.

Give the agent a clear task

Specify which sandbox it should use, what it may change, and when it should stop. Useful tools include sandbox_get, sandbox_create, sandbox_exec_start, and snapshot_create.

Ask the client to inspect operation results and follow progress. A tool response that accepts a request does not mean the sandbox is running or an execution has succeeded.

Confirm destructive work

Deletion and other destructive tools use a preflight confirmation flow. Read the affected resource and intended action before approving it. Do not configure a general-purpose agent to approve all destructive requests automatically.

Workspace transfers use resource or upload handles and dedicated streaming paths. They do not require the model to carry an entire archive as base64 text. See workspace transfers.

If tools are missing or calls are forbidden, check the client’s token, organisation context, and permissions using authentication.