Skip to main content
Glama
ellmos-codecommander-mcp

ellmos-codecommander-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
cc_analyze_codeA

Analyzes a Python, JavaScript, or TypeScript file: classes, functions, imports, metrics.

Args:

  • path (string): Path to a .py, .js/.jsx/.mjs/.cjs, or .ts/.tsx/.mts/.cts file

Returns:

  • Classes with methods, functions, import analysis, LOC, complexity

cc_analyze_methodsA

Detailed method analysis of a Python, JavaScript, or TypeScript file.

Args:

  • path (string): Path to a .py, .js/.jsx/.mjs/.cjs, or .ts/.tsx/.mts/.cts file

  • class_name (string, optional): Only methods of this class

Returns:

  • Methods with parameters and visibility; Python analysis also includes decorators, complexity, data flow, and BACH guardrails

cc_extract_classesB

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)

  • include_content (boolean, optional): Include pycutter-style code blocks in the response

  • max_chars (number, optional): Maximum response characters for included code

Useful for code review and documentation.

cc_organize_importsA

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_diagnose_importsA

Diagnoses import issues in Python, JavaScript, or TypeScript files.

Args:

  • path (string): Path to a .py, .js/.jsx/.mjs/.cjs, or .ts/.tsx/.mts/.cts file

Detects: Unused bindings, duplicates, relative-import risks, and import-order issues

cc_check_indentationB

Prüft Python-Dateien auf fehlende Doppelpunkte, unindentierte return/yield-Zeilen und gemischte Tab-/Leerzeichen-Einrückung

cc_generate_python_codeC

Generiert Python-Code-Snippets aus BACH-abgeleiteten Templates ohne Dateien zu schreiben

cc_runtime_import_diagnoseC

Führt BACH-abgeleitete Python-Runtime-Importdiagnosen in isolierten Subprozessen aus

cc_python_structural_editC

Prüft und wendet BACH-abgeleitete strukturelle Python-Edits mit Vorschau, Testdatei und Backup-Schutz an

cc_fix_jsonA

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_validate_jsonA

Validates JSON with detailed error information and position.

Args:

  • path (string): Path to the JSON file

cc_fix_encodingC

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_cleanup_fileB

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_formatC

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_fix_umlautsA

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_scan_emojiB

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_generate_licensesB

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_htmlB

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_pdfA

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_diff_filesB

Vergleicht zwei Dateien und zeigt Unterschiede im Unified-Diff-Format

cc_regex_testC

Testet reguläre Ausdrücke gegen Text oder Dateiinhalt

cc_set_languageB

Set the output language for CodeCommander tools

cc_get_languageA

Get the currently configured output language and supported languages for CodeCommander tools

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 23 tools

Disambiguation3/5

Several clusters overlap: cc_fix_encoding, cc_fix_umlauts, cc_cleanup_file and cc_fix_json all repair file-level defects (BOM, NUL bytes appear in both fix_json and cleanup_file), and cc_analyze_code vs cc_analyze_methods / cc_extract_classes are nested views of the same file. Import handling is split across three tools (organize, diagnose, runtime_diagnose) that an agent could easily misselect. Descriptions help somewhat, but boundaries are blurry in the repair and analysis families.

Naming Consistency4/5

All 23 names use a uniform cc_ prefix and snake_case, with mostly verb_noun form (fix_json, analyze_code, organize_imports, validate_json). A few deviate slightly toward noun_verb (cc_regex_test, cc_diff_files) but remain readable and predictable. The only inconsistency is that some descriptions are in German while names stay English.

Tool Count3/5

23 tools sits in the heavy range for what is essentially a file-maintenance utility belt. Each tool has a specialty, but several niche ones (fix_umlauts, scan_emoji, check_indentation) arguably belong as options of broader repair/analysis tools rather than first-class endpoints.

Completeness4/5

Coverage across JSON repair/validation, code analysis, import hygiene, format conversion, encoding repair, and Markdown-to-HTML/PDF is broad with few dead ends. Gaps exist: no generic file read/write, formatting tools only cover Python imports (not JS/TS), code generation is Python-only, and convert_format supports YAML/TOML/XML but has no validate/repair counterparts for those formats.

Maintenance

ActivityNo data
ResponsivenessOutdated data