MCP: Connect via OAuth (Interactive Sign-in)
Overview
Interactive sign-in lets you ask Felix questions about your Quantum Metric data from your own AI assistant: Claude, ChatGPT, Cursor, VS Code, or any client that supports the Model Context Protocol (MCP).
You sign in once with your Quantum Metric account. Every call runs as you, with your role, permissions, workspace and timezone. There is no token to create or store.
Once connected, your assistant can query behavioral data, investigate sessions and errors, run funnels and saved queries, and work with the dashboards, workflows and monitoring agents in your subscription.
Scope and limits
- Read and act on collected data only. Quantum Metric MCP works with a subscription that already collects data.
- Targeted questions and actions. For bulk data movement, you should use the Quantum Metric API instead.
- Your permissions carry over unchanged. Your assistant sees only what your Quantum Metric account can see.
Before you begin
You need:
- A Quantum Metric login with access to the subscription.
- Your subscription name, as it appears in your Quantum Metric URL.
- An MCP client that supports sign-in (MCP OAuth). Claude Code, Claude desktop and web, ChatGPT, Cursor and VS Code all do.
Endpoint
https://api.quantummetric.com/mcp/<subscription>
Replace <subscription> with your subscription name.
Connect your client
Add the endpoint URL to your client with no headers or token. The first time you connect, a browser window opens for Quantum Metric sign-in. The client keeps you signed in after that.
Client | Where you add it | How sign-in starts |
|---|---|---|
Claude Code | A terminal command | Run |
Claude desktop and web | Customize › Connectors | When you add the connector |
ChatGPT | chatgpt.com/plugins | When you install the plugin |
Cursor |
| From Cursor's MCP settings |
VS Code |
| Automatically on first connect |
Claude Code
Step 1. In a terminal, run:
claude mcp add --transport http felix https://api.quantummetric.com/mcp/<subscription>
Step 2. Start Claude Code, run /mcp, select felix, and sign in. You can also sign in from a terminal with claude mcp login felix.
Claude desktop and web
- Go to Customize › Connectors.
- Select + Add › Add custom connector.
- Enter a name, such as
Felix, and the endpoint URL. Select Add. - Sign in with your Quantum Metric account when prompted.
On Team and Enterprise plans, an organization owner adds the connector once under Organization settings › Connectors. Members then open Customize › Connectors, find it, and select Connect. The connector works across Claude desktop, web and mobile.
ChatGPT
- Go to chatgpt.com/plugins.
- Select + › Add custom MCP server.
- Enter a name and the endpoint URL.
- Set Authentication to OAuth.
- Create the plugin, then install it.
- Sign in with your Quantum Metric account when prompted.
Whether you can add custom MCP servers depends on your ChatGPT plan and your workspace admin's settings.
Cursor
Step 1. Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
{
"mcpServers": {
"felix": {
"url": "https://api.quantummetric.com/mcp/<subscription>"
}
}
}
Step 2. Restart Cursor, open its MCP settings, connect felix, and sign in.
VS Code (Copilot agent mode)
Step 1. Add the server to your user mcp.json, or to .vscode/mcp.json in a workspace. The top-level key is servers:
{
"servers": {
"felix": {
"type": "http",
"url": "https://api.quantummetric.com/mcp/<subscription>"
}
}
}
Step 2. Restart VS Code. A browser window opens for sign-in the first time it connects.
Verify the connection
- Check that the server shows as connected:
claude mcp listin Claude Code, or the connector status in your client's settings. - Ask a question that needs your data, such as "List the dashboards in this subscription."
- Ask your assistant to run
get_context. Confirm it shows your subscription, workspace and timezone.
Working with workspaces
Your session starts in your current Quantum Metric workspace and uses your profile timezone, so answers should match what you see in the UI.
To query a different workspace:
- Ask your assistant to run
list_workspacesand find the workspace ID. - Ask it to pass that ID as
workspaceon later calls. The server keeps no state between calls, so the workspace applies per call.
To use a different timezone, ask your assistant to pass timezone on tools that accept it.
Security and data governance
- Access follows your identity. Every call runs as your Quantum Metric account. MCP adds no access beyond what your account has.
- Disconnecting. Remove the server from your client to stop using it. Removing your Quantum Metric access ends access from every client.
Troubleshooting
Symptom | Cause | Fix |
|---|---|---|
Client connects, but no tools appear | The client loads MCP configuration only at startup | Restart the client. Confirm the URL is |
No sign-in window opens | The client does not support MCP sign-in, or sign-in was not started | In Claude Code, run |
401: "The access token expired", "was rejected" or "is no longer valid" | Your sign-in expired or is no longer accepted | Sign in again from your client. |
"Session expired or unauthorized (403)" on every tool call | Most often, the subscription in the URL is one your login cannot access. The same message appears when your sign-in is no longer accepted. | Check the subscription name, then sign in again with the account that belongs to it. |
"You do not have access to this feature" on specific tools | Your role does not include that feature | Ask your Quantum Metric admin to review your permissions. |
Results differ from the Quantum Metric UI | Different workspace or timezone | Run |
A parameter seems to have no effect | Tools ignore parameters they do not define | Check the name against the tool definition, e.g. |
Query times out | Analytics queries are limited to 120 seconds | Narrow the time range, add filters, or use a saved query. |
Query returns no data | Wrong workspace, time range or event name | Confirm workspace, time range, and that the events exist. |
"Error: no workspace set" | Your Quantum Metric profile has no current workspace | Ask your assistant to run list_workspaces and pass a workspace ID as workspace. |
Getting help
Contact your Customer Success Engineer for help connecting MCP to your AI assistant.
Appendix: tool reference
The server exposes tools across 16 capability areas. Your client retrieves the current list at connect time. Some per-subscription tools, such as Voice of Customer survey tools, appear when enabled for your subscription.
Area | What it covers |
|---|---|
Workspaces | List team workspaces and resolve one to its ID |
Context | Subscription, workspace, timezone and profile for the session |
Analytics | Ad-hoc queries of behavioral and performance data |
Saved Queries | List, run and create saved queries |
Sessions and users | Session and user summaries, replay URLs, page hits, replay screenshots |
Business Concepts | The business concept model configured for the subscription |
Events | Event definitions, event discovery and event value search |
Catalog | Metrics and dimensions available to query |
Dashboards | List and inspect dashboards; run individual cards |
The Quad | Search and read Quantum Metric knowledge base articles |
Knowledge | Analytics skills and guidance available to the assistant |
Page Discovery | Resolve a page name to an analytics filter |
Funnels | List and run funnels; analyze step drop-off |
Monitoring Agents | List and run background agents; read results |
Workflows | List and run workflows; read runs and reports |
Alerts | Alerts, incidents, time series and affected sessions |





