Use this guide when you are implementing a custom MCP client instead of relying on a first-party integration.
Streamable HTTP baseline
URL: https://mcp.undisk.app/v1/mcp
Auth: Authorization: Bearer sk_live_YOUR_KEY_HERE
WebSocket profile
wss://mcp.undisk.app/ws?token=sk_live_YOUR_KEY_HERE
Request/response implementation tips
- Always send explicit auth headers for HTTP MCP calls.
- Use deterministic request IDs for easier cross-system tracing.
- Add retry handling only for transient failure classes (429/5xx/network timeouts).
- Log workspace routing context with each call.
Choosing transport
- Prefer HTTP for compatibility and predictable gateway behavior.
- Prefer WebSocket for low-latency interactive workloads where long-lived connections are stable.
Coming soon: transport-specific benchmarking guides and client library adapters for common runtimes.
