Pendo Orchestrate vs dev.ascendkit/ascendkit
Pendo Orchestrate is a plugin bundle for AI coding tools published by pendo-io. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins). dev.ascendkit/ascendkit is an MCP server published by ascendkit.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Pendo Orchestrate | |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 1.0.0 Forks (GitHub): 5 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Claude: knowledge-work-plugins | Listed Version: 1.0.0 Forks (GitHub): 5 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.22 Downloads/month (npm): 205 Downloads/week (npm): 20 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Pendo Orchestrate | dev.ascendkit/ascendkit |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 5 | No figure on GitHub |
| Last release (differs) | 2026-10-16 | Not published |
| Where it runs (differs) | Remote server (app.pendo.io/mcp/v0/shttp) | On your machine (@ascendkit/cli) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/pendo-io/claude-pendo-plugin | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago, requires a key | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Pendo Orchestrate
Create, configure and edit draft Pendo Orchestrate email journeys, including multi-email and conditional split flows, via the Pendo connector. Journeys stay in draft; activation happens in the Orchestrate UI.
dev.ascendkit/ascendkit
Auth, email, journeys, surveys, webhooks, and analytics for SaaS in one project, one API key.
How to run each
Pendo Orchestrate As a Claude Code plugin
/plugin install pendo-orchestrate@claude-plugins-officialdev.ascendkit/ascendkit As a local MCP server: npm package
claude mcp add --transport stdio ascendkit -- npx -y -p @ascendkit/cli ascendkit-mcp @ascendkit/cliCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Pendo Orchestrate has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Pendo Orchestrate · What it can do: dev.ascendkit/ascendkit · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.