How to Use the Appcues MCP in CrewAI

Q: How does CrewAI verify the Appcues connection before running a task?

The lead agent runs checkappcuesstatus at the start of the crew's execution block. If the connection fails, the crew halts the mission and reports the API error.

Q: Can a crew automatically unpublish broken Appcues flows?

Yes, your monitoring agent can call unpublishflow if it detects high drop-off rates or broken links. This protects your user experience from broken onboarding steps.

Run autonomous CrewAI agent crews to monitor, audit, and update your Appcues onboarding flows.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Appcues MCP to CrewAI

Create your Vinkius account to connect Appcues to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Appcues with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Autonomous onboarding audits with CrewAI

This MCP Server provides `list_flows` to your CrewAI agent team so they can audit your onboarding experience without human intervention. A researcher agent pulls the active flows while an analyst agent flags outdated copy. Once the crew identifies a flow that needs updating, a writer agent drafts the new content. The supervisor agent then runs `unpublish_flow` to take the old version offline until the changes are approved.

Multi-agent user profile cleanup

This MCP Server exposes `get_user` to help your crew identify inactive trial accounts that are skewing your metrics. The research agent scans your database, identifies the dead accounts, and passes the list to the cleanup agent. The cleanup agent then runs `delete_user` to remove those profiles from Appcues. This coordinated effort keeps your billing tier accurate without requiring manual CSV exports.

Continuous segment monitoring and reporting

This MCP Server uses `list_segments` to let your CrewAI agents track user distribution across your onboarding funnels. One agent extracts the segment sizes while another drafts a weekly performance summary for your product team. If the crew notices a segment shrinking unexpectedly, it uses `get_segment` to inspect the exact rules. The agents then flag the anomaly in your team chat so you can fix the underlying tracking issue.

Setup guide

Set up Appcues MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Appcues tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Appcues Analyst",
    goal="Access and analyze Appcues data via MCP.",
    backstory="Expert analyst with direct Appcues access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Appcues transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Appcues Analyst",
        goal="Access and analyze Appcues data via MCP.",
        backstory="Expert analyst with direct Appcues access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Appcues transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Appcues now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Appcues MCP in CrewAI

You assign different tools to different agents. For example, one agent uses `get_flow` to analyze the steps, while a supervisor agent uses `publish_flow` to push the finalized updates.

Yes, you can. Use CrewAI's tool filter options to expose only safe tools like `list_checklists` to your research agents while keeping write tools restricted.

The lead agent runs `check_appcues_status` at the start of the crew's execution block. If the connection fails, the crew halts the mission and reports the API error.

Yes, your monitoring agent can call `unpublish_flow` if it detects high drop-off rates or broken links. This protects your user experience from broken onboarding steps.

It does not store them. The server acts as an ephemeral bridge, passing Appcues user profiles and checklist details directly to your CrewAI agents before wiping its memory clean.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript