CodeDoc MCP Server
Related Servers
Alternatives to CodeDoc MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnforces disciplined programming practices by requiring AI assistants to audit their work and produce verified outputs at each phase of development, following structured workflows for refactoring, feature development, and testing.2012-
- AlicenseAqualityDmaintenanceA deterministic architecture audit engine for Cursor. It enforces visual Mermaid protocols to prevent LLM hallucinations, ensuring AI modifies code based on strict blueprints.1MIT
- AlicenseNot gradedqualityBmaintenanceOrchestrates Claude Code and OpenAI Codex to plan, implement, review, and verify code changes via pull requests with security controls.MIT
- FlicenseAqualityAmaintenanceAI-powered continuous code assistant for Cursor, VS Code, Antigravity, and Claude Code via MCP, providing tools for code review, testing, documentation, and quality analysis.81-
- AlicenseAqualityBmaintenanceIndependent verification for code written by AI agents. Adds an /elliot-audit command to Claude Code, Cursor and Codex that checks whether a repo does what its docs claim, verifies every cited line at file:line, and writes an HTML/Markdown/JSON report into the repo.141MIT
- AlicenseNot gradedqualityCmaintenanceEnables auditing and drafting of AI agent files (CLAUDE.md, AGENTS.md, Cursor rules) and turning project descriptions into full build specs, with local and API-based tools.43 npmMIT
TDQS
Scored across 10 tools
Multiple tools have overlapping purposes: refactor_and_optimize and evaluate_and_refactor both refactor/optimize code, while global_security_audit and guardian_scan both perform security scanning. generate_smart_doc is described as 'universal' and could be mistaken for an audit tool, adding confusion.
Naming conventions are mixed: some tools use verb_noun (scan_project_files, predict_impact), some use verb_and_verb (refactor_and_optimize, evaluate_and_refactor), and others use arbitrary adjectives (guardian_scan, generate_smart_doc). This inconsistency makes it harder to predict tool behavior from the name.
The count of 10 is within a reasonable range, but several tools serve nearly identical functions (two refactoring tools, two security scanners), suggesting the set is not well-scoped and redundant tools could be consolidated.
The server covers multiple areas (documentation, refactoring, security, impact analysis, dependency healing), but the name 'CodeDoc' suggests a focus on documentation, which is only represented by one broad tool. Missing features like updating existing documentation or verifying code post-refactor create notable gaps.