Connect an agent to HumanDesign.ai.
The canonical remote Streamable HTTP endpoint is https://mcp.humandesign.ai/. OAuth connects private account tools; API keys preserve the calculation/reference API surface.
Membership rule: Free and Individual HumanDesign.ai users can create, save, view, and render their own primary chart; Individual also sees account usage. Personal or Pro is required to read other people's authorized charts or use wider account features. Website Builder tools appear only when HumanDesign.ai has enabled the Builder for your account, and only when tools/list advertises them.
Choose an access surface
OAuth platform tools →
19 currently exposed account, chart-rendering, library, operation, report-status, and Builder tools.
API-key calculation tools →
6 calculation/reference tools governed by the separate API plan and calculation quota.
Protocol surface
The server accepts JSON-RPC over HTTP POST at the domain root. GET and DELETE are intentionally rejected for the MCP transport; GET /health exposes only safe service health metadata.
Canonical endpoint
POST https://mcp.humandesign.ai/
Content-Type: application/json
Accept: application/json, text/event-streamSupported methods
initializeConnection or discovery method; it does not consume quota or AI credits.
notifications/initializedConnection or discovery method; it does not consume quota or AI credits.
pingConnection or discovery method; it does not consume quota or AI credits.
tools/listConnection or discovery method; it does not consume quota or AI credits.
tools/callExecutes an authorized tool according to its billing and confirmation policy.
Birth times are local wall clock times
Send the birth date and time as it read on the clock where the person was born, with no Z and no UTC offset, and give the timezone separately as an IANA identifier.
"birthDateTime": "1990-05-15T14:30:00" with "timezone": "America/New_York" means half past two in the afternoon in New York.
A value carrying Z or an offset does not name a wall clock time on its own. Something has to decide which zone to read it in, and that decision changes the chart.
Z and UTC offsets are deprecated. Values ending in Z or a numeric offset are deprecated. The MCP forwards them and the API still accepts them for now, reading them as UTC, and the deprecation is announced on the API response. They will stop being accepted, and the date will be announced in advance.
A wall clock time that names no single moment is refused by the API before any calculation unit is used:
| Error code | When it is returned |
|---|---|
nonexistent_local_time | A daylight-saving change skipped that wall time, so it never happened in that zone. |
ambiguous_local_time | The wall time falls inside a daylight-saving fold, so it happened twice in that zone. |
future_birth_datetime | The birth time is in the future. |
invalid_birth_datetime_format | The value is not a wall clock time. After the cutover this covers Z and numeric offsets too. |
Transit dates use the same wall clock format but may be in the future.
Start here
Getting started →
Connect through OAuth and make a safe first request.
Membership and permissions →
Understand capability grants, workspaces, ownership, and confirmations.
Claude, ChatGPT & Codex →
Download setup files and the dual-format plugin package.
Authentication →
Choose OAuth or calculation-only API-key access.