UserGuiding MCP Use Cases and Example Prompts

Once your assistant is connected, the fastest way to learn what the MCP Server can do is to steal a prompt. Everything below is written the way you would type it into Claude, Cursor or Codex. The tools named after each group are what the assistant reaches for, so you can look them up in the UserGuiding MCP Tool Reference.

Not connected yet? Start with Setting Up the UserGuiding MCP Server.

Product and growth: how is the product doing

Start wide, then drill in. One question about the whole project usually turns into three follow-ups about a single guide, and the assistant chains them without you naming a single tool.

• "Give me an engagement summary for the last 30 days and tell me what moved compared to the two weeks before."
• "Which guides got the most plays last month, and which of them has the worst completion rate?"
• "Show me the step funnel for the Onboarding guide over the last 90 days. Where do people drop off?"
• "How many users adopted the export_csv feature this quarter, and is it sticky or a one-time thing?"
• "Plot weekly usage of the new dashboard event since we launched it and tell me whether it is still growing."

Tools: get_project_overview, get_material_performance, get_guide_step_funnel, analyze_feature_adoption, get_event_timeseries, get_goal_performance.

Activation and retention: who sticks around

Cohort questions are the ones spreadsheets are worst at, and they are one MCP call each.

• "Build a weekly retention matrix for users who first showed up in the last three months. What does the average curve look like?"
• "Do users who completed the onboarding checklist retain better than the ones who did not?"
• "Which of our goals are actually being reached, and which ones has nobody hit this quarter?"
• "Compare the completion rate of every checklist we have, best to worst."

Tools: analyze_retention, get_checklist_item_stats, get_goal_performance, get_material_performance.

Segmentation without the filter builder

Describe the audience in a sentence. The assistant discovers your attribute and event names first, sizes the audience, then saves the segment once you agree with the number.

• "How many users are on the Pro plan, signed up in the last 30 days, and fired export_csv at least once?"
• "Create a segment called Power Users: enterprise plan, more than ten sessions, and completed the Onboarding guide."
• "Create a segment for accounts that have either churn_risk set to true or have not been seen in 30 days, and are on a paid plan."
• "Update the Trial Users segment so it also excludes anyone who already upgraded."
• "Take the Enterprise Admins segment and tell me what its members actually interacted with last month."

Tools: list_attributes, list_events, get_user_count, create_segment, update_segment, list_segments, get_segment_user_interactions.

Tip: ask for the count before you ask for the segment. It costs one call and catches a misunderstood filter before it becomes a saved audience.

Customer Success: account health and pre-call research

Everything you would normally open four tabs for, in one prompt before a renewal call.

• "Look up [email protected]. What plan are they on, when did they sign up, and what have they done in the product this week?"
• "Give me the engagement health for Acme Corp this month against last month. Are they going quiet?"
• "Which features has Acme Corp's team actually used in the last 60 days, and who are their most active members?"
• "Find users on the Starter plan who hit api_rate_limit_hit more than ten times this month. Those are my upsell calls."

Tools: get_user, get_user_activities, get_company, get_company_engagement, search_users, list_users_by_event.

Support: full context on a ticket

Cuts the two or three back-and-forth messages that usually start with "what plan are you on?".

• "Pull the full profile for [email protected] so I can see their plan, the features they use and their recent activity."
• "Did this user ever see the Billing Update banner, and did they dismiss it?"
• "Search the knowledge base for articles about SSO setup and give me the two best links to send."
• "This customer says onboarding is stuck. Reset their UserGuiding history so they see it again."

Tools: get_user, get_user_activities, search_kb_articles, get_kb_article, reset_user_history.

Feedback and surveys

• "Summarise the NPS survey for the last quarter: response rate, score distribution and where people dropped off."
• "Read the free-text answers from the last 50 responses to the Churn Reasons survey and group them into themes."
• "Which of our surveys has the worst response rate this month?"

Tools: get_survey_report, list_survey_responses, get_material_performance.

Knowledge Base: write, tidy and migrate

The Knowledge Base tools cover the whole structure, not just article bodies, so "reorganise the help center" is a real prompt rather than an afternoon of clicking.

• "Draft a new article about our new SSO setup, in the same tone as the existing articles in the Getting Started category."
• "Article 299 is out of date since we shipped the new indexing options. Update it."
• "Show me the help center structure and tell me which categories have no Portuguese titles yet."
• "Create a Billing sub-category under Settings and move these five articles into it."
• "Our old help center is at support.example.com. Work out what platform it runs on so we can plan the migration."

Tools: search_kb_articles, get_kb_article, create_kb_article, update_kb_article, list_kb_categories, create_kb_sub_category, assign_kb_articles, detect_kb_platform.

Articles written this way land as drafts. You review and publish them from the panel, so nothing reaches your help center without a human clicking Publish.

Product Updates: announce what shipped

• "Read our last five product update posts, then draft one about the new dashboard filters in the same voice."
• "Which product update posts got the most reads last month?"
• "How many times was the Product Updates page opened in the last 30 days?"
• "Add the Beta label to the post about the new API and fix the typo in the second paragraph."

Tools: list_product_updates_posts, create_product_updates_post, update_product_updates_post, get_material_performance, count_events.

Roadmap and feature requests: clear the inbox

• "How many feature requests are waiting for moderation, and what are the roadmap columns?"
• "Show me the pending feature requests sorted by votes and summarise the themes."
• "Approve the top three, reject anything that is obviously spam, and tell me what you did."
• "What is currently on the public roadmap board, column by column?"

Tools: get_roadmap_overview, list_feature_requests, get_feature_request, approve_feature_request, reject_feature_request, list_roadmap_items.

Getting better answers

• Name the window. "Last 30 days" or an explicit date range beats "recently". Ranges are capped at one year.
• Ask for the count before the list. Sizing an audience is one call. Fetching thousands of profiles is not, and long result sets get trimmed.
• Say people or events. "How many users adopted X" and "how many times did X happen" are different questions with different tools, and the answers are rarely the same number.
• Let it discover names. If you are not sure whether the event is signup or signed_up, ask the assistant to list the events first.
• Confirm before writes. Ask it to show you the segment filters, the article draft or the list of requests it plans to approve before it commits.

Related articles

• UserGuiding MCP Server
• Setting Up the UserGuiding MCP Server
• UserGuiding MCP Tool Reference