ai-adoption-playbook vs New-Term Radar
ai-adoption-playbook is a plugin bundle for AI coding tools published by adimango. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). New-Term Radar is an MCP server published by zhuyansen. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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 |  ai-adoption-playbook |  New-Term Radar |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.2.0 Forks (GitHub): 2 Stars (GitHub): 23 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.6.1 Downloads/month (PyPI): 0 Downloads/week (PyPI): 444 Forks (GitHub): 591 Stars (GitHub): 1 902 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 | ai-adoption-playbook | New-Term Radar |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 23 (worse) | 1 902 (better) |
| Forks (GitHub) (differs) | 2 (worse) | 591 (better) |
| Last release (differs) | Not published | 2026-10-28 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (new-term-radar) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 2 |
| Parts of the bundle (differs) | 24 | 4 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/adimango/ai-adoption-playbook | github.com/zhuyansen/new-term-radar |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen (differs) | 2026-10-11 | 2026-10-18 |
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
ai-adoption-playbook
Structured AI adoption framework for leaders — diagnostic assessments, blocker analysis, rollout plans, and board-ready narratives
New-Term Radar
New AI model, product and repo names as they surface, and the search terms behind them, sized.
How to run each
ai-adoption-playbook As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install ai-adoption-playbook@claude-communityNew-Term Radar As a local MCP server: PyPI package
claude mcp add --env "AISA_API_KEY=<YOUR_AISA_API_KEY>" --env "GOANYAPI_API_KEY=<YOUR_GOANYAPI_API_KEY>" --transport stdio new-term-radar -- uvx --with mcp new-term-radar mcpRequires: AISA_API_KEY (secret), GOANYAPI_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of ai-adoption-playbook publish no settings it asks for, so we do not compare settings.
What it can do: ai-adoption-playbook · What it can do: New-Term Radar · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/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.