Generate org charts, MCD/ERD data models, and C4 architecture diagrams — pilot OrgGen AI via MCP.
https://www.orggen.ai/api/mcpHeaders: Authorization, X-Project-Id
Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"ai-orggen-orggen": {
"url": "https://www.orggen.ai/api/mcp"
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Paste an API key, bearer token, or session value from the provider. It is used once to list inventory and discarded after the request.
Bearer token. Generate an API key from https://www.orggen.ai/settings (Pro plan required).
Optional. UUID of the project to operate on. If omitted, the key's stored active_project_id is used — set it once via the set_active_project tool and forget. Override per-call by passing this header.
OrgGen AI is an MCP server for Generate org charts, MCD/ERD data models, and C4 architecture diagrams — pilot OrgGen AI via MCP.. It supports HTTP transport.
Use the generated config in Install. It points your client at the advertised remote endpoint shown on this page.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://www.orggen.ai/api/mcp.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://www.orggen.ai/api/mcp.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://www.orggen.ai/api/mcp.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://www.orggen.ai/api/mcp.
OrgGen AI uses HTTP transport. Endpoint: https://www.orggen.ai/api/mcp.
OrgGen AI inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
OrgGen AI is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.