Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 48,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

An MCP server plugin for Claude Code that analyzes local AI session logs to provide coaching on coding patterns, tool usage, and productivity insights via tools and slash commands.

README.md

claude-engineering-coach

A native Claude Code plugin that coaches you on your AI-assisted coding — without leaving the Claude Code terminal. Get usage summaries, anti-pattern coaching, tool comparisons, and flow analysis via MCP tools and /coach:* slash commands. (It can still read Codex / OpenCode / Copilot sessions too, but it runs inside Claude Code.)

Local-only · read-only · zero telemetry.

Reuses the analytics core of Microsoft's AI Engineering Coach — but that is a VS Code / GitHub Copilot extension. This one is built for Claude Code: it ships as a Claude Code plugin, so the coaching lives where you already work. MIT-licensed. Not affiliated with, sponsored by, or endorsed by Microsoft. See NOTICE.

---

What it does

It reads your on-disk AI session logs (e.g. ~/.claude/projects/*/.jsonl) and turns them into actionable coaching:

  • /coach:summary — sessions, output, and your top anti-patterns
  • /coach:improve — prioritized, evidence-backed recommendations
  • /coach:compare — your AI tools side-by-side (sessions, LOC, models, cancel rates)
  • /coach:flow — deep-work scores, best hours, session continuity

Claude can also call the underlying tools on its own — just ask "how was my coding this week, and what should I improve?"

Nothing leaves your machine: the server parses your logs in-process, redacts secrets before any output reaches the model, and never writes to your session files.

---

Install

Requires Node ≥ 18 (the bundled MCP server runs with node). No npm install needed — the server bundle and rule assets are committed.

Easiest — install straight from GitHub (no local path)

In an interactive Claude Code session:

/plugin marketplace add nnhhoang/claude-engineering-coach
/plugin install coach@devempower-coach
/reload-plugins

Here marketplace add points at the GitHub repo (owner/repo), so there is no folder path to fill in. The marketplace name devempower-coach is read from .claude-plugin/marketplace.json; you use it in the install coach@devempower-coach step. Choose a scope when prompted (Local is fine for yourself).

Local dev — clone and load directly

git clone https://github.com/nnhhoang/claude-engineering-coach.git
cd claude-engineering-coach
claude --plugin-dir .

The . means "this folder" — nothing to fill in. Loads the plugin (commands + MCP server) for that session only.

Note: an earlier draft showed /plugin marketplace add /path/to/claude-engineering-coach. That /path/to/... was just a placeholder for "wherever you cloned it" — the two methods above avoid it entirely (one uses owner/repo, the other uses .).

Verify

/mcp

You should see the coach server connected with 13 tools. Then run:

/coach:summary

---

MCP tools (13)

coach_summary, coach_activity, coach_credits, coach_codeProduction, coach_flow, coach_patterns, coach_insights, coach_wellbeing, coach_workflows, coach_harnessComparison, coach_sessions, coach_contextHealth, and coach_reload (re-read logs after new sessions).

When no date range is given, tools default to the last 90 days. Pass fromDate / toDate (ISO YYYY-MM-DD) to widen or narrow.

---

How it works

core/                vendored analytics (parsers, analyzers, 45 rule + 10 metric .md)
  └─ formatters.ts   pure formatter functions
mcp/
  ├─ tool-defs.ts    12 tools (+ 90-day default + secret redaction)
  ├─ analyzer-cache.ts  lazy, cached Analyzer over parseAllLogs(findLogsDirs())
  ├─ server.ts       MCP stdio server (list / call / reload)
  └─ dist/server.mjs committed esbuild bundle (+ rules/ + metrics/ assets)
commands/            /coach:summary · improve · compare · flow
.claude-plugin/      plugin.json + marketplace.json
.mcp.json            registers the bundled "coach" server

The analytics engine is reused verbatim from upstream (it was already VS Code-free). Only the integration layer (mcp/) and packaging are new.

Rebuild after changing mcp/** or re-vendoring core/

npm install   # first time only
npm run build # → mcp/dist/server.mjs (+ copies rule/metric assets)
npm test      # core-smoke, tool-defs, analyzer-cache, server.e2e

The build commits its output (mcp/dist/) so the plugin runs on a fresh clone with only node.

---

Attribution & license

This project vendors the analytics core of microsoft/ai-engineering-coach (MIT). Vendored files under core/ keep their original Microsoft copyright headers; see NOTICE and VENDOR.md for the exact upstream commit.

Licensed under the MIT License. Not affiliated with Microsoft.

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Developer Tools servers.