Userpilot MCP Server

​

Overview

​

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 connects to MCP servers. Claude lists Userpilot in its connectors directory. ChatGPT, Cursor, Microsoft 365 Copilot, and other tools connect with the server address.

https://mcp.userpilot.io/mcp

​

Connect your AI tool

• Claude
• Claude Code
• ChatGPT
• Cursor
• Microsoft 365 Copilot
• Other AI tools

Userpilot is listed in the Claude connectors directory. You connect it once in Claude on the web or in the Claude desktop app, and it then works in the Claude mobile apps and in Claude Code too.

1

Find Userpilot in the directory

Go to Customize → Connectors and select Discover. In the desktop app, select Customize in the sidebar, then Connectors. Search for “Userpilot”, then select Userpilot.

2

Connect Userpilot

Select Connect to Claude.On Team and Enterprise plans, an organization Owner adds Userpilot once with Connect for your team. Members then connect with their own Userpilot login. If Userpilot isn’t added for your organization yet, you see Request or a note to ask an Owner instead.

3

Sign in and choose permissions

Claude opens the Userpilot sign-in. Log in as you always do (SSO included), tick the access you want to grant, and approve.

Userpilot shows as Connected in your connectors.

4

Turn it on in a chat

In a chat, select + in the message box, then Connectors, and switch on Userpilot. Claude may ask for your approval before it uses a Userpilot tool. Select Allow once or Always allow.

Claude can now use Userpilot in that chat.

If you sign in to Claude Code with your Claude account, the Userpilot connector you connected in Claude is already available. Run /mcp to see it. Claude Code doesn’t load your Claude connectors when it runs with an API key or through a cloud provider such as Amazon Bedrock. In that case, add the server yourself:

1

Add the server

claude mcp add --transport http userpilot https://mcp.userpilot.io/mcp

2

Authenticate

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.

1

Turn on developer mode

Open Settings → Apps & Connectors → Advanced settings and switch on Developer mode.

2

Add the connector

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.

3

Sign in and choose permissions

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.

4

Enable it in a chat

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.

1

Add the server

Open Cursor Settings → MCP → Add new MCP server, or edit ~/.cursor/mcp.json yourself:

{
  "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.

2

Reload Cursor

Restart Cursor, or refresh the list from Settings → MCP. The userpilot server appears there.

3

Sign in and choose permissions

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.

4

Check the tools loaded

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.

1

Create an agent

Sign in to Copilot Studio. 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.

2

Add the MCP tool

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.

3

Sign in to Userpilot

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.

4

Publish and add to Microsoft 365 Copilot

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, 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

• 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

• 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.

• 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

​

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.

​

FAQs