Install the Claude communication channel with Builder CLI. Builder validates Runtime MCP and OAuth discovery, then leaves only Anthropic-owned add, authenticate, and enable steps.
Users state a business goal in Claude. AI Fabrix Role Assistants return a governed result, question, or completed outcome. Claude does not execute enterprise work or grant authority. See Conversation-first work and Assistant channels.
Prerequisites
- Deliver assistant channels hub read
aifabrix loginand developer workstation ready- Claude workspace Owner available for Team or Enterprise (Owners add the connector; members authenticate)
- External Access Claude profile enabled (
miso-claude) - Runtime MCP reachable from the public internet so Claude can discover OAuth
Where it lives
| Artifact | Location |
|---|---|
| OAuth2 profile | Controller External Access → OAuth2 profiles → Claude |
| Stable profile URL | /miso/external-access/oauth2-profiles/miso-claude |
| First-run output | Terminal values for the Claude connector form (Name, Server URL, OAuth) |
| Channel package | Builder output under dist/channels/claude/ after channel add (INSTALL guide) |
| Secrets | OAuth discovered from Runtime — no static Claude API key in the package |
Claude.ai, Claude Desktop, Cowork, and mobile use the same account-level custom connector. One Claude channel install serves many Role Assistants. See External AI and Enterprise MCP.
How to set
aifabrix channel add claude --name "Onni"
If Runtime or OAuth discovery is not ready, Builder reports Not ready and a blocker. Open the Claude OAuth2 profile (/miso/external-access/oauth2-profiles/miso-claude): enable it, and confirm CIMD is advertised when discovery supports it. Then run the same command again. When ready, Builder prints:
- Claude connectors URL:
https://claude.ai/settings/connectors - Name
- Description
- Server URL
- Authentication: OAuth
Add a custom connector in Claude with those values. Leave Client ID and secret empty when discovery advertises CIMD. Do not paste a static API key.
Remaining Claude-owned steps:
- Add the custom connector (Owners for Team or Enterprise).
- Authenticate.
- Enable the connector.
If Claude shows a callback URL that is not already registered:
aifabrix channel configure claude --callback-url "<callback-url>"
The hosted callback is https://claude.ai/api/mcp/auth_callback. Admin completes Connect assistant channels after the connector is enabled.
Defaults and examples
| Setting | Typical value |
|---|---|
| Target key | claude |
--name |
Customer-visible brand (for example Onni) |
| Server URL | Runtime MCP URL from Builder |
| Authentication | OAuth discovered from Runtime — CIMD preferred |
| OAuth2 profile | /miso/external-access/oauth2-profiles/miso-claude (miso-claude) |
| Hosted callback | https://claude.ai/api/mcp/auth_callback |
| Surfaces | Claude.ai, Claude Desktop, Cowork, and mobile share the account connector |
| Product law | One Claude channel install per environment; many Role Assistants |
Do not paste a static API key or write a local desktop MCP file for this remote connector. Builder prints the live values; copy them into Claude connectors.
Validate
aifabrix channel add claude --name "Onni" --probe
A successful AI Fabrix probe does not replace Claude's own add, authenticate, and enable steps. If the probe reports not ready, fix Runtime MCP and the Claude OAuth2 profile before opening Claude connectors.
Common mistakes
| Mistake | Fix |
|---|---|
| Claude profile disabled | Enable Claude at /miso/external-access/oauth2-profiles/miso-claude |
| Non-Owner on Team or Enterprise | An Owner must add the custom connector; members then authenticate and enable it |
| Pasting a static API key into Claude | Use OAuth so Claude discovers the authorization server |
| Filling Client ID and secret by hand | Activate CIMD so discovery advertises it |
Writing claude_desktop_config.json for remote MCP |
Hosted Claude surfaces use the account connector, not a local desktop file |
| Localhost MCP URL | Claude connects from Anthropic cloud; the Runtime MCP URL must be public HTTPS |
| One connector per Assistant | Single channel; many Assistants |
| Opening Claude connectors while Runtime is not ready | Re-run channel add until Builder reports ready |
Limits
Claude add, authenticate, and enable remain Anthropic-owned steps until Anthropic documents a provisioning API. Treat Claude as another channel into the same Operational Trust boundary — not a bypass around Role Assistants.