context-mapper-mcp
Related Servers
Alternatives to context-mapper-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAn MCP server that maps any repository into architecture diagrams, providing tools for scanning code facts, building import graphs, and generating Mermaid/DOT diagrams, plus architecture rule enforcement for CI.542 npm1MIT
- AlicenseBqualityCmaintenanceA local MCP server for managing engineering context across Components, Repos, Tasks, and Governance entities. It enables capturing reusable context and composing it per-task with typed relationships and cross-cutting guidelines.361MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that manages C4 architecture models, ADRs, and flow diagrams as TOML files in a docs directory, with git versioning and an HTTP viewer.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that provides persistent memory and contextual awareness to language models, enabling project onboarding, recall of architectural rules, and code consistency across sessions.32MIT
- FlicenseAqualityBmaintenanceMCP server for repository mapping, dependency analysis, and architecture diagram generation for JavaScript, TypeScript, and Python projects.47 npm-
- AlicenseNot gradedqualityCmaintenanceMCP server that lets Claude, ChatGPT, or VS Code build a complete, machine-checked model of your domain and generate an app from it.Apache 2.0
TDQS
Scored across 47 tools
Most tools have clear purposes, but the large number (47) and some overlapping concepts (e.g., generate vs. create for context maps) may cause minor confusion. Descriptions help distinguish, but agents might misselect between aggregate-level and full-model diagram generators.
All tools use 'cml_' prefix with consistent snake_case and verb_noun pattern (e.g., cml_add_command, cml_delete_aggregate, cml_generate_diagram). No mixing of conventions.
47 tools is high, reflecting comprehensive DDD modeling capabilities. While each tool serves a specific purpose, the count exceeds typical scopes, and some could be consolidated (e.g., separate delete tools for each element type).
The tool set covers full lifecycle management for bounded contexts, aggregates, relationships, and elements (commands, events, entities, etc.), plus model validation, file I/O, batch operations, and extensive generation outputs (diagrams, reports, glossary, JDL, MDSL). No obvious gaps.