Ext Ops Panel
Open dashboard
Comparison

sensei vs devcoach

sensei is a plugin bundle for AI coding tools published by jreynolds-dev. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). devcoach is an MCP server published by UltimaPhoenix. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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

Where each is published
Marketplacesenseidevcoach
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.7.1
Downloads/month (npm): 6 104
Downloads/week (npm): 835
Forks (GitHub): 0
Stars (GitHub): 5
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

sensei vs devcoach
Factsenseidevcoach
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)5 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (devcoach)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)14Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/jreynolds-dev/senseigithub.com/ultimaphoenix/dev-coach
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

sensei

In its own words, on Claude Code: claude-plugins-community:

Sensei is a Claude Code plugin that turns any project into a guided learning environment. It installs a persistent AI mentor — selectable between Master Splinter and Gandalf — that teaches through the Socratic method rather than serving direct answers. Key behaviors: Code gate — refuses to give code unless the student uses a character-specific safeword or demo trigger - Session lifecycle — /dojo-open sets a micro-goal, /pizza-time closes the session and updates progress tracking - Spaced repetition — tracks concepts introduced, practiced, and mastered across sessions - Character integrity — hooks enforce voice and teaching stance across every message, preventing drift

devcoach

In its own words, on Official MCP Registry:

Progressive in-context technical coaching in your AI agent — one local, free lesson per task.

How to run each

sensei As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install sensei@claude-community

devcoach As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio devcoach -- npx -y devcoach

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

Neither one's marketplaces publish the settings it asks for.

What it can do: sensei · What it can do: devcoach · 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.

Where the data comes from: how the catalog is built