Bring Product Adoption
to AutoGen
Learn how to connect Pendo to AutoGen 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 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 AutoGen?
AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Pendo tools. Connect 10 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.
- —
Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Pendo tools to solve complex tasks
- —
Role-based architecture lets you assign Pendo tool access to specific agents. a data analyst queries while a reviewer validates
- —
Human-in-the-loop support: agents can pause for human approval before executing sensitive Pendo tool calls
- —
Code execution sandbox: AutoGen agents can write and run code that processes Pendo tool responses in an isolated environment
Pendo in AutoGen
Pendo and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Pendo to AutoGen 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 AutoGen
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 AutoGen 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 AutoGen
Every tool call from AutoGen 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 AutoGen connect to MCP servers?
Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Pendo tools during their conversation turns.
Can different agents have different MCP tool access?
Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
Does AutoGen support human approval for tool calls?
Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.
McpWorkbench not found
Install: pip install "autogen-ext[mcp]"
