Recon exposes a standard MCP server. Any client that speaks the protocol can connect. This guide is the generic reference for clients without a dedicated setup page (Hermes, OpenClaw, Continue, Cline, Goose, Raycast, custom integrations).
Server details
- Endpoint:
https://askrecon.com/api/mcp - Transport: Streamable HTTP (the 2025-03-26 MCP revision). SSE is not supported; the spec dropped it and Recon followed.
- Authentication: OAuth 2.0. Resource discovery at
/.well-known/oauth-protected-resourceand authorization server metadata at/.well-known/oauth-authorization-server.
Generic connection steps
- Configure your client to use
https://askrecon.com/api/mcpas an HTTP MCP server. - On first connection, your client will fetch
/.well-known/oauth-protected-resourceand follow the OAuth flow. - Sign in with your Recon account. The grant is workspace-scoped and read-only.
What you get
Six read-only tools:
| Tool | What it does |
|---|---|
get_account | Full memory profile for ONE customer (claims, observations, risk score) |
list_accounts | Ranked list of customers by risk (or recency / claim count) |
search | Full-text search across observations and claims |
impact | Customers affected by a feature, ticket, or code path |
themes | Cross-account claim clusters |
theme_evidence | Source claims behind a theme |
See the MCP tools reference for the input schema of each tool.
Already supports MCP?
If your client passed our compatibility check, it appears in the harness section on the landing page by name. If you're using a client that doesn't appear there, it likely still works as long as it speaks Streamable HTTP MCP with OAuth. Contact us and we'll add it to the list.