Productivity & Project Management · Userflow + Claude
Userflow MCP with Claude: Automate Product Onboarding Without Coding
The short answer
Claude connects to Userflow through the Model Context Protocol (MCP), a secure standard that lets Claude read and act within the tool. Using an API key, Claude can help launch product tours, manage onboarding checklists, update user segments and automate in-app messages, with permissions your team controls and approvals on consequential changes.
What is Userflow?
Userflow is user onboarding software that helps product and growth teams build product tours and onboarding checklists inside their applications. It lets teams guide new users and drive feature adoption without writing code. It is typically used by product managers, customer success teams, marketers and developers who want users to reach value faster and stay engaged with the product.
How Claude connects to Userflow through MCP
The Model Context Protocol is an open standard that works like a universal adapter between Claude and other software. It lets Claude use a tool securely, reading information and taking actions, with permissions the organisation controls. Instead of copying data between systems by hand, your team can describe what they need in plain language.
Once Claude is connected to Userflow using an API key, it can typically look up user segments, review existing tours and checklists, help draft and launch new product tours, update onboarding checklists and set up automated in-app messages. Each request is handled within the access granted to that key.
Permissions and approvals keep people in charge. Access is limited to the actions your team needs, and the API key can be scoped, rotated and revoked at any time. Consequential changes such as launching a tour to all users can be routed to a named person for sign-off before they go live, and audit logs record what was changed.
What you can automate
Launching a new feature tour
When a product manager ships a new feature, Claude can help draft a short product tour, select the relevant user segment and prepare it for review. The product team approves the final version before it reaches customers. This shortens the gap between release day and user awareness, without waiting on a developer for each change.
Maintaining onboarding checklists
Customer success teams often need onboarding checklists updated as products and plans change. Claude can help review existing checklists, suggest edits in plain language and apply approved updates, so new customers always see current steps and fewer get stuck during setup.
Segmenting users for targeted guidance
Marketing and growth teams can ask Claude to update user segments based on behaviour, such as accounts that have not completed setup within a set number of days. Those segments then decide who sees which tour or message, making guidance more relevant and less intrusive.
Automating in-app messages
Teams can set up in-app messages that respond to user actions, such as a tip after a first project is created or a reminder when a trial is nearing its end. Claude can help draft the wording, configure the trigger and report back, while the team keeps control over tone and timing.
Reviewing adoption and handing over issues
When adoption of a feature is low, Claude can help summarise which tours were viewed, which checklist steps were skipped and which segments are stuck. Findings can then be passed to the support or product team as a ticket, so follow-up happens in the usual workflow.
An end-to-end workflow: New customer onboarding with support handover
TriggerA new account is created in the company CRM after a successful purchase.
Claude reads the new account details from the CRM and assigns the customer to the correct Userflow segment, such as plan type or industry.
Claude starts the matching onboarding checklist in Userflow so the customer sees the first setup steps when they sign in.
If the customer has not completed key steps within three days, Claude flags the account and drafts a reminder in-app message for approval.
Once an approved reminder is sent, Claude logs the activity against the account in the CRM.
If the customer still has not completed setup after seven days, Claude opens a ticket for the customer success team with a summary of progress.
OutcomeNew customers reach their first useful result sooner, the customer success team receives early warnings about stalled accounts, and every step is recorded in the CRM. Typical results vary by product and team.
How we set it up
Free automation audit
We review how your team currently runs product tours, onboarding and in-app messaging, and identify the workflows worth automating first. You leave with a clear plan and no obligation.
Secure connection with an API key
We connect Claude to Userflow using an API key, the sign-in method the tool supports. The key is created with the access your workflows need, stored securely and can be rotated or revoked at any time.
Workflow design across your systems
We design the end-to-end workflow across Userflow and your other systems, such as Microsoft 365, CRM, ERP or ticketing. Approval points are set for any change that reaches users.
Testing and launch with monitoring
We test the workflow against past onboarding cases, then launch with audit logs and monitoring so you can see every action Claude takes and how it performs.
Team training and handover
We train product, marketing and customer success staff to request changes in plain language, review Claude's suggestions and manage approvals, so your team owns the workflow from day one.
Who benefits
- Product managers
- Launch feature tours faster, with drafts prepared for review rather than built from scratch each time.
- Customer success leads
- Receive early warnings about stalled accounts and keep onboarding checklists current.
- Growth and marketing teams
- Update user segments and in-app messages through plain-language requests instead of waiting on developers.
- IT and security heads
- Control exactly what Claude can access through a scoped API key, with audit logs and clear approval points.
Security and control
- Scope the API key to only the actions each workflow needs, and rotate it on a regular schedule.
- Require named approval for any change that reaches live users, such as launching a tour to a full segment.
- Keep audit logs of every change Claude makes, so the team can review and reverse actions.
- Test workflows on past onboarding cases before launch, and monitor them after going live.
- Store credentials in a managed secrets store and never place them in shared documents or chat messages.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can use Claude with Userflow under their existing data protection frameworks, with access controlled through scoped keys. Indian organisations are supported in line with the Digital Personal Data Protection Act, 2023. Companies in the UAE and Saudi Arabia are supported in line with local data protection laws. The hosting region for custom applications is chosen to meet your legal and contractual requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Userflow MCP server do?
The Userflow MCP server acts as a secure bridge between Claude and your Userflow account. It lets Claude work with product tours, onboarding checklists, user segments and in-app messages through natural language requests. Access is limited to what the connected API key allows, so the server only does what your team has permitted.
Is connecting Claude to Userflow secure?
The connection uses an API key, which can be scoped to specific permissions, rotated regularly and revoked instantly. Changes that reach users can require human approval, and audit logs record each action. Credentials are stored in a managed secrets store rather than shared directly.
What can Claude do with Userflow once connected?
Typically, Claude can help launch product tours, manage onboarding checklists, update user segments and set up automated in-app messages. It can also summarise adoption data and draft content for review. The exact actions available depend on the permissions given to the API key.
How long does setup take?
Setup time depends on how many workflows are in scope and how many systems need to be connected. A focused connection with one or two workflows is often completed within a few weeks, including testing and training. We confirm timelines after the free automation audit.
What plan or permissions do I need?
You need a Userflow account with an API key that has the permissions your workflows require. Generally, the key should be created by an administrator with access limited to the necessary actions. We will confirm the exact requirements for your account during the audit.