mellos-mapping
Related Servers
Alternatives to mellos-mapping
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceMCP server that gives AI coding assistants persistent memory, structural code graph analysis, and safe multi-agent coordination, enabling them to answer architectural questions, track decisions across sessions, and coordinate safely in multi-agent workflows.394MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that builds a dependency graph of your codebase, giving AI agents structural understanding to analyze impact, find context, and make safe modifications across languages and infrastructure.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Code, ChatGPT desktop Codex mode and Codex CLI to declare and maintain a live, terminal-native layered dependency map of a system as it is built. Exposes tools that lay down a ghost design first, mark the node currently under construction, and light nodes solid only when they are built and verified.58 npmMIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that lets Claude Code, Codex, pi, omp and other MCP clients declare and maintain a live layered dependency map of a system, exposing eight mmap_* tools to add ghost nodes, draw downward-only edges, and light nodes up as built and verified. It turns bottom-up progress into a shared ledger in a terminal pane beside the conversation, marking nodes red when later work cracks a foundation.58 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that analyzes codebases to provide dependency graphs, impact analysis, and file insights across 15+ programming languages, enabling AI assistants to understand project structure and navigate code efficiently.MIT
- AlicenseAqualityDmaintenanceMCP server that helps AI coding agents understand a repository by providing lightweight tree/map, code search, and token-budgeted context packing tools without dumping the entire monorepo into the prompt.326 npm104MIT
TDQS
Scored across 8 tools
mmap_batch explicitly combines additions, updates, and removals on one page, directly overlapping with mmap_declare (add), mmap_update (revise), and mmap_remove (delete). The verbosely-written descriptions try to delineate boundaries, but an agent must read carefully to decide between batch and the individual mutation tools. mmap_view vs mmap_read is clearer (picture vs structured records), but the core mutation overlap remains.
Every tool uses the identical mmap_ prefix followed by a short lowercase verb/noun (batch, open, declare, read, remove, setup, update, view). The convention is uniform and predictable throughout, with no style mixing.
Eight tools is a well-scoped set for a mapping/visualization server. Each targets a distinct phase (policy, declare, read, update, remove, batch, view, open), and none feels gratuitous or trivially redundant.
The surface covers the full lifecycle: policy setup, creation (declare), reading (read/view), mutation (update/batch), removal, and display (open). Coverage is strong, though the functional overlap means some gaps are masked by tools doing multiple jobs rather than cleanly separated operations.