Bring Product Adoption
to CrewAI
Learn how to connect Pendo to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
What is the Pendo MCP Server?
Connect your Pendo subscription to any AI agent and take full control of your product adoption and user engagement workflows through natural conversation.
What you can do
- Guide Management — List all in-app guides and retrieve detailed metadata and performance metrics.
- User & Account Insights — Look up detailed profiles for visitors and accounts to understand their journey.
- Product Tagging Auditing — List defined pages and features to verify your product instrumentation.
- Metadata Schema Discovery — Retrieve schemas for visitor and account metadata to understand available data points.
- Segment Overview — List saved user segments to maintain visibility over your audience targeting.
How it works
1. Subscribe to this server
2. Enter your Pendo Integration Key
3. Start optimizing your product experience from Claude, Cursor, or any MCP client
Who is this for?
- Product Managers — quickly check guide performance or verify if a feature is correctly tagged.
- Customer Success Managers — lookup visitor activity and account metadata during high-pressure support cases.
- Growth Engineers — audit segments and metadata schemas while implementing new tracking events.
Built-in capabilities (10)
Get details for a specific account
Get details for a specific guide
Get performance metrics for a guide
Get details for a specific visitor
List applications tracked in the Pendo subscription
List tagged features
) defined in Pendo. List Pendo guides
List metadata schema definitions
List tagged pages
List saved user segments
Why CrewAI?
When paired with CrewAI, Pendo becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Pendo tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
Pendo in CrewAI
Pendo and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Pendo to CrewAI 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 Pendo in CrewAI
The Pendo 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 CrewAI 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
Pendo for CrewAI
Every tool call from CrewAI to the Pendo 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 Pendo Integration Key?
In Pendo, navigate to Settings > Integrations. There you can find or generate your Integration Key for API access.
Can I see real-time statistics for my guides?
Yes! Use the get_pendo_guide_metrics tool with a Guide ID to retrieve live data on views, clicks, and completion rates.
Does this support looking up individual user metadata?
Absolutely. Use the get_pendo_visitor tool to retrieve all identified properties, account association, and activity history for a specific user ID.
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.
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.