/mcp/v1 on your Breakcold API base URL. It uses Streamable HTTP and exposes tools generated from the same public API contract as OpenAPI.
For application-specific setup, open the Applications hub.
For authentication details, open MCP authentication.
MCP URL
Use this MCP URL for every workspace./mcp/v1 URL as a protected resource for MCP clients. Enable client metadata document support, and keep dynamic client registration enabled when you need compatibility with older MCP clients.
Use OAuth when the MCP client supports sign-in. OAuth calls run as the signed-in Breakcold user and still enforce organization, workspace, and record-level permissions.
Use a bearer token only for MCP clients that cannot complete OAuth or for service-style agents that should not act as a signed-in user. Bearer tokens use the scopes and workspace limits configured in Breakcold.
For user sign-in applications managed by Breakcold, MCP clients should send X-Breakcold-Organization-Id unless the user belongs to exactly one active Breakcold organization. Tool calls still enforce workspace permissions from the workspace or record ids passed to the tool.