Overview
The UXCam MCP connects your AI assistant (Claude, ChatGPT, Cursor and others) directly to your UXCam data. Ask questions in plain language and your assistant pulls real numbers, funnels, retention and session evidence from your apps, without opening the UXCam dashboard.
It is built on the Model Context Protocol (MCP), an open standard for connecting AI assistants to data sources.
What you can do with it
Answer product questions: sessions, users, crash rate, screen visits and events, broken down by platform, country, app version and more.
Analyze conversion and retention: multi-step funnels with drop-off, and cohort retention.
Find out why: search sessions and screens for what users actually experienced.
Integrate and verify the SDK: let a coding assistant add UXCam to your app, then confirm that sessions, screens and events are arriving.
Combine UXCam with your other work: your roadmap doc, tickets or code sit in the same conversation as your UXCam data.
A typical workflow
Pick your app: ask "Which UXCam apps do I have access to?" and name the one you want.
Discover: let the assistant look up your real screen names, event names and properties.
Query: ask for metrics, funnels, retention or heatmaps.
Investigate: drill into sessions and screens behind the numbers.
Iterate: refine with follow-up questions in the same conversation.
The UXCam MCP is read-only: it cannot change anything in your UXCam account. It also does not use Tara credits.
Who can use it
Everyone with an active UXCam account can use the MCP, on every plan. No admin setup is needed.
You sign in with your normal UXCam account. Your existing permissions apply.
You only see apps you already have access to in UXCam. If a teammate can see an app and you can't, your assistant can't either.
Your plan's data retention still applies, exactly as in the UXCam dashboard.
You also need an AI assistant that supports MCP connectors. Some assistants only offer custom connectors on paid plans (see Connect).
Connect
Add one connector to your assistant, sign in with your UXCam account, and you're done. There's no key to copy and no config file for Claude or ChatGPT.
Server URL: https://connect.uxcam.com/mcp
Any assistant that supports remote MCP servers over HTTP with OAuth sign-in should work. Reach out to team@uxcam.com if you need help.
Claude (web and desktop)
Go to Settings → Connectors → Add custom connector.
Name it UXCam and paste the server URL: https://connect.uxcam.com/mcp
Click Connect and sign in with your UXCam account when the login window opens.
UXCam then appears in Claude's tool list, and you can ask questions in any conversation.
ChatGPT
Go to Settings → Connectors → Add custom connector.
Paste the server URL: https://connect.uxcam.com/mcp and set authentication to OAuth.
Sign in with your UXCam account.
Custom connectors require a ChatGPT Plus, Pro, Business or Enterprise plan. On some plans they only appear once Developer mode is turned on under Settings.
Cursor
Go to Settings → Tools & MCP → New MCP Server and add:
{
"mcpServers": {
"uxcam": {
"type": "streamable-http",
"url": "https://connect.uxcam.com/mcp"
}
}
}
The first time the assistant uses UXCam, a browser window opens so you can sign in.
Claude Code
claude mcp add --transport http uxcam https://connect.uxcam.com/mcp
Then run /mcp inside Claude Code and complete the UXCam sign-in in your browser.
VS Code and other assistants
Use the same JSON configuration as Cursor, or follow your assistant's instructions for adding a remote MCP server. You'll be asked to sign in to UXCam the first time a UXCam tool runs.
Gemini CLI limitations
Currently, versions above v0.56.0 do not allow you to connect to MCPs like ours. Please follow the bug link for updates: https://github.com/google-gemini/gemini-cli/issues/29477
Working with more than one app
One app: your assistant uses it automatically.
Several apps: ask "Which UXCam apps do I have access to?" first, then name the app in your question. If you don't, the assistant will ask you which one you mean.
Available tools
Available tools
The UXCam MCP gives your assistant 19 read-only tools, grouped below by the job they do. You don't call them yourself: your assistant picks the right tool based on your question.
Category | Tool | What it does |
Apps and account | list_user_apps | Lists every app you can access, grouped by organization |
| list_projects | Lists projects by environment, each with its SDK app key |
| get_app_info | Shows one app's SDK status, recording setup and features in use |
| get_account_settings | Shows your plan, session quota usage, team members and recording health |
Analytics | query_metrics | Runs metric queries: sessions, users, crashes, screens, events, with breakdowns |
| query_funnels | Runs multi-step conversion funnels with drop-off and timing |
| query_retention | Runs cohort retention analysis |
| get_analytics_schema | Lists the metrics and dimensions available, including your custom properties |
| lookup_filter_values | Finds real values to filter on: screen names, events, devices, app versions |
| get_screen_heatmap | Returns gesture heatmap data for a screen |
Sessions and screens | explore_sessions | Finds and filters sessions, with plain-language search |
| explore_screens | Finds screens and what users experienced on them |
| query_pii_exposure | Finds sessions where personal data was detected on screen |
SDK integration | get_sdk_guide | Returns integration docs for iOS, Android, Flutter, React Native and web |
| get_integration_checklist | Shows integration milestones and how to fix open issues |
| verify_integration | Checks whether sessions are arriving from your app |
| validate_instrumentation | Confirms that tagged screens and events are landing |
| verify_web_occlusion | Confirms a sensitive value on a web page was hidden before recording |
Data quality | get_verification_stats | Shows how many sessions were recorded versus attempted, and why any were lost |
Tool reference
What each tool is for, what to ask, and the limits to know. "Platform" shows whether a tool works with mobile apps, web apps or both.
Apps and account
Try: "Which UXCam apps do I have access to, and is the SDK live on all of them?"
Tool | Good to know | Platform |
list_user_apps | Usually the first thing your assistant runs. Only shows apps you can access in UXCam. | Both |
list_projects | Shows each environment's app key, so a coding assistant can put the right key in the right config file. Returns up to 50 projects at a time. | Both |
get_app_info | Also shows whether AI session summaries are enabled for the app, which plain-language session search depends on. | Both |
get_account_settings | If you have several apps, name one first. | Both |
Analytics
Try: "Compare checkout funnel conversion on iOS vs Android for the last 30 days, and show me where the biggest drop-off is."
Tool | Good to know | Platform |
query_metrics | Covers sessions, users, new vs returning users, session duration, crash rate, UI freezes, rage gestures, app start times, screen visits and event counts. Break down by date, platform, country, app version, device and your custom properties. Defaults to the last 30 days. Returns up to 1,000 rows. Flags when the latest period is still incomplete. | Both |
query_funnels | Steps can be screens or events, in strict order or any order. Shows conversion and drop-off per step, time between steps, breakdowns and trends over time. Chooses user-level or session-level counting automatically and tells you which. Defaults to the last 30 days. | Both |
query_retention | Separates retention of genuinely new users from stickiness of your existing user base. | Both |
get_analytics_schema | Lets the assistant see which metrics and properties exist before it builds a query. | Both |
lookup_filter_values | Returns the exact screen names, event names, devices and versions in your data, so filters match what's really tracked. | Both |
get_screen_heatmap | Taps, swipes, rage taps and unresponsive gestures for one screen. Needs the exact screen name. | [Mobile only] |
Sessions and screens
Try: "Show me sessions from last week where users hit an error on the checkout screen, and what happened right before."
Tool | Good to know | Platform |
explore_sessions | Filter and sort by date, device, OS, app version, country, duration, crashes, rage gestures and more. Returns up to 100 sessions per page. Plain-language search ("users who gave up at payment") only works if AI session summaries are enabled, and only covers sessions that have been summarized. Without it, you can still filter and sort. | Both |
explore_screens | Works best with short screen names ("Checkout", "Login") rather than long descriptions. Returns up to 100 screens. Plain-language search has the same requirement as explore_sessions. | Both |
query_pii_exposure | Shows which screens exposed personal data, the type of data and when. Looks back 1 to 365 days. Does not return the personal data itself. | Both |
SDK integration
Try: "Add the UXCam SDK to this app, tag the checkout screens, then check that sessions are arriving."
These tools are designed for coding assistants such as Cursor or Claude Code, working inside your app's codebase.
Tool | Good to know | Platform |
get_sdk_guide | Covers iOS, Android, Flutter, React Native and web. | Both |
get_integration_checklist | Shows the same readiness steps as the UXCam dashboard, with fix instructions. | Both |
verify_integration | Checks whether sessions are really arriving. Limited to 6 checks per minute, because assistants tend to retry it while waiting for the first session. | Both |
validate_instrumentation | Tells you, item by item, whether the screens and events you tagged are arriving, with counts. | Both |
verify_web_occlusion | Confirms a sensitive value never left the user's browser, by checking the recorded page rather than the video. | Web only |
Data quality
Try: "Are we losing sessions, and if so, why?"
Tool | Good to know | Platform |
get_verification_stats | Compares sessions recorded with sessions attempted, and explains any gap. Worth checking if numbers look lower than expected. | Both |