Claude Desktop & Claude.ai

Both Claude Desktop and Claude.ai (Pro / Team / Enterprise) support MCP. Wire up AssureAgent once — Vibe answers from the same conversation window you’re already using.

Prerequisites

A personal AssureAgent API key. Mint one from the portal: Settings → API Keys → Create key. Starts with aa_live_.
Either Claude Desktop (Mac / Windows) or a Claude.ai plan that supports Custom connectors (Pro, Team, or Enterprise).

Open the Claude Desktop config file:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json

Add AssureAgent under mcpServers:

{
  "mcpServers": {
    "assureagent": {
      "type": "http",
      "url": "https://mcp.assureagent.ai/mcp",
      "headers": {
        "Authorization": "Bearer aa_live_YOUR_KEY"
      }
    }
  }
}

Restart Claude Desktop. Open any conversation and type:

Ask my QA developer what projects I have.

Claude picks up the new server and calls list_projects on AssureAgent.

In Claude.ai, open Settings → Connectors → Custom connector → Add connector.
Fill in:
- Name: AssureAgent
- URL: https://mcp.assureagent.ai/mcp
- Auth header: Authorization: Bearer aa_live_YOUR_KEY
Save. In any chat, enable the AssureAgent connector for that session, then ask something like:

Ask my QA developer to summarise this week’s failed runs.

What Claude can do

Same tools as Claude Code — see the Claude Code page for the full inventory:

talk_to_vibe — primary conversational tool.
poll_conversation — async companion.
list_projects, list_recent_runs, list_scenarios — deterministic reads.

Where these conversations appear in the portal

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

Troubleshooting

Claude Desktop doesn’t see the server — check the JSON is valid (no trailing commas, proper quotes). The config is only read at startup; restart Claude Desktop after every edit.

Custom connector shows “Not connected” — the URL must be https://mcp.assureagent.ai/mcp exactly (with the trailing /mcp). Double-check the API key hasn’t been rotated.

Response says “invalid or revoked api key” — mint a new key from the portal and update the connector config.