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-
- AlicenseAqualityCmaintenanceA 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
- FlicenseBqualityDmaintenanceMCP server providing 37 developer tools for hashing, encoding, regex, JSON, SQL, cron, QR codes, UUID, JWT, and more, all powered by bmobot.ai APIs.37-
- AlicenseNot gradedqualityBmaintenanceA 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.9 npmMIT
- 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.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides developer knowledge and utility tools including local documentation search, text summarization, safe arithmetic calculation, unit conversion, and knowledge-base 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.