Recon ships an MCP server at https://askrecon.com/api/mcp. Both Claude Desktop and claude.ai (web) support MCP through the same Custom Connector flow. Set it up once on either; the connector follows your Claude account, so the other surface picks it up automatically.
1. Open Custom Connectors
In Claude (Desktop or web), open Settings → Connectors. Scroll to the bottom and click Add Custom Connector.
- Web direct link: claude.ai/settings/connectors
- Desktop URL scheme:
claude://settings/connectors
2. Add the Recon connector
Fill in the connector dialog:
- Name: Recon (or anything you prefer)
- URL:
https://askrecon.com/api/mcp
Submit, then follow the OAuth prompt in your browser. Sign in with your Recon account. Claude will request workspace-scoped read access to your customer memory.
3. Verify
Open a new Claude chat (on either Desktop or claude.ai) and type:
List the accounts in my Recon workspace, ranked by risk.
Claude will call Recon's list_accounts tool and return a ranked list with memory_state and risk scores. From here, ask about any specific customer:
What's happening with Acme this week?
Claude calls get_account and reads back a brief with active claims, recent observations, and source citations.
Desktop and Web behavior
Custom Connectors are tied to your Claude account. Add Recon on either surface and:
- Same chat history, same connector availability across Desktop and Web.
- OAuth tokens are scoped per-account; revoking from Settings → Connectors revokes from both surfaces.
- Tool calls run server-side, so the surface you're chatting from doesn't change what Recon returns.
How it works
Claude speaks Streamable HTTP MCP. When you ask a question, Claude decides which Recon tool to call (get_account, list_accounts, search, impact, themes, or theme_evidence), gets back structured JSON, and writes the answer. Recon never sees your Claude prompts and Claude never modifies your data. All six tools are read-only.
Troubleshooting
- OAuth fails or hangs: check that your Recon workspace is active and that you signed in with the same account that owns the workspace. Try the OAuth flow in a fresh browser tab to clear stale cookies.
- No data comes back: free-tier workspaces only have data after the initial discovery completes. Confirm discovery finished from your Recon dashboard.
- Connector appears on one surface but not the other: force-refresh on the missing surface (Cmd+Shift+R on web, restart the Desktop app). Connector lists are cached per session.
- Connector disappears after a Desktop update: Claude Desktop sometimes loses custom connectors during major updates. Re-add via Settings → Connectors.