All guides

Setup guides · 2 min read

Recon for Cursor

Add Recon to Cursor so your coding assistant has memory of every customer. Edit one config file, restart Cursor.

Cursor reads MCP servers from a JSON config file. Recon plugs in with a few lines.

1. Open the MCP config

Cursor stores MCP configuration at ~/.cursor/mcp.json (global) or .cursor/mcp.json inside any project for project-scoped MCP servers.

If the file doesn't exist yet, create it.

2. Add Recon

Add this entry to mcpServers:

{
  "mcpServers": {
    "recon": {
      "url": "https://askrecon.com/api/mcp",
      "transport": "http"
    }
  }
}

If you already have other MCP servers configured, add recon alongside them inside the mcpServers object.

3. Restart Cursor and authenticate

Restart Cursor. Open any project, then the Cursor command palette → MCP: Authenticate → select recon → follow the OAuth flow in your browser.

4. Use it

In Cursor's chat (Cmd+L), reference Recon directly:

Using Recon, find the customers affected by the export timeout bug
and show me which ones are on Enterprise plans.

Or use it implicitly. Cursor will call Recon tools when it judges that customer context is relevant to your task.

When this shines

  • Debugging customer-reported bugs: Cursor pulls the customer's account memory and the open Linear issues at once.
  • Code review with customer context: "Will changing this function affect any customer?" Cursor uses impact.
  • Migration planning: Use Recon to find a high-volume customer we can safely migrate first.

Start with a snapshot

Connect your first source in under 10 minutes.

Sign up free. No card required. Your AI tools get customer memory the moment discovery finishes.

Start free