BACH CodeCommander MCP server

Read from the package source without running it. The installed server may list more.

• cc_analyze_code

  Analyzes a Python file: classes, functions, imports, metrics. Args: - path (string): Path to the Python file Returns: - Classes with methods, functions, import analysis, LOC, complexity

• cc_analyze_methods

  Detailed method analysis of a Python file. Args: - path (string): Path to the Python file - class_name (string, optional): Only methods of this class Returns: - Methods with parameters, decorators, complexity, data flow

• cc_cleanup_file

  Cleans up source code files: BOM, NUL bytes, trailing whitespace, line endings. Args: - path (string): Path to the file - remove_bom (boolean): Remove BOM - remove_trailing_whitespace (boolean): Trailing whitespace - normalize_line_endings (string): "lf" | "crlf" - remove_nul_bytes (boolean): Remove NUL bytes - dry_run (boolean): Preview only

• cc_convert_format

  Converts between JSON, CSV, INI, YAML, TOML, XML, and TOON formats. Args: - input_path (string): Source file - output_path (string): Target file - input_format (string): "json" | "csv" | "ini" | "yaml" | "toml" | "xml" | "toon" - output_format (string): "json" | "csv" | "ini" | "yaml" | "toml" | "xml" | "toon" - json_indent (number): JSON indentation

• cc_diagnose_imports

  Diagnoses import issues: missing modules, circular imports, unused imports. Args: - path (string): Path to the Python file Detects: Missing modules, suspected circular imports, import issues

• cc_diff_files
• cc_extract_classes

  Extracts Python classes and functions from a file as separate text blocks. Args: - path (string): Path to the Python file - output_dir (string, optional): Output directory (otherwise display only) Useful for code review and documentation.

• cc_fix_encoding

  Repairs encoding errors (Mojibake, double UTF-8). Args: - path (string): Path to the file - dry_run (boolean): Preview only - create_backup (boolean): Create backup Repairs 27+ Mojibake patterns (German, French, Spanish).

• cc_fix_json

  Automatically repairs common JSON errors. Args: - path (string): Path to the JSON file - dry_run (boolean): Only show issues - create_backup (boolean): Create backup Repairs: BOM, trailing commas, single quotes, comments, NUL bytes

• cc_fix_umlauts

  Repairs broken German umlauts in source code files. Args: - path (string): Path to the file - dry_run (boolean): Preview only - create_backup (boolean): Create backup Detects 70+ patterns of broken umlauts and replaces them correctly.

• cc_generate_licenses

  Generates a third-party license file for an npm or Python project. Args: - project_dir (string): Project directory - output_path (string): Output file - format (string): "text" | "json" | "csv" Reads package.json (npm) or pip packages and collects license info.

• cc_md_to_html

  Converts Markdown to formatted HTML (printable as PDF). Args: - input_path (string): Path to the Markdown file - output_path (string): Path to the HTML output - title (string, optional): Document title Produces standalone HTML with CSS styling, printable as PDF via browser.

• cc_md_to_pdf

  Converts Markdown to PDF using a headless browser (Edge/Chrome). Args: - input_path (string): Path to the Markdown file - output_path (string): Path to the PDF output - title (string, optional): Document title Uses the same Markdown parser as cc_md_to_html. Requires Edge or Chrome. Falls back to HTML if no browser is found.

• cc_organize_imports

  Organizes Python imports per PEP 8: sorted, deduplicated, grouped. Args: - path (string): Path to the Python file - dry_run (boolean): Preview only Groups: 1) __future__ 2) stdlib 3) third-party 4) local

• cc_regex_test
• cc_scan_emoji

  Scans files for emojis and shows ASCII alternatives. Args: - path (string): Path to the file or directory - recursive (boolean): Scan recursively - extensions (string): Only certain extensions Useful for systems that don't support Unicode/Emoji.

• cc_set_language

  Set the output language for CodeCommander tools

• cc_validate_json

  Validates JSON with detailed error information and position. Args: - path (string): Path to the JSON file

• Code scan11 source files scanned13/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 2 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Safety score

75/100

higher than 45% of 48,273 servers

Tools

18

the typical server has 7

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

3

more than 80% of 28,534 servers

BACH CodeCommander: common questions

Is BACH CodeCommander MCP server safe?

Mostly: it is graded B (75/100). Read the BACH CodeCommander safety report

How do I install BACH CodeCommander?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does BACH CodeCommander need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is BACH CodeCommander maintained?

The last commit was 37 days ago (2026-09-26). The latest release is v1.3.0.

What can I use instead of BACH CodeCommander?

Servers from other publishers that do the same job: Sem MCP server.

How does BACH CodeCommander compare with other MCP servers?

safety score 75/100 (higher than 45% of 48,273 servers); tools 18 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.