Human Design MCP for Claude.
Connect Claude Code or Claude's custom connectors to HumanDesign.ai with browser-based OAuth.
Recommended: connect your HumanDesign.ai account
- Add the canonical remote endpoint
https://mcp.humandesign.ai/without a static API-key header. - Start the client's OAuth login and complete the branded HumanDesign.ai browser flow.
- Review the membership-aware tools returned after reconnect.
Claude OAuth setup
claude mcp add --transport http --scope user human-design-ai https://mcp.humandesign.ai/
claude mcp login human-design-aiProject-file setup
CLAUDE.md does not install the connector. It tells Claude how to use HumanDesign.ai after the separate .mcp.json connection is trusted and authenticated.
- Download .mcp.json and CLAUDE.md into the project root.
- Run
claudein that directory. - If needed, run
/loginto sign Claude Code itself in. - Approve the project-scoped MCP server when prompted.
- Run
/mcpand complete HumanDesign.ai OAuth.
.mcp.json
{
"mcpServers": {
"human-design-ai": {
"type": "http",
"url": "https://mcp.humandesign.ai/"
}
}
}For Claude.ai or Claude Desktop, open Customize → Connectors → Add custom connector, use https://mcp.humandesign.ai/, and select Connect. The downloaded files are not needed for that connector flow.
OAuth visibility follows HumanDesign.ai Free/Individual/Personal/Pro membership and entitlements. API-key visibility follows the separate Free/Creator/Startup/Business API plan. Neither credential type bypasses ownership or quota checks.
Verify the connection
Run tools/list and confirm the catalog matches the account boundary; discovery is free. Ask for “my chart” and verify the client uses chart_get_primary, not a name search. If none exists, ask it to preview chart_generate and confirm only after checking the normalized birth details and one-unit quota estimate. Then request a PNG and confirm either the inline image or its short-lived download link appears. Personal or Pro is required for other people's authorized charts.