ellmos-codecommander-mcp
Related Servers
Alternatives to ellmos-codecommander-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceA lightweight MCP server providing everyday developer utilities such as JSON formatting, UUID generation, Base64 conversion, HTTP status lookup, and Unix timestamp conversion as tools and resources.5-
- AlicenseAqualityDmaintenanceA credential-free MCP server offering developer utilities such as JSON formatting, regex testing, hashing, UUID generation, base64 transforms, and JWT inspection, with no network dependencies.6MIT
- AlicenseBqualityDmaintenanceMCP server providing 37 developer tools for hashing, encoding, regex, JSON, SQL, cron, QR codes, UUID, JWT, and more, all powered by bmobot.ai APIs.37MIT
- AlicenseNot gradedqualityCmaintenanceA unified developer toolbox MCP server providing utilities for base64, JWT, timestamps, UUID, JSON formatting, hashing, URL handling, case conversion, color conversion, number bases, string operations, and regex.5 npmMIT
- AlicenseNot gradedqualityCmaintenanceA remote MCP server exposing developer utility tools that compute QR codes, JSON diffs and formatting, base64/URL encoding, hashes, JWT decoding, cron explanations, timestamp conversions, placeholder images, flowcharts, HTML/React forms, color scales and regex matches with exact results. Results can be previewed, edited and exported in an interactive workbench where the host supports MCP Apps.MIT
- FlicenseNot gradedqualityDmaintenanceA modular MCP server that provides tools for file operations, regex-based code searching, and structural analysis of functions and classes across multiple programming languages. It also includes AI-powered features for intelligently updating files according to architectural changes.-
TDQS
Scored across 23 tools
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.
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.
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.
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.