Setup · ~1 minute

MCP server

Connect Irv to Claude Desktop (or any Model Context Protocol client) so the agent can query your projects directly. Same data the dashboard reads, pulled into Claude's context on demand.

Generate an MCP token

Open /app/account, find the MCP access tokenscard, type a label (e.g. "Claude Desktop"), and click Generate token.

The 64-char hex token is shown once. Copy it now — it can't be retrieved later. (You can always generate a new one.)

Add Irv to Claude Desktop's config

Open Claude Desktop's config file:

Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Paste this snippet (creating the file if it doesn't exist):

json
{
  "mcpServers": {
    "irv": {
      "url": "https://irv-web.vercel.app/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Replace YOUR_TOKEN_HERE with the token from step 1.

Restart Claude Desktop + ask a question

Quit Claude Desktop fully (Cmd+Q on Mac), reopen, and start a new chat. Try:

“What does my SaaS app's traffic look like this week?”
“What's the highest-priority fix on my Lovable app right now?”
“Show me commits from the last 24 hours.”
“Which shipped insight had the biggest measured lift?”

Claude will call the relevant tool, read the live data, and answer with real numbers + paste-ready Lovable prompts when applicable.

Tools exposed

Seven tools, all read-only. Each project access is ownership-checked against the resolved token's user.

list_projects— List all projects owned by the authenticated user
get_metrics— Headline metrics + breakdowns for one project over a date range
list_insights— Currently-active AI insights with paste-ready Lovable prompts
list_outcomes— Measured outcomes from previously-shipped insights (DiD, CI)
get_project_log— Per-project event log: commits, prompts, outcomes, daily metrics
get_tracking_plan— Code-derived tracking plan from the linked GitHub repo
get_causation— Correlations + counterfactuals + anomalies for one project

Troubleshooting

Claude doesn't see Irv. Quit Claude Desktop fully (not just close the window) and reopen. The config is read at startup only.

“invalid_token”. The token is 64 hex characters. Confirm there are no spaces or quotes inside the value, and that the Authorization header reads exactly Bearer <token>.

Token leaked. Open /app/account, click the trash icon next to the token, paste the first 8 chars to confirm. Generate a fresh one + update Claude's config.

Verify connectivity. The endpoint responds to GET with version info: curl https://irv-web.vercel.app/api/mcp.

Other MCP clients