FAQ

LiveRecover MCP is a Model Context Protocol server that lets you connect AI assistants like Claude to your LiveRecover data. You can ask natural language questions about your conversations, workflows, analytics, and customer insights — and get answers backed by real data.

LiveRecover MCP works with any MCP client that supports HTTP transport, including:

• Claude Code (CLI)
• Claude Desktop
• Cursor

See the quickstart guides for setup instructions.

Customer-data tools live on the dedicated CDP MCP server at https://cdp-mcp.vyg.app/mcp — 16 read-only tools for customer lookup, audiences, and behavioral insights. Two of them (cdp_customer_profile and cdp_customer_journey) currently also run on this server, but they are moving to the CDP MCP, which is the home for all customer-data work going forward. See the CDP MCP overview to connect.

Yes. LiveRecover MCP uses OAuth 2.1 with PKCE — the same security standard used by major platforms. Your credentials are never shared with the MCP client. All tools are read-only and scoped to the brand you select during authentication. See Authentication for details.

You can access the brand you select during the OAuth authentication flow. Your session is scoped to a single brand at a time.

To switch brands, disconnect and reconnect with a different brand selection:

• Claude Code: claude mcp remove liverecover then claude mcp add liverecover --transport http https://mcp.vyg.app/mcp
• Claude Desktop / Cursor: Restart the application to trigger a new authentication flow

Not in a single session. Each MCP connection is scoped to one brand. You would need separate sessions for different brands.

Your access token may have expired. Try these steps:

1. Disconnect the MCP server
2. Reconnect and re-authenticate
3. Make sure to select a brand during the approval step

If the issue persists, check that your LiveRecover account is active and has access to at least one brand.

This means authentication succeeded but no brand was selected. Reconnect and make sure to select a brand during the OAuth approval step.

Tokens refresh automatically in the background. If auto-refresh fails, you'll be prompted to re-authenticate. You won't lose any data.

Check your terminal output for a URL you can copy and paste into your browser manually. Some environments (SSH sessions, containers) don't support automatic browser opening.

Make sure:

• You selected the correct brand during authentication
• The brand has active conversations and workflows
• Your date filters (if any) match a period with data