UserGuiding MCP Server

Connect your AI tools directly to your UserGuiding project through the MCP Server. Once connected, tools like Claude, Cursor, OpenAI Codex or any MCP-compatible assistant can analyse product usage, look up users and companies, build segments, read survey results, manage Knowledge Base articles and Product Updates posts, and moderate your public roadmap, all through natural language.

MCP is available on all UserGuiding plans and takes about two minutes to set up. No developer help needed.

How it works

MCP (Model Context Protocol) is an open standard released by Anthropic in 2024 that lets AI tools call external services in a structured, authenticated way. Instead of pasting data into a chat window or wiring up ad-hoc integrations, the AI tool connects once to an MCP server and gets a well-defined set of tools it can invoke on your behalf.

   AI tools (Claude, Cursor, OpenAI Codex, and others)
        |
        |  Streamable HTTP + JSON-RPC
        v
   UserGuiding MCP Server  (US or EU)
        |
        |  OAuth sign-in, scoped to one project
        v
   Your UserGuiding project data

Two things are worth knowing up front:

• The connection is pinned to one project. You choose it when you sign in, and no tool argument can point the assistant at a different project or another account.
• There is a server per data region. US accounts use https://mcp.userguiding.com/mcp/ and EU accounts use https://eu-mcp.userguiding.com/mcp/. The panel shows the right one for your account.

What you can do with UserGuiding MCP

The MCP Server turns the product data you already track into something you can query conversationally.

Product analytics without dashboards. Engagement summaries, guide funnels, feature adoption, cohort retention and goal completion, asked in a sentence.

"Show me the step funnel for the Onboarding guide over the last 90 days. Where do people drop off?"

User research without SQL. Filter users by any attribute or event, combine criteria, then save the result as a segment.

"Create a segment for Pro plan users who signed up in the last 30 days and fired the export_csv event at least once."

Pre-call research for sales and CS. Before a renewal call, pull everything an account has done: plan, signup date, feature usage, active members, and whether usage is fading against last month.

"Give me the engagement health for Acme Corp this month against last month. Are they going quiet?"

Support context in one prompt. Full profile and recent interaction history, plus the help article to send back.

"Pull the full profile for [email protected], then find me the best knowledge base article about SSO setup."

Content operations. Draft and update Knowledge Base articles in your existing tone, reorganise categories, write Product Updates posts, and clear the feature request inbox.

"Read our last five product update posts, then draft one about the new dashboard filters in the same voice."

More prompts to copy: UserGuiding MCP Use Cases and Example Prompts.

Getting started

• Step 1. In the panel, go to Settings > Project Settings > MCP & API Key and copy the server URL shown there. It already matches your data region.
• Step 2. Add it to your assistant as a custom connector or MCP server. The same page has ready-to-paste snippets for Claude Code, Codex CLI, Cursor and other JSON-config clients.
• Step 3. Connect. Your browser opens a UserGuiding sign-in, you pick the project the assistant may access, and you approve the permissions it asked for.

Full instructions, including API key setup and troubleshooting: Setting Up the UserGuiding MCP Server.

Upgrading from an older setup? The server now speaks Streamable HTTP at /mcp/. The legacy Server-Sent Events endpoints (/mcp/sse and /mcp/messages) have been retired and answer with 410 Gone, so update the URL in your client. API key authentication still works but is being retired in favour of OAuth.

Available tools

The MCP Server exposes 58 tools across nine areas. You never call them by name: you ask a question and the assistant picks the tools, often chaining several to answer one prompt.

• Users and attributes. Look up, search, count, create, update and delete users, read their raw activity feed, and discover which attributes and events your project has.
• Events and product analytics. Event counts, time series with day, week or month buckets, feature adoption with stickiness, and cohort retention matrices.
• Segments. List segments, create and update them from a plain-language description, see what a segment's members actually did, and see how materials targeted to a segment performed.
• Companies. Company profiles, filtered listings, and account engagement health with a previous-period comparison.
• Material analytics. Project-wide overview, per-material performance, guide step funnels, per-user guide progress, checklist item stats, hotspot stats, banner button clicks, resource center tab views and goal completions.
• Surveys. A full survey report with score distributions and drop-off, plus individual responses for reading free-text answers.
• Knowledge Base. Search and read articles, create and update them, manage categories and sub-categories, move articles in bulk, and detect which platform an existing help center runs on before a migration.
• Product Updates. List, create, update and delete posts, with labels and per-language content.
• Roadmap and feature requests. Overview counts, pending and approved requests with live vote counts, the public board, and approve or reject actions.

Every tool, what it returns and the permission it needs: UserGuiding MCP Tool Reference.

Permissions and safety

• Scoped access. An OAuth connection carries only the permissions you approve, from users:read through to roadmap:write. A tool outside those scopes is refused, so a read-only connection stays read-only.
• One project, always. The project is fixed when you connect. Cross-project and cross-account access is not possible.
• Nothing publishes itself. Knowledge Base articles and Product Updates posts written through MCP are saved as drafts. A person with publish permission still has to hit Publish in the panel.
• Everything is logged. Tool calls are retained for roughly three months, and writes appear in the panel Activity Log under the name of the panel user behind the connection.
• Guardrails on analysis. Date ranges are capped at one year, the project is rate limited to 60 tool calls per minute, and oversized requests are rejected with an explanation rather than answered with silently trimmed data.

Pairing with no-code event tracking

The MCP Server pairs naturally with UserGuiding's No-Code Event Tracking. Point and click on elements in your product to start capturing events, with no code, no engineer time and no new SDK. Then query those events through the MCP Server in plain English.

For most product, growth and CS teams, this combination replaces a stack that previously needed a separate analytics product for event tracking plus another tool for exploration. Event capture lives in the same platform as your onboarding, your checklists and your Knowledge Base, and the MCP Server turns product analytics into a chat interface inside Claude, Cursor or Codex.

FAQ

Which plans include MCP? All UserGuiding plans.

Do we need engineering help to set it up? No. It is a connection you enable in your AI tool's settings. Total setup time is about two minutes.

Which server URL should we use? The one shown in Settings > Project Settings > MCP & API Key. It resolves your data region for you: mcp.userguiding.com for US accounts and eu-mcp.userguiding.com for EU accounts.

Does the EU server work the same way? Yes. Both regions share one sign-in service, but tokens are bound to the region, and each server only accepts its own. That is what keeps EU data inside the EU environment. An EU account pointed at the US URL fails on the token check instead of silently reading the wrong data.

My connection stopped working after an update. Older setups used the Server-Sent Events endpoint, which has been retired. Change the URL to end in /mcp/ and reconnect.

Should we use OAuth or an API key? OAuth, for anything new. It never puts a secret in a config file, it lets you grant only the permissions you need, and it names the panel user behind every write in your Activity Log. API keys still work but are being retired.

What data can the MCP Server access? Only the project you selected when connecting, and only within the permissions you approved.

Is the connection secure? Yes. All communication is over HTTPS, every request is authenticated, and access tokens are short-lived and refreshed automatically.

What about data privacy? Data stays in your UserGuiding project. The AI tool sends queries and receives results. No bulk export or storage happens on the AI side.

Is the data real-time? Live for user, company and material queries. The project-wide overview reads the same pre-aggregated daily metrics as the panel dashboard, so today's numbers appear once that day's rollup has run.

Does it work with ChatGPT or other AI tools? Any client that supports remote MCP servers over Streamable HTTP can connect. Claude (web, desktop and Claude Code), Cursor and OpenAI Codex all do today. For other tools, check whether they support custom or remote MCP connectors.

Can someone break things with write operations? Only within the scopes you approved. Four tools are irreversible (delete_user, reset_user_history, delete_kb_article and delete_product_updates_post) and are marked as destructive so assistants confirm before calling them. If a connection is only for analysis, approve read scopes and nothing else.

Is there a rate limit? Yes, 60 tool calls per minute per project, shared across every connection into that project.