parenting-frameworks vs Life Scenario
parenting-frameworks is a plugin bundle for AI coding tools published by ironyjk. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Life Scenario is an MCP server published by lifescenario.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 |  parenting-frameworks |  Life Scenario |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.2.0 Forks (GitHub): 2 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.3.0 No figure published 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 | parenting-frameworks | Life Scenario |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 2 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (lifescenario.ai/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 17 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/ironyjk/parenting-frameworks | Not stated |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days ago |
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
parenting-frameworks
Parenting & Education Framework Guide — 16 frameworks: Positive Discipline (Adler), PET (Gordon), CPS (Greene), Emotion Coaching (Gottman), Triple P, Attachment Parenting (Bowlby/Ainsworth/Siegel), SDT Parenting (Deci/Ryan), Retrieval Practice, Growth Mindset (Dweck), UbD (Wiggins/McTighe), PBL, Montessori, DAP (NAEYC), UDL, Formative Assessment (Black/Wiliam), Differentiated Instruction (Tomlinson). Korean parenting/education context. Invoke /parenting.
Life Scenario
For parents and teachers: SEL trait guides, practice scenarios, what-to-say guides (ages 6-14).
How to run each
parenting-frameworks As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install parenting-frameworks@claude-communityLife Scenario As a remote MCP server
claude mcp add --transport http info https://lifescenario.ai/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Life Scenario 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: parenting-frameworks · What it can do: Life Scenario · 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 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.