Appcues MCP. Manage flows and track user activity with simple commands.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Appcues MCP lets your AI client audit product experiences, manage in-app content, and track real-time user behavior directly through conversation.
You can list existing flows, retrieve detailed user profiles, define target segments, and fire custom events—all without leaving your agent workspace.
What your AI agents can do
Get account details
Verifies your connection credentials and basic account setup information for Appcues.
Get flow
Retrieves the detailed content and settings for a single, specific in-app experience flow.
Get segment
Gets all details about one defined user segment, including its rules and member count.
List, view, publish, or unpublish entire flows of in-app content for both web and mobile platforms.
Retrieve details on defined user segments or pull a specific user's complete profile data to understand their journey.
Send custom events and update user profiles as they interact with your product, triggering immediate personalization logic.
Check account status, view configured checklists, or retrieve specific flow metadata for auditing purposes.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Appcues MCP: 11 Tools Available
Use these tools to list flows, check segments, retrieve user profiles, and fire custom events—all through your AI client.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Appcues on Vinkius019d754fget account details
Verifies your connection credentials and basic account setup information for Appcues.
019d754fget flow
Retrieves the detailed content and settings for a single, specific in-app experience flow.
019d754fget segment
Gets all details about one defined user segment, including its rules and member count.
019d754fget user profile
Pulls the current profile information for a specific end-user based on their ID.
019d754flist checklists
Lists all account checklists configured in Appcues, helping you audit setup requirements.
019d754flist flows
Gets a complete list of every flow (in-app experience) available across your entire Appcues account.
019d754flist mobile experiences
Retrieves a separate list containing only the experiences designed specifically for mobile apps.
019d754flist segments
Provides a master list of all user segments you have defined within your account.
019d754fpublish flow
Takes a draft flow and publishes it, making the in-app experience live for users.
019d754ftrack user activity
Sends real-time events or updates a user's profile data immediately as they use your product.
019d754funpublish flow
Removes an active flow from circulation, taking the in-app content offline until you publish it again.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Appcues, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Appcues. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 11 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Dealing with content lifecycles is always a mess of clicks and tabs.
Today, releasing or retiring in-app content means logging into the platform. You have to click through flow lists, manually confirm if a draft is ready, check its status, and then hit publish. If you need to pause something quickly during an emergency, it's another deep dive into settings, often involving copy-pasting IDs just to disable it.
With this MCP, that entire process shrinks down to conversation. You tell your agent what needs to change—like 'Pause the onboarding flow for Enterprise users.' The agent handles the complex steps of finding the right content and running `unpublish_flow`. It's instant status changes based on natural language commands.
Publishing and managing flows using `list_flows` and `publish_flow`
Manually, you have to navigate to the flow editor, check all versions, ensure no conflicting content exists, and finally hit publish. This is slow, error-prone work that stops your team in its tracks.
Now? You just ask it. The agent pulls the list of flows using `list_flows`, confirms the draft status with `get_flow` details, and publishes everything you want with a single command. It's reliable.
What you can do with this MCP connector
You're building a feature, but you need to know exactly who sees it and when. This integration gives your AI client direct access to the Appcues account. It lets you check which onboarding flows are active for web versus mobile. Need to understand your users better? You can pull up specific segments or retrieve any user's full profile details instantly.
Furthermore, if a critical event happens—like a user clicking 'purchase'—you can track that activity right away to trigger personalization. If you connect this through the Vinkius catalog, your agent handles all the complex data calls, letting you focus on what’s next for the product.
It’s about asking questions like, “Which flows should we pause?” or “Show me all users who signed up last week and haven't seen the pricing page.” You get structured answers that let you take immediate action.
019d754f-cd7a-724e-b24b-72e6c8695e54 
How Appcues MCP Works
- 1 Tell your AI client what you want to do. For example: “List all active app experiences and check the profile of user X.”
- 2 Your agent calls the necessary tools, pulling specific data points like flow lists or segment IDs.
- 3 The system returns structured data that lets you confirm the status, receive a list of drafts, or execute an action like publishing content.
The bottom line is: your AI client executes complex Appcues tasks using natural language input, giving you actionable data without needing to log into the platform itself.
Who Is Appcues MCP For?
Product Managers who need to audit content status pre-launch; Growth Engineers who have to programmatically track user actions in real time; and Customer Success teams that need instant visibility into a customer's segment membership.
Uses this MCP to check which onboarding flows are currently live, or to unpublish a flow quickly because it contains outdated information.
Runs the tool to track user activity after implementing a new feature, ensuring custom events fire correctly for immediate personalization logic.
Uses the segment and profile tools to view a user's history and membership status so they can guide the client with specific context.
What Changes When You Connect
- Product Managers save time by auditing flow status. Instead of navigating multiple dashboards, you can use
list_flowsto see all available experiences and check drafts before publishing. - Growth Engineers gain programmatic control over user behavior. Use
track_user_activityto fire custom events precisely when a user reaches a key milestone in their journey. - You instantly understand your audience. By listing segments via
list_segmentsor pulling data withget_segment, you know exactly who is seeing specific content. - Auditing account health becomes simple. Running
list_checklistsensures all the necessary setup steps are complete, preventing deployment delays before launch. - The integration handles mobile complexity for you. You can access dedicated experiences just for your native apps using
list_mobile_experiences, keeping web and mobile content separate.
Real-World Use Cases
Rolling out a new feature announcement
A PM needs to announce 'Feature X' across the app. They ask their agent to list all flows, identify the draft for Feature X, and then execute publish_flow so everyone sees it immediately.
Debugging a personalization issue
A Growth Engineer suspects users aren't seeing personalized content. They ask the agent to first run get_user_profile for a test user, and then confirm which segment that profile belongs to using get_segment.
Analyzing failed conversion paths
A Data Analyst wants to know what happened when users abandon the cart. They ask the agent to track a 'cart_abandoned' event via track_user_activity, tying it to the user’s ID.
Decommissioning old content
The team retired an outdated onboarding flow. Instead of manually finding and disabling it, they ask the agent to find the flow using get_flow details and then execute unpublish_flow.
The Tradeoffs
Trying to publish a non-existent draft
A user tries to manually tell their agent, 'Publish the flow called Q3 Launch.' but they don't know the exact name or if it's even in draft status.
→
First, run list_flows to see all available experience names. Then use get_flow on the correct ID before attempting to publish_flow.
Tracking events without a user context
Sending an event like 'checkout_started' but forgetting which user performed the action, so the data is useless.
→
Always retrieve the necessary identity first. Use get_user_profile to pull the user ID and key attributes before calling track_user_activity. The profile ensures accurate attribution.
Assuming account setup is fine
A developer starts working on new flows without checking if mandatory Appcues checklists (like analytics integration) have been completed.
→
Always start by running list_checklists and then reviewing the details via get_account_details. This confirms your environment is ready for development.
When It Fits, When It Doesn't
Use this MCP if your goal is structured data manipulation, auditing content status, or programmatically updating user records. You need to run commands like list_flows and then conditionally use publish_flow based on the results of a segment check (get_segment). Don't use it if all you want is a visual dashboard view—this MCP doesn't replace your Appcues UI. If your core need is just seeing traffic metrics, look for an analytics-type connector instead.
Common Questions About Appcues MCP
How do I find out what flows are available in Appcues using `list_flows`? +
list_flows returns an array of all app experiences configured for your account. This list includes the names, IDs, and current status (draft or published) of every flow.
What is the difference between `get_flow` and `list_flows`? +
list_flows gives you a high-level overview—it's a list. get_flow, though, retrieves the full, granular details for one specific flow ID, including its content structure.
Can I use `track_user_activity` to measure button clicks? +
Yes, you send custom events via track_user_activity. You define the event name (like 'clicked_buy_button') and include relevant data in JSON strings so your agent tracks it correctly.
How do I see which users are part of a specific group using `list_segments`? +
You first run list_segments to get the segment ID, then you use get_segment with that ID. This reveals the rules and currently included members for that user group.
Should I call `get_account_details` before making changes? +
Absolutely. Running get_account_details first verifies your connection status and ensures you're operating within the correct permissions, preventing unnecessary tool failures later on.
I just finished editing a flow; how do I make sure it's live for users using `publish_flow`? +
You must use the publish_flow tool to activate your changes. This moves the experience from draft status, making it visible across web and mobile platforms immediately. Publishing ensures that any recent edits—like text or new steps—are picked up by the live user journey.
When should I use `get_user_profile` instead of relying on a segment from `list_segments`? +
You use get_user_profile when you need specific details about one person, like their last login or email. Use list_segments only to see group membership; it tells you who belongs to a defined category, not the individual data points.
What information does calling `list_checklists` provide regarding my Appcues setup? +
The list_checklists tool gives you an audit of required account metadata and steps. This is useful for product managers who need to verify if all necessary system settings or experience components are configured correctly across the platform.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.