> ## Documentation Index
> Fetch the complete documentation index at: https://docs.userpilot.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Userpilot MCP Server
> Connect AI assistants like Claude to your Userpilot account to explore analytics, look up users and companies, and create segments, reports, and surveys.
## Overview
The Userpilot MCP server connects AI assistants to your Userpilot account. Once connected, you can ask questions in plain language, such as "How did my signup funnel perform last month?", and the assistant reads the answer directly from your Userpilot data. You can also ask it to create things for you, such as segments, reports, dashboards, and survey drafts.
MCP (Model Context Protocol) is an open standard that AI tools use to talk to other products. Userpilot hosts the server for you: you connect from the AI tool you already use and sign in with your regular Userpilot login. There is nothing to install or configure inside Userpilot.
## Use Cases
* **Ask analytics questions**: "What's the completion rate of my onboarding funnel this quarter?" or "Show retention for users who used the export feature."
* **Explore users and companies**: "Which companies were most active this week?" or "Summarize this user's recent activity."
* **Build as you think**: "Create a segment of users who completed onboarding but never opened reports" or "Build a dashboard for my activation metrics."
* **Draft surveys**: "Draft a short survey asking users why they canceled." You review and publish it in Userpilot.
* **Look things up while you work**: "What audience does the 'New user tour' flow target?" or "List the events we track on the checkout page."
## What you need
* A Userpilot account. The MCP server is available on all plans, and your plan's feature limits apply the same way they do in the app.
* An AI tool that supports remote MCP servers (sometimes called custom connectors), for example Claude, Claude Code, ChatGPT, Cursor, or Microsoft 365 Copilot.
The server address is:
```text theme={null}
https://mcp.userpilot.io/mcp
```
## Connect your AI tool
Custom connectors are available on paid Claude plans. On Team and Enterprise plans, a Claude admin adds the connector once for the organization; every member then connects it with their own Userpilot login.
Open the account menu (your name, bottom left) and go to **Organization settings → Connectors** (under "Libraries & Access"). Click **+ Add → Custom → Web**.
In the **Add custom connector** dialog, name it "Userpilot" and paste the server address above into **Remote MCP server URL**. Leave the Advanced settings fields empty — Userpilot registers automatically. Keep **Individual sign-in** switched on, then click **Add**.
On a personal account, add the same connector under **Settings → Connectors** instead.
Click **Connect** on the Userpilot connector. Your browser opens the Userpilot sign-in. Log in as you always do (SSO included). On team plans, each member does this once with their own login.
Userpilot shows a permission screen. Tick the access you want to grant and approve.
Claude can now use Userpilot in your chats. You can toggle it per conversation from the tools menu.
```bash theme={null}
claude mcp add --transport http userpilot https://mcp.userpilot.io/mcp
```
Run `/mcp` inside Claude Code, select **userpilot**, and complete the browser sign-in and permission screen.
Claude Code lists the Userpilot tools once the connection is active.
Custom connectors are available on paid ChatGPT plans and need developer mode switched on. On Business and Enterprise plans, a ChatGPT workspace owner may need to allow custom connectors first.
Open **Settings → Apps & Connectors → Advanced settings** and switch on **Developer mode**.
Still under **Apps & Connectors**, create a new connector. Name it "Userpilot", paste the server address above into the **MCP Server URL** field, and choose **OAuth** as the authentication method.
Save the connector. Your browser opens the Userpilot sign-in — log in as you always do, then tick the access you want to grant and approve.
Open a new conversation and switch on the Userpilot connector from the composer's tools menu. For deep research, pick Userpilot as a source.
ChatGPT can now use Userpilot in that conversation.
ChatGPT's connector settings change often. If the menus no longer match, the parts that stay the same are: create a **custom MCP connector**, choose **OAuth**, and use the server address above.
Open **Cursor Settings → MCP → Add new MCP server**, or edit `~/.cursor/mcp.json` yourself:
```json theme={null}
{
"mcpServers": {
"Userpilot": {
"url": "https://mcp.userpilot.io/mcp"
}
}
}
```
If that file already exists, add the `userpilot` entry inside the existing `mcpServers` object rather than replacing the file, so your other servers stay. To use Userpilot in one project only, create `.cursor/mcp.json` in that project folder instead.
Restart Cursor, or refresh the list from **Settings → MCP**. The `userpilot` server appears there.
Use the sign-in prompt on the `userpilot` entry. Your browser opens the Userpilot sign-in — log in as you always do, then tick the access you want to grant and approve.
Back in **Settings → MCP**, the `userpilot` entry lists the Userpilot tools it can use.
Cursor's agent can now use Userpilot in chat.
Connecting Userpilot to Microsoft 365 Copilot goes through **Microsoft Copilot Studio**, where you build and publish the agent that end users chat with.
Sign in to [Copilot Studio](https://copilotstudio.microsoft.com/). On the **Home** page, under **Start building from scratch**, select **Create an agent**, then give it a name, for example "Userpilot".
If your organization already has an agent you want to use instead, open it from **Agents** in the left navigation and skip to the next step.
In the agent, select **Tools** in the left navigation, then **Add a tool** and **New tool**. Search for `Model Context Protocol` and select it, and the **Add a Model Context Protocol server** dialog opens.
Name it "Userpilot", write a short description, and paste the server address above into **Server URL**. Under **Authentication**, choose **OAuth 2.0**, then **Dynamic discovery**. Userpilot supports OAuth 2.0 dynamic client registration, so there's nothing else to configure.
Select **Create**, then **Next**.
On the **Add tool** dialog, select **Create a new connection**. Your browser opens the Userpilot sign-in: log in as you always do (SSO included), then tick the access you want to grant and approve.
Select **Add to agent** to finish.
The Userpilot tool appears under the agent's **Tools** section.
Select **Publish** at the top of the agent page, then **Publish** again to confirm.
Go to **Channels**, select the **Teams and Microsoft 365 Copilot** tile, keep **Make agent available in Microsoft 365 Copilot Chat** checked, then select **Add channel**.
Once connected, open [Microsoft 365 Copilot](https://copilot.cloud.microsoft/), enter **@**, select your agent from the list, and start asking it about your Userpilot data.
Microsoft 365 Copilot can now use Userpilot when your agent is mentioned.
Any tool that supports remote MCP servers with OAuth sign-in can connect:
1. Add a remote (HTTP) MCP server in the tool's settings and paste the server address above.
2. When the tool prompts you, sign in with your Userpilot login and approve the permissions.
The exact menu names vary by tool. Look for "MCP servers", "connectors", or "integrations" in its settings.
## Choose what the assistant can access
When you connect, Userpilot shows a permission screen. You decide what the assistant can see and change:
| Permission | What it allows |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Read your product data, analytics, and reports | The foundation, always required: reports, dashboards, events, pages, features, flows, surveys, segments, and analytics results. |
| Read individual user and company profiles | Profile details and activity for specific users and companies. Leave it unchecked to keep individual records out of AI conversations. |
| Read session replay data | Session replay lists and activity summaries. |
| Create and update user segments | New segments, and changes to existing ones. |
| Create and update reports and dashboards | New reports and dashboards, and changes to existing ones. |
| Create and update surveys (saved as drafts) | Survey drafts for you to review. Nothing reaches your users until you publish. |
| Keep this connection active without re-login | Stay signed in between conversations. Without it, access ends about 15 minutes after each sign-in. |
A few things to know:
* **You can change your mind later.** To grant a permission you skipped, connect again from your AI tool: the permission screen appears and remembers what you approved before.
* **Write permissions need the read permission.** The screen enforces this automatically.
* **Changes are real.** Segments, reports, and dashboards the assistant creates or updates take effect immediately, just as if you made the change in the app.
## What the assistant can and can't do
With the permissions you grant, the assistant can:
* Run and read analytics: funnels, trends, retention, paths, saved reports, and dashboards.
* Look up your product setup: flows, surveys, events, pages, features, segments, and more.
* Read user and company lists and profiles.
* Create and update segments, reports, dashboards, and survey drafts.
* Go beyond the basics: when a question needs it, the assistant can search hundreds of additional read-only operations.
It can never:
* Build or publish in-app content such as flows and banners (content building stays in the Userpilot builder).
* Delete anything.
* Access team management, billing, account settings, or other administration areas.
* Do anything your own Userpilot role doesn't allow.
### Working with multiple apps
If your account has more than one app, the assistant can list the ones you have access to and ask which one to use. It remembers your choice for the connection, and you can tell it to switch at any time.
## Security and privacy
* **Your login, your permissions.** The connection runs under your own Userpilot user. The assistant can only see and change what your role allows, in the apps you have access to.
* **You control the scope.** The permission screen decides what is reachable; everything outside it is refused by Userpilot's servers, not by the assistant's judgment.
* **No destructive access.** Delete operations and administration areas are not available through the connection at all.
* **Built-in limits.** Rate limits automatically contain runaway or abusive usage.
* **Disconnect anytime.** Remove the connector in your AI tool to stop new access. Without the "keep active" permission, access also expires on its own shortly after each sign-in.
Data the assistant reads through this connection is processed by your AI provider (for example, Anthropic for Claude) under that provider's terms. Review your organization's AI policies before connecting tools to customer data.
### FAQs
Any tool that supports remote MCP servers with OAuth sign-in. Claude, Claude Code, ChatGPT, Cursor, and Microsoft 365 Copilot are documented step by step above; for other tools, use the server address and follow the tool's own instructions for adding an MCP server or custom connector.
You skipped that permission when connecting. Connect again from your AI tool. The permission screen appears with your earlier choices remembered; tick the missing one.
Your access to that app changed. Ask the assistant to list your workspaces and pick one you can access.
Only within the write permissions you granted, and never beyond them: segments, reports, dashboards, and survey drafts. It cannot delete anything, publish content, or touch account settings. If you grant no write permissions, the connection is read-only.
Anyone with a Userpilot login. On Claude Team and Enterprise plans, a Claude admin adds the connector once for the organization; each member then connects and signs in as themselves, and their connection mirrors their own role and app access.
Your AI tool keeps its own copy of the tool list. In Claude, open the Userpilot connector's settings and use **Refresh tools**; disconnecting and reconnecting alone does not refresh the list.
Remove the connector in your AI tool. If you need a connection revoked on the Userpilot side (for example, for a teammate who left), contact support.
For any questions or concerns please reach out to [**support@userpilot.com**](mailto:support@userpilot.com)