codebase-mcp

2026-03-05 ~ 2026-03-31 · 26 days

Solo Burnout

An ambitious AI context generator, never released to the wild despite a 'publish' job configuration

“AI's perfect brain, without a body to serve”

Death Type

Solo Burnout (Abrupt Cessation)

A solo developer, 'Dipanshu-js', crafted 'at least 10 commits' to build a complex CLI, server, and VS Code extension in just 26 days. The project's ambitious scope across '6 tool endpoints' and 'advanced scanning capabilities' likely outpaced the capacity of a single maintainer, leading to an abrupt halt before any release, despite the developer not showing traditional signs of burnout.

Cause of Death

1. Ephemeral existence

The project lived a mere 26 days, from its creation on March 13, 2026, to its last push on March 31, 2026. A lifespan shorter than most development sprints.

2. Unfulfilled deployment

Despite a '.github/workflows/ci.yml' defining a 'publish' job for npm, and 10 core Node.js dependencies installed, no releases were ever published. The code was ready, but the world was not.

3. Feature-rich, user-poor

In its brief 26-day life, the project implemented a 'full MCP server mode with 6 tool endpoints', a 'VS Code extension', and an 'auto-sync command for Claude Projects'. All this by a single contributor, 'Dipanshu-js', for an estimated 0 users.

Vibe Score

10/ 100

Hand-coded. Respect.

What They Did

Conceived as a command-line interface tool, codebase-mcp aimed to 'automatically generate AI-ready context' from codebases for LLMs like Claude, Cursor, and ChatGPT. It aspired to streamline interactions with a 'full MCP server mode' and a dedicated VS Code extension, leveraging a modern Node.js and TypeScript stack.

Node.jsTypeScriptcommanderfast-globsimple-git

Burnout Analysis

Despite a 'low burnout' score of 0/100, the single developer, 'Dipanshu-js', ceased activity after 26 days. The project saw 'at least 10 commits' in that brief period, averaging 0.42 commits per day, indicating consistent but ultimately finite effort. No late-night commit patterns or erratic message lengths were observed; the activity simply ceased, leaving a comprehensive blueprint for an unlaunched product.

Dependency Archaeology

With 10 core Node.js dependencies, including 'commander' for CLI parsing, 'fast-glob' for file scanning, and 'simple-git' for repository operations, the project possessed a robust foundation. The 'package-lock.json' file, with +1268 lines, represented the heaviest component, outweighing the actual application logic's public utility. A full toolbox, but no public job to do.

Autopsy: File Structure

├──.github/workflows/ci.ymlConfigured for release, but the 'publish' job never ran. A tragic testament to unfulfilled deployment.

├──src/cli.tsThe main entry point, adding 331 lines for a sophisticated tool no one used.

├──src/mcp/server.ts309 lines for a 'full MCP server mode with 6 tool endpoints' that served 0 requests.

├──src/scanner/files.ts225 lines dedicated to scanning codebases for AI, perhaps to explain its own demise.

├──src/generator/markdown.ts171 lines to generate CONTEXT.md, a document more complete than the project's public presence.

├──src/commands/sync.ts165 lines for 'Claude Projects auto-sync', a feature waiting for a Claude Project to sync with.

├──packages/vscode-extension/src/extension.ts139 lines for a VS Code extension, waiting patiently in the void for an installation.

└──package-lock.jsonThe most modified file, with +1268 lines, showcasing dependencies installed but never fully utilized in a public release.

Eulogy Stats

Total Commits: 10
Ambitious Adjectives: 6
Deploy Config: Yes
Estimated Users: 0 (the GitHub Actions 'publish' job was never triggered for release)

Last Words

“The silent promise of 'npm publish' (never executed)”