Skip to content
AssureAgent

ChatGPT

ChatGPT Team and Enterprise plans support custom MCP connectors via the workspace admin’s connector settings. This guide covers the Bearer-token setup — same personal API key you use for Claude Code and Claude Desktop.

Prerequisites

  • ChatGPT Team or Enterprise access with permission to add custom connectors (usually a workspace admin).
  • A personal AssureAgent API key. Mint one from the portal: Settings → API Keys → Create key. Starts with aa_live_.

Setup

  1. In ChatGPT, open your workspace Admin panel → Connectors → Add custom connector.

  2. Choose MCP server as the connector type. Fill in:

    • Name: AssureAgent
    • URL: https://mcp.assureagent.ai/mcp
    • Authentication: Custom header
      • Header name: Authorization
      • Header value: Bearer aa_live_YOUR_KEY

  3. Save the connector. Enable it for the users who need Vibe access (or the whole workspace).

  4. In any chat, prompt ChatGPT:

    Ask my QA developer what projects I have in AssureAgent.

    ChatGPT will call list_projects on the AssureAgent MCP server and summarise the result.

What ChatGPT can do

Same tool set as Claude Code and Claude Desktop — see the Claude Code page for the full inventory:

  • talk_to_vibe — primary conversational tool.
  • poll_conversation — async companion for long-running work.
  • list_projects, list_recent_runs, list_scenarios — deterministic reads.

Because ChatGPT leans on tool schemas more than Claude does, the tool descriptions include canonical example prompts to give the model enough structure without giving up the single-conversation elegance.

Where these conversations appear in the portal

Every message ChatGPT sends to Vibe lands under Manager → AI conversations in the portal, badged ChatGPT. Same monthly turn cap as portal chat.

Coming next: OAuth 2.1 + public marketplace

Right now every user pastes their personal API key into their workspace connector config. That works fine for Team / Enterprise workspaces where the admin manages a shared key set.

The next milestone is OAuth 2.1 for AssureAgent’s MCP server, which unlocks two things:

  • A public listing in the ChatGPT connector marketplace (no workspace-admin config step for users).
  • Per-user consent flow (each ChatGPT user grants AssureAgent access once, mints a token in the background, no key-pasting).

Track progress on the changelog.

Troubleshooting

Connector shows “disconnected” — the header must be exactly Authorization: Bearer aa_live_.... ChatGPT sometimes shows only the first header when displaying the connector, so double-check the raw config.

“invalid or revoked api key” in the tool response — the key you pasted is malformed or has been rotated. Mint a new one from the portal and update the connector.

Long-running work seems stuck — ask ChatGPT to call poll_conversation with the conversation_id from the earlier talk_to_vibe reply.