Connecting to the Qvasa MCP

The Qvasa MCP lets AI assistants like Claude work with your Qvasa data on your behalf: running metric queries, inspecting dashboards and answering questions in plain words. Claude users connect from Qvasa's listing in Claude's connector directory: you sign in to Qvasa and choose what Claude may do, with nothing to install, no token to paste and nothing to keep up to date. Claude can never do more than you can: what you allow is checked against your live Qvasa permissions on every request.

This guide walks through what an admin turns on first (Steps 1 and 2), then connecting Claude. Other AI clients, such as Cursor and Glean, connect to it as a remote MCP server at https://www.qvasa.com/mcp, or through the local package, with a User Access Token; those setups follow after.

Before you start

You need admin access in Qvasa for Steps 1 and 2. Every way to connect needs them.
The feature must be turned on for your account by the Qvasa team. If you don't see the setting described below, contact your Qvasa representative and we'll enable it for you.
Admins keep a kill switch: toggling the account setting off rejects all existing tokens immediately.
IT and security teams reviewing the connector: the Qvasa MCP Server — Security and Integration Reference covers authentication, scopes, data handling and auditing.

Step 1: Enable User Access Tokens for your account

Go to Settings → Account Settings in Qvasa.
Search for "user access" and find the card labeled User Access Tokens.
Click Enable.

Step 2: Grant the permission to a user

Each user who should be able to create tokens needs the manage user access tokens permission:

Go to Settings → Manage Account Members and open the user you want to grant the permission to.
In the permissions list, find the User Access Token Permissions group and check Can manage user access tokens.
Save the user.

With this permission, the user can connect Claude, and create, re-scope, revoke, and delete their own tokens. For a general overview of how Qvasa permissions work, see Managing User Permissions in Qvasa.

Step 3: Connect Claude

Qvasa is listed in Claude's connector directory. There's nothing to install and no token to paste: Claude signs in to Qvasa for you, and the connection never needs updating.

You'll also find these steps in Qvasa, on the Connect Claude to Qvasa page (under User Settings).

Claude Desktop and claude.ai

1. Open Qvasa in Claude's connector directory and click Connect. In Claude Desktop you can also open Customize → Connectors, browse the connectors and search for Qvasa.

2. Qvasa's permissions page opens. Choose exactly what Claude is allowed to do (the same scope picker you see when creating a token) and click Connect. You're sent back to Claude.

On a Claude Team or Enterprise plan, an owner of your Claude organization adds Qvasa for the organization first. After that, each member connects as above and signs in to Qvasa with their own login, so Claude only ever has that member's Qvasa permissions.

That's it! Now, what to ask Qvasa

Once Qvasa is connected, ask about your support data in plain words. A few to start with:

"How many tickets did we get last week, broken down by group?"
"Which agents solved the most tickets in the last 7 days?"
"Show me five of the tickets behind that number."
"Make me a dashboard called Weekly Review with a chart of tickets created by group."
"Alert me when we get more than 50 new tickets in an hour."

Claude can only do what you have permission to do in Qvasa.

Using Qvasa in Claude Code (optional)

If Claude Code is signed in with your claude.ai account, Qvasa is already there once you've connected it in claude.ai: type /mcp and look for claude.ai Qvasa.

Don't see it? (For example, Claude Code is signed in with an API key rather than your claude.ai account.) Add Qvasa yourself:

In a terminal, run:
```
claude mcp add --transport http --scope user qvasa https://www.qvasa.com/mcp
```
Already inside Claude Code? Type the same command at the prompt with ! in front: ! claude mcp add --transport http --scope user qvasa https://www.qvasa.com/mcp. --scope user makes Qvasa available in every folder you open Claude Code in; without it, only in the current one.
In Claude Code, type /mcp, pick qvasa and choose Authenticate. A browser window opens: log into Qvasa and choose what Claude is allowed to do. If qvasa isn't listed, restart Claude Code.

Other ways to set up the MCP

Not needed if you connected in Step 3. These use a User Access Token instead of a sign-in: for the Claude Desktop bundle, Cursor, Genspark and other MCP clients.

The server URL for any remote MCP client is https://www.qvasa.com/mcp (Streamable HTTP). It doesn't need a token: add the URL in an app that supports remote MCP servers, and once an admin has done Steps 1 and 2, the app takes you through the same Qvasa sign-in and permissions page as Claude.

Generate a token for local MCP or HTTP requests

Now, as the user who received the permission:

Go to User Settings → User Access Tokens and click to generate a new token.
Give the token a name (for example, "Claude MCP").
Pick an expiration — the default is 90 days and the maximum is 1 year; shortcut buttons fill in common choices.
Choose the token's scopes. Every token can query metrics and manage its own memory out of the box; the checkboxes grant additional read, write, and special-feature scopes on top of that baseline. You'll only see sections your own permissions allow — a token can never exceed what you can already do.
Click Generate.

Copy your token — it's shown exactly once

The next screen shows your new token. Copy it now — Qvasa never stores the raw token (only a one-way hash), so this is your only chance to see it. Store it in a secrets manager, and never share it in plain text. If you lose it, revoke the token and generate a new one.

Connect with the token: Claude Desktop bundle, Cursor and other clients

Claude Desktop — one-click bundle

Download qvasa-mcp.mcpb.
Double-click the downloaded file. Claude Desktop opens an install dialog.
Paste your token into the field labeled Qvasa User Access Token, then click Install.

No terminal, no JSON, no Python install. A bundle doesn't update itself: when Claude tells you a newer version is out, download it again from the same link.

Cursor, Claude Code and other MCP clients — the qvasa-mcp package

Install uv, the Python runner, once: curl -LsSf https://astral.sh/uv/install.sh | sh. Don't use brew install uv, which builds Python. On Windows, see uv's install docs.
Claude Code: run claude mcp add qvasa --env QVASA_API_KEY=qva_uat_YOUR_TOKEN_HERE -- uvx qvasa-mcp@latest, then check it with claude mcp list. Connecting with a Qvasa sign-in (Using Qvasa in Claude Code, above) is simpler.
Cursor and most other clients: open the client's MCP config file and paste the block below. If it already has an mcpServers block, add the "qvasa" entry to it.

{
  "mcpServers": {
    "qvasa": {
      "command": "uvx",
      "args": ["qvasa-mcp@latest"],
      "env": {
        "QVASA_API_KEY": "qva_uat_YOUR_TOKEN_HERE"
      }
    }
  }
}

Replace qva_uat_YOUR_TOKEN_HERE with your full token. qvasa-mcp@latest checks for a new version each time it starts, so the package keeps itself up to date.

Then verify the connection by asking: "In your integrations, what qvasa tools do you have?"

Genspark and clients that take a request header

The Qvasa MCP server works with any client that supports remote MCP servers over Streamable HTTP with custom request headers. Genspark is a popular example, and the same pattern applies to similar clients.

One important difference from Claude: connecting with a Qvasa sign-in is supported only in Claude clients (Claude Desktop, claude.ai and Claude Code). In Genspark and other clients, skip OAuth entirely and authenticate with your token in a request header, as follows:

Generate and copy a token (above).
In the Genspark AI Browser, click the wrench icon at the bottom of the window, choose Add, then Add new MCP server.
Fill in the form: Server name: qvasa · Server type: Streamable HTTP · Server URL: https://www.qvasa.com/mcp · Description: optional, for example "Qvasa support analytics".
In the Request headers field, add your token as an Authorization header: { "Authorization": "Bearer qva_uat_YOUR_TOKEN_HERE" }. Replace everything after Bearer with your full token. The word Bearer and the single space before the token are required.
Save the server, then verify by asking the agent: "In your integrations, what qvasa tools do you have?" A working connection lists the qvasa tools, including qvasa_overview and qvasa_query_metric.

A few notes for non-Claude clients:

Don't configure OAuth. If your client shows an OAuth screen or an invalid_redirect_uri error, it is trying the sign-in that only Claude clients support. Remove any OAuth client settings and use the request-header setup above.
Use Streamable HTTP, not SSE. Qvasa's endpoint does not support SSE connections; a client configured for SSE will fail to connect.
Rotate before expiry. When your token expires (90 days by default), generate a new one and update the saved Authorization header in your client.

Troubleshooting

I don't see the User Access Tokens setting. The feature needs to be turned on for your account by the Qvasa team — contact your Qvasa representative.
I don't see User Access Tokens under User Settings. Confirm the account setting is enabled (Step 1) and that your user has the Can manage user access tokens permission (Step 2).
Switching from the qvasa-mcp package to connecting by URL. Remove the old server first, so Claude doesn't run both: in Claude Code, run claude mcp remove qvasa from the folder where you first set it up (claude mcp list there shows it), then follow Using Qvasa in Claude Code. In Claude Desktop, remove the Qvasa extension under Settings → Extensions, then connect Qvasa from the directory.
Connecting sent me to my Qvasa dashboard, not the permissions page. You weren't signed in to Qvasa when you clicked Connect. Stay signed in to Qvasa, go back to Claude and click Connect again.
I added Qvasa as a custom connector before it was in the directory. It keeps working; nothing to change. To switch to the directory listing, remove the custom one under Customize → Connectors first, so Claude doesn't list Qvasa twice.
Claude Code says MCP server qvasa already exists. An earlier setup is still configured. Run claude mcp remove qvasa and add it again.
I lost my token. Raw tokens can't be recovered. Revoke the lost token from the User Access Tokens page and generate a new one.
My token stopped working. Check that it hasn't expired or been revoked, and that the account-level setting is still enabled — turning it off rejects all tokens. Also remember scopes are intersected with your live permissions: if a permission was removed from your user, the token loses it too.