MCP JSON-RPC transport

POST/MCPFrom Free

Connect any MCP-compatible client to trusted HumanDesign.ai tools.

The canonical stateless Streamable HTTP endpoint supports initialize, notifications/initialized, ping, tools/list and tools/call using protocol version 2025-11-25. An API key exposes only the tier-filtered six-tool calculation surface; HumanDesign.ai OAuth exposes only account tools permitted by the selected workspace, membership, role, server-derived capability grants, and entitlements.

Authentication

Use Authorization: Bearer YOUR_API_KEY or X-Api-Key. Query-key authentication is deprecated compatibility behavior on supported REST routes and is rejected on Agent HTTP and MCP surfaces. Never put credentials in URLs, request bodies, or browser code.

Parameters

NameInRequiredDescription
AuthorizationheaderYesBearer API key. X-Api-Key is also supported.
Bearer YOUR_API_KEY
jsonrpcbodyYesJSON-RPC protocol version.
2.0
methodbodyYesMCP method name.
tools/list
idbodyNoJSON-RPC request identifier.
1
paramsbodyNoMethod parameters.
{}

Errors

Expect 400 for invalid input, 401 for a missing or malformed key, 403 when the active plan does not include this operation, and 429 when the monthly allowance is exhausted.

Related operations