Platform MCP Docs

MCP Client Configuration

Configure the canonical endpoint with placeholder-only credentials and current transport headers.

Version MCP 2025-11-25 Current Streamable HTTP contract with compatibility versions Reviewed Jul 26, 2026 Next review Oct 26, 2026

Start Reading Report documentation issue Try in a Free Developer Workspace

The free Developer workspace is for non-production building and learning under published limits. External API or MCP client credentials use a separate scoped request and approval process.

Owner: Batoi Developer Experience Reviewed by: Batoi Platform Security Source revision: upgrade-jul-26-2026

On this page

MCP Client Configuration

The exact client file format varies. Configure these logical values:

{
  "name": "Batoi Platform",
  "transport": "streamable-http",
  "url": "https://batoi.com/mcp/<workspace>/",
  "headers": {
    "Authorization": "Bearer <host-credential>",
    "Accept": "application/json, text/event-stream"
  }
}

Rules

Replace <workspace> with the approved workspace UID or slug.
Keep the bearer value in the client's secure credential facility, not in a shared configuration file.
Use the canonical endpoint for new connections.
Preserve MCP-Protocol-Version and MCP-Session-Id headers after initialization.
Do not add arbitrary downstream URLs, workspace selectors, or connector credentials.

Browser clients

Browser-origin requests are allowed only from the configured same origin or an explicit server allowlist. A wildcard origin is not supported for authenticated MCP access.