Log inSubmit server
Devcoach logo

Devcoach

Local MCP coaching that delivers one contextual technical lesson after selected AI-assisted development tasks.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Devcoach

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "devcoach": {
      "command": "npx",
      "args": [
        "-y",
        "devcoach"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The devcoach MCP server provides progressive, in-context technical coaching inside MCP-compatible developer tools. It runs locally as a stdio server, stores coaching history in SQLite at ~/.devcoach/coaching.db, and uses pacing, topic selection, and lesson logging to avoid repetition. Reach for it when you want to practice validating AI-generated work without sending data to a remote service. Node.js 24 or later is required for the standard installation.

Use cases

  • Add contextual lessons after AI-assisted coding tasks
  • Track completed lessons in a local SQLite database
  • Open a local coaching dashboard from an agent
  • Share or import lesson data between local environments

Key features

  • Progressive lesson selection based on task context
  • Pacing and rate limiting for lesson delivery
  • Local SQLite storage at ~/.devcoach/coaching.db
  • MCP tools for logging, skipping, and opening the UI
  • CLI commands for lessons, statistics, sharing, importing, and backups
  • Claude Code plugin with coaching hooks and skill

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 42d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 1d ago via OSV.dev · devcoach (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars5Stargazers on the source repository.
npm downloads4.6kPackage downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.

How Devcoach works

What devcoach MCP server does

The devcoach MCP server adds short technical lessons to an AI-assisted development workflow. After a task is completed, it checks whether coaching is due, determines whether the work is technical, selects a topic and depth, and records the lesson. The intended result is a brief prompt tied to the work that just happened rather than a separate, generic tutorial.

All coaching data remains on the local machine. The server uses one SQLite database at ~/.devcoach/coaching.db; the project states that it does not use telemetry, accounts, or outbound calls. This makes it suitable for developers who want local learning history alongside their agent sessions.

How it works

The devcoach MCP server uses an MCP skill and, where configured, a stop hook. Completed tasks first pass through pacing and rate-limit checks. If a lesson is not due, the workflow stays silent and increments its counter. When coaching is due, the skill checks whether the task involved technical work. Non-technical work is skipped; eligible work results in topic selection, depth calibration, lesson logging, and a lesson card.

The lesson can prompt the developer for feedback such as whether it was understood. The documented flow resets the counter after a lesson and re-arms pacing after a skipped task. This approach is intended to limit interruptions while still making coaching part of normal agent use.

Setup and configuration

The standard package runs locally as a stdio MCP server and requires Node.js 24 or newer because it uses the embedded node:sqlite module. With a compatible client, the documented command is npx -y devcoach install; restart the agent afterward. Homebrew installation is available for macOS and Linux and also provides the devcoach command-line interface.

Claude Code users can install the provided plugin, which bundles the MCP server, automatic-coaching stop hooks, and skill. The plugin should not be combined with devcoach install, because both would register the hooks. Claude Desktop users can instead install the supplied .mcpb extension; that bundle uses Claude Desktop's runtime and does not require Node or a terminal.

The project also lists the server in the official MCP Registry under io.github.UltimaPhoenix/devcoach.

Tools and capabilities

The documented MCP tools and related commands include:

  • log_lesson records a selected lesson.
  • skip_lesson handles work that should not receive a lesson.
  • open_ui opens the web dashboard.
  • The CLI supports dashboard access, lesson and statistics views, sharing and importing lessons, and database backup.

Claude Code users can also access the dashboard with /devcoach:ui, share or import lessons, and turn a lesson they could not follow into a step-by-step course through /devcoach:course. These plugin commands are separate from the core lesson-selection flow.

Limitations and notes

The server is local and stores its state in a SQLite file on the machine where the agent runs. It is therefore not presented as a hosted, shared coaching service. Automatic lesson delivery depends on the client integration and its hooks or plugin support; simply connecting an MCP client does not imply that every client provides the same automation.

Gemini CLI and Codex CLI are identified as beta integrations in the README, and the Claude Desktop extension is also marked beta. The Claude Desktop extension is self-signed and installs as an unverified publisher. The project is licensed under AGPL-3.0.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Devcoach

devcoach is an MCP server that connects AI coding clients such as Claude Code, Claude Desktop, Cursor, Windsurf, Gemini CLI, and Codex CLI to local technical coaching. Its main tools include log_lesson, skip_lesson, and open_ui, with lesson history stored in a local SQLite database.

Install it with npx using `npx -y devcoach install`, then restart your agent. The standard package requires Node.js 24 or newer. Homebrew, the Claude Code plugin, the Claude Desktop `.mcpb` extension, and MCP Registry installation are also documented options.

Yes, devcoach lists Cursor among its compatible MCP clients. It runs as a local stdio MCP server, while automatic lesson delivery depends on the client-specific setup and supported hooks or skills.

devcoach stores its data locally in `~/.devcoach/coaching.db`, a SQLite file on the machine running the agent.

No, devcoach does not support claude.ai web. The README identifies it as a local stdio server, while claude.ai web supports hosted or remote connectors.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDevcoach AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/devcoach?style=directory)](https://allmcps.com/mcp/devcoach)
HTML Embed
<a href="https://allmcps.com/mcp/devcoach"><img src="https://allmcps.com/api/badge/devcoach?style=directory" alt="Devcoach on AllMCPs" /></a>