Bring User Onboarding
to LangChain
Learn how to connect Appcues to LangChain and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Appcues MCP Server?
Connect your Appcues account to any AI agent and take full control of your in-app onboarding and automated user experience orchestration through natural conversation.
What you can do
- Experience Portfolio Orchestration — List and manage your entire portfolio of flows and checklists programmatically, retrieving detailed engagement metadata
- User & Event Intelligence — Programmatically monitor real-time user events and access behavioral metadata to coordinate your engagement strategy
- Segment & Targeting Architecture — Access your complete directory of user segments to coordinate your organizational resource allocation
- Performance Monitoring — Access real-time status updates for active flows and track individual completion metrics directly through your agent for instant reporting
- Operational Monitoring — Verify account-level API connectivity and monitor event ingestion volume directly through your agent for perfectly coordinated service scaling
How it works
1. Subscribe to this server
2. Retrieve your API Key and API Secret from your Appcues dashboard (Settings > API)
3. Start orchestrating your user growth from Claude, Cursor, or any MCP client
No more manual checking of individual flow completion rates or missing critical onboarding drop-offs. Your AI acts as your dedicated experience coordinator and user architect.
Who is this for?
- Product Managers — instantly retrieve experience performance recaps and monitor onboarding health using natural language commands
- Growth Leads — verify individual user metadata and track event history without leaving your creative workspace
- Developers — integrate high-speed Appcues engagement data into custom analytics and CRM tools through simple AI queries
Built-in capabilities (10)
Verify Appcues API connectivity
This action is irreversible. Delete a user from Appcues
Get flow details
Get segment details
Get user profile from Appcues
List all checklists
List all onboarding flows
List all user segments
The flow must be in draft or unpublished state. Publish a flow
Users will no longer see it until republished. Unpublish a flow
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Appcues through native MCP adapters. Connect 10 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Appcues MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Appcues queries for multi-turn workflows
Appcues in LangChain
Appcues and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Appcues to LangChain through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Appcues in LangChain
The Appcues 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. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LangChain only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Appcues for LangChain
Every tool call from LangChain to the Appcues MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Appcues API Key?
Log in to your account, navigate to Settings > API, and copy your unique API Key and Secret from the credentials section.
Can I check flow completion rates via AI?
Yes! The list_flows tool allows your agent to retrieve completion and interaction metadata for all your active experiences.
How do I list my user segments?
Use the list_segments tool to retrieve your complete directory along with the unique identifiers for all managed targeting groups.
How does LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters