BACH CodeCommander
Give your coding agent a stdio MCP toolkit for parsing, fixing JSON, normalizing encodings, converting formats, diffing text, and running regex without one-off scripts.
Overview
BACH CodeCommander is a Build-phase MCP server that gives coding agents 17 tools for code analysis, JSON repair, encoding fixes, format conversion, diffing, and regex.
What is this MCP server?
- 17 MCP tools covering code analysis, JSON repair, encoding fixes, format conversion, unified diff, and regex operations
- stdio transport via npx (`bach-codecommander-mcp` npm package, v1.3.0)
- Suited for agent-driven refactors, config cleanup, and pre-commit sanity checks without leaving the chat
- Pairs with local repos and CI logs where malformed JSON or encoding glitches block merges
- Developer Tools MCP integration—not a packaged agent skill or cloud IDE extension
- 17 documented MCP tools (analysis, JSON, encoding, format, diff, regex)
- Server version 1.3.0; npm package `bach-codecommander-mcp`; stdio transport
Community signal: 2 GitHub stars.
What problem does it solve?
Agents and humans waste cycles fixing malformed JSON, encoding mistakes, and unstructured text with fragmented online utilities instead of one MCP-accessible toolkit.
Who is it for?
Solo builders who want deterministic text and code hygiene tools callable from Claude Code, Cursor, or Codex during integration and review work.
Skip if: Teams that need hosted browser automation, database admin, or full static-analysis suites without running a local Node MCP process.
What do I get? / Deliverables
After you add CodeCommander to your MCP config, agents can normalize payloads, compare revisions, and run regex or format conversions in-thread during build and review.
- Repaired or validated JSON and converted text artifacts from agent tool calls
- Readable diffs and regex-transformed strings for review in the chat thread
- Repeatable local MCP integration you can version in dotfiles or team docs
Recommended MCP Servers
Journey fit
Canonical on Build because solo builders wire MCP servers while assembling agent workflows; the same utilities support Ship review when comparing patches and validating payloads. agent-tooling is the right shelf for a 17-tool CodeCommander server that extends Claude Code, Cursor, or Codex with deterministic text and code helpers.
How it compares
Local Developer Tools MCP server with 17 text/code utilities—not a cloud LLM API wrapper or a single-purpose agent skill.
Common Questions / FAQ
Who is BACH CodeCommander for?
It is for indie developers and agent-first builders who want JSON repair, diff, encoding, format conversion, regex, and light code analysis available as MCP tools in their daily coding client.
When should I use BACH CodeCommander?
Use it while building or shipping when agents generate configs, migrations, or API responses that need validation, diff review, or encoding cleanup before you merge or deploy.
How do I add BACH CodeCommander to my agent?
Register the npm package `bach-codecommander-mcp` (v1.3.0) as a stdio MCP server with runtimeHint npx in Claude Desktop, Claude Code, Cursor, or another MCP-compatible host, then restart the client.