ellmos-codecommander-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cc_analyze_codeB | Analyzes a Python file: classes, functions, imports, metrics. Args:
Returns:
|
| cc_analyze_methodsA | Detailed method analysis of a Python file. Args:
Returns:
|
| cc_extract_classesA | Extracts Python classes and functions from a file as separate text blocks. Args:
Useful for code review and documentation. |
| cc_organize_importsA | Organizes Python imports per PEP 8: sorted, deduplicated, grouped. Args:
Groups: 1) future 2) stdlib 3) third-party 4) local |
| cc_diagnose_importsA | Diagnoses import issues: missing modules, circular imports, unused imports. Args:
Detects: Missing modules, suspected circular imports, import issues |
| cc_check_indentationB | Prüft Python-Dateien auf fehlende Doppelpunkte, unindentierte return/yield-Zeilen und gemischte Tab-/Leerzeichen-Einrückung |
| cc_generate_python_codeB | Generiert Python-Code-Snippets aus BACH-abgeleiteten Templates ohne Dateien zu schreiben |
| cc_runtime_import_diagnoseB | Führt BACH-abgeleitete Python-Runtime-Importdiagnosen in isolierten Subprozessen aus |
| cc_python_structural_editA | 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:
Repairs: BOM, trailing commas, single quotes, comments, NUL bytes |
| cc_validate_jsonB | Validates JSON with detailed error information and position. Args:
|
| cc_fix_encodingA | Repairs encoding errors (Mojibake, double UTF-8). Args:
Repairs 27+ Mojibake patterns (German, French, Spanish). |
| cc_cleanup_fileA | Cleans up source code files: BOM, NUL bytes, trailing whitespace, line endings. Args:
|
| cc_convert_formatA | Converts between JSON, CSV, INI, YAML, TOML, XML, and TOON formats. Args:
|
| cc_fix_umlautsA | Repairs broken German umlauts in source code files. Args:
Detects 70+ patterns of broken umlauts and replaces them correctly. |
| cc_scan_emojiA | Scans files for emojis and shows ASCII alternatives. Args:
Useful for systems that don't support Unicode/Emoji. |
| cc_generate_licensesA | Generates a third-party license file for an npm or Python project. Args:
Reads package.json (npm) or pip packages and collects license info. |
| cc_md_to_htmlA | Converts Markdown to formatted HTML (printable as PDF). Args:
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:
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_filesA | Vergleicht zwei Dateien und zeigt Unterschiede im Unified-Diff-Format |
| cc_regex_testB | 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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 23 tools
Most tools target distinct tasks (analysis, fixing, conversion), but some overlap exists: cc_diagnose_imports and cc_runtime_import_diagnose both address import issues, and cc_fix_encoding vs cc_fix_umlauts are similar. Descriptions generally clarify the differences, so ambiguity is limited.
All tools share the 'cc_' prefix and mostly follow verb_noun ordering (e.g., get_language, fix_json, organize_imports). A few deviate like runtime_import_diagnose and python_structural_edit, but the pattern is largely predictable.
At 23 tools, this is at the high end of reasonable for a broad code-utility toolkit. The count is slightly heavy but justifiable given the wide range of functions (analysis, fixing, conversion, generation).
The tool surface covers a wide variety of code operations: static analysis, import handling, JSON/encoding fixes, format conversion, markdown output, and license generation. Minor gaps exist (e.g., no general-purpose code formatting or search), but core workflows are well represented.