Skip to main content
Platform MCP Docs

MCP Quickstart

Initialize a current MCP client, discover scoped capabilities, and make an approved read call.

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

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

Browse Batoi Platform MCP Documentation MCP Quickstart

MCP Quickstart

Register an active AI host for the intended workspace, assign its minimum capability class, approve its policy, and copy its bearer credential into the MCP host's secure credential store.

Initialize

Send JSON-RPC over HTTPS POST. Current clients include both accepted response media types.

curl --request POST "https://batoi.com/mcp/<workspace>/" \
  --header "Content-Type: application/json" \
  --header "Accept: application/json, text/event-stream" \
  --header "Authorization: Bearer <host-credential>" \
  --data '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-11-25",
      "capabilities": {},
      "clientInfo": {"name": "example-client", "version": "1.0"}
    }
  }'

Retain the returned MCP-Session-Id header when the server issues one. Send it with later current-protocol requests.

Discover

Call tools/list and resources/list; do not rely on a static tool inventory. Results are filtered to the registered host.

Invoke

Call an approved read tool with tools/call. Retain the external request ID and the returned workspace session UID for support and evidence.