How do I get my Appcues API Key and Secret?

You can generate API keys in the Appcues Studio. Go to **Settings > Integrations > API Keys** to create a new set of credentials.

What is my Appcues Account ID?

Your Account ID is a unique numeric identifier for your Appcues account. You can find it in the URL of your Appcues Studio (e.g., studio.appcues.com/accounts/YOUR_ID) or in your Account Settings.

Does this server support the EU region?

Yes, you can configure the `APPCUES_REGION` environment variable to `eu` if your account is hosted in the Appcues European data center.

Appcues MCP Server for CrewAI 11 tools — connect in under 2 minutes

Name: Appcues
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to Appcues through Vinkius, pass the Edge URL in the `mcps` parameter and every Appcues tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Appcues Specialist",
    goal="Help users interact with Appcues effectively",
    backstory=(
        "You are an expert at leveraging Appcues tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Appcues "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 available tools "
        "and what they can do."
    ),
)

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Appcues MCP Server

The Appcues MCP Server empowers your AI agent to interact directly with your Appcues account. Whether you need to audit your current onboarding flows, manage user segments, or track real-time user activity, this integration provides a seamless natural language interface to your product experience platform.

When paired with CrewAI, Appcues becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Appcues tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

Key Features

Flow Management — List, view, publish, and unpublish flows (in-app experiences) across web and mobile.
User Segmentation — Retrieve and analyze your targeting segments to understand who is seeing your content.
Activity Tracking — Send real-time events and profile updates for immediate targeting and personalization.
Mobile Support — Access specific experiences designed for your mobile applications.
Auditing & Reporting — Quickly check account status, checklists, and experience metadata.

Benefits for Teams

Product Managers — Quickly audit which onboarding flows are active and make changes without leaving your AI workspace.
Growth Engineers — Programmatically track user events to trigger personalized in-app journeys.
Customer Success — View user profiles and segment membership to provide better support and guidance.

The Appcues MCP Server exposes 11 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Appcues to CrewAI via MCP

Follow these steps to integrate the Appcues MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 11 tools from Appcues

Why Use CrewAI with the Appcues MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Appcues through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Appcues + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Appcues MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Appcues for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Appcues, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Appcues tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Appcues against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Appcues MCP Tools for CrewAI (11)

These 11 tools become available when you connect Appcues to CrewAI via MCP:

get_account_details

Verify Appcues account connection

get_flow

Get details for a specific flow

get_segment

Get details for a specific segment

get_user_profile

Retrieve the profile of a specific user

list_checklists

List all checklists configured in the account

list_flows

List all Appcues flows (experiences) for the account

list_mobile_experiences

List mobile-specific experiences

list_segments

List all user segments defined in Appcues

publish_flow

Publish a draft flow

track_user_activity

Use JSON strings for profileUpdate and events. Track real-time events and profile updates for a user

unpublish_flow

Unpublish an active flow

Example Prompts for Appcues in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Appcues immediately.

"List all my active Appcues flows."

"Track a 'clicked_checkout' event for user 'user_123'."

"Show me the details of the segment with ID '998877'."

Troubleshooting Appcues MCP Server with CrewAI

Common issues when connecting Appcues to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Appcues + CrewAI FAQ

Common questions about integrating Appcues MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.