How to add Quarzo MCP
Add Quarzo as an MCP connection using Streamable HTTP and OAuth. Do not enter an OAuth client ID or client secret. Use aggregate /mcp unless you are testing a role-specific QA connection.
With QA integration disabled, /mcp exposes only tools associated with roles in the signed-in account. An account carrying multiple roles receives their combined tool surface. With QA integration enabled, /mcp exposes every role tool plus QA tools. The backend remains the authoritative authorization layer.
Connection values
| Name | Description | Server URL |
|---|---|---|
| Quarzo Life MCP | Manage Quarzo Life operations and insurance workflows. | https://mcp-development-300d.up.railway.app/mcp |
When QA_INTEGRATION=true on MCP deployment, these additional connections are available. They expose shared tools plus tools associated with named role and require signed-in account to carry that role.
| Name | Server URL |
|---|---|
| Quarzo Life Broker MCP | https://mcp-development-300d.up.railway.app/mcp/broker |
| Quarzo Life Subscriber MCP | https://mcp-development-300d.up.railway.app/mcp/subscriber |
| Quarzo Life Insurer MCP | https://mcp-development-300d.up.railway.app/mcp/insurer |
When QA integration is disabled, role-specific URLs are not registered and return 404.
ChatGPT
- Open Settings → Security and login and enable Developer mode.
- Open Plugins, then select +.
- Fill the form:
- Name: copy the name from the table.
- Description: copy the description from the table.
- Connection: select Server URL, then copy the server URL.
- Authentication: select OAuth.
- Leave Advanced OAuth settings unchanged.
- Accept the custom MCP warning and select Create.
- Select Sign in, then complete the Quarzo Zitadel login.
Claude
- Open Customize → Connectors.
- Select + → Add custom connector.
- Enter chosen server URL. If Claude asks for a name, copy it from matching table row.
- Leave the OAuth client ID and client secret empty.
- Select Add, then Connect and complete the Quarzo Zitadel login.
On Team or Enterprise, an owner must first add the URL under Organization settings → Connectors → Add → Custom → Web.
Claude Code
claude mcp add --transport http quarzo-life https://mcp-development-300d.up.railway.app/mcpRestart Claude Code, run /mcp, then authenticate.
Zitadel app redirect URIs
The MCP server uses a fixed Zitadel OAuth application. Its client ID is returned automatically during connection; you do not enter it.
The Zitadel app must be configured with every redirect URI that MCP clients will use. The OAuth flow fails at the invalid_request → redirect_uri missing error when a client's redirect is not on the allow-list.
| Redirect URI | Client |
|---|---|
https://claude.ai/api/mcp/auth_callback | Claude Chat web |
https://chatgpt.com/connector/oauth/session | ChatGPT web |
http://127.0.0.1:*/callback/* | Claude Desktop, Codex, Claude Code |
http://localhost:*/callback/* | Local browser dev |
If the Zitadel app is NATIVE type, it may reject non-loopback (https://...) redirect URIs. Change it to WEB type, or create a second WEB app for browser clients and configure the server with the matching MCP_ZITADEL_CLIENT_ID = "388093223391823928".
Expected result
The connection shows as connected. For aggregate /mcp, signed-in account must carry at least one of broker, insurer, or subscriber roles. For a QA-only role connection, account must carry matching role. Discovered tools follow QA_INTEGRATION behavior described above.
Platform instructions: