Skip to content

Connect Cavaridge to ChatGPT

ChatGPT (OpenAI) supports MCP via custom connectors. The setup is similar to Claude — pick the Cavaridge product surface(s) you want, OAuth in, done.

  • ChatGPT Plus/Pro/Team/Enterprise (custom connectors require a paid tier)
  • Cavaridge tenant + account
  • Permission to create OAuth clients (MSP Admin, Platform Admin, or Individual Owner)
  1. In ChatGPT, open Settings → Connectors → Add custom connector (the menu names move; ChatGPT releases iterate quickly).
  2. Server URL: choose your product surface. Examples:
    • https://mcp.cavaridge.app/forge — Cavaridge AI tools
    • https://mcp.cavaridge.app/cavalier — Cavaridge Operations (quotes, deals)
    • https://mcp.cavaridge.app/aegis — Cavaridge AEGIS (posture, findings)
  3. Auth: OAuth 2.1 with PKCE.
  4. Authorize URL: https://auth.cavaridge.app/oauth/authorize
  5. Token URL: https://auth.cavaridge.app/oauth/token
  6. Scopes: minimum sufficient for your use case.

ChatGPT opens the Cavaridge consent page. Sign in, review scopes, Allow.

In ChatGPT, ask:

Draft a quote for ContosoCare with one Operations Pro seat

ChatGPT calls cavalier.create_quote. Because that’s a destructive tool, Cavaridge returns confirmation_required — ChatGPT shows you the proposed quote contents and waits for your confirmation. Approve, and ChatGPT re-invokes with confirmed: true.

  • ChatGPT prefers richer tool schemas with description blocks per parameter. Cavaridge’s tool catalog includes those by default.
  • ChatGPT’s connector UI is more aggressive about asking for confirmation on every destructive call — the same envelope works, the UI just amplifies it.
  • ChatGPT can connect to multiple servers concurrently; the audit log in the Cavaridge portal aggregates across all of them.

Same as Claude:

Same as Claude. Every call audit-logged. Destructive tools require confirmation. Cross-tenant calls rejected. Revocation is immediate.