mellos-mapping
Related Servers
Alternatives to mellos-mapping
No user-submitted related servers found.
Related Servers
- FlicenseBqualityCmaintenanceMCP 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.394-
- 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 gradedqualityBmaintenanceMCP 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
- AlicenseAqualityBmaintenanceMCP 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.32 npm105MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.44 npm8MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for creating interactive terminal canvases (calendar, document, flight) in AI coding assistants. Supports multiple TUI frameworks and integrates with tmux.MIT
TDQS
Scored across 8 tools
The tools are mostly distinct: declare creates, update revises, read fetches structured data, view renders text, remove deletes, batch combines operations, open displays on screen, and setup configures policy. Minor confusion remains between mmap_read and mmap_view, and between single-operation tools versus mmap_batch, but the detailed descriptions largely resolve these boundaries.
All tools share the consistent mmap_ prefix and use short command-style names such as declare, read, update, remove, and view. The pattern is mostly uniform, though mmap_batch and mmap_setup are slightly noun-like rather than clear verb_noun commands.
Eight tools is a well-scoped count for a mapping tool: create, read, update, delete, batch, render, display, and policy configuration each earn a place. There is no obvious bloat or noticeable thinness.
The tool surface covers the full lifecycle of map pages and elements: declaring maps, reading existing state, updating and removing entities, atomic multi-operation changes, rendering views, and controlling display. Administrative concerns like cleanup and policy configuration are also addressed, leaving no major dead ends.