MeshMind
Related Servers
Alternatives to MeshMind
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA local-first MCP server that turns a .context/ folder of markdown files into a searchable knowledge layer for AI coding agents.4 npm2MIT
- AlicenseNot gradedqualityDmaintenanceA local MCP server that gives AI coding agents persistent memory and context across sessions.24 npmMIT
- AlicenseAqualityAmaintenanceA local-first MCP server that gives AI coding agents persistent memory and controlled commands. Features a git-backed markdown knowledge vault with FTS5 search, surgical section edits, token-aware context budgeting, and a sandboxed command engine with human approval gates. Works with Claude Code, Cursor, Copilot, Gemini, and more.53316 npm1Apache 2.0
- AlicenseAqualityAmaintenanceLocal-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.3718 npm4MIT
- -licenseNot gradedqualityNot gradedmaintenanceAn MCP server that enables multiple AI models (Claude, ChatGPT, Gemini) to share and persist context via a local-first vault of markdown files and SQLite index, allowing seamless cross-AI memory.-
- AlicenseBqualityFmaintenanceA zero-cost MCP server that forces AI to self-correct code using prompt injection and context isolation.411MIT
TDQS
Scored across 7 tools
Tools have largely distinct purposes, with some overlap between crush_file and get_optimized_context as both compress, but they target different use cases (file shortcut vs. general pipeline). export_codebase_graph and scan_local_codebase are related but differ in output format and depth. Overall, agents can distinguish most tools.
All tool names use snake_case with a consistent verb_noun or descriptive pattern (e.g., crush_file, get_optimized_context, research_last_30_days). No mixing of conventions, making naming predictable and clear.
Seven tools cover the advertised functionality—context compression, codebase analysis, and research—without being excessive. Each tool has a defined role, and the count is appropriate for the server's purpose.
The tool set covers key operations: compression, decompression, stats, codebase scanning, graph export, and research. Minor gaps exist, such as no tool to list or manage stored refs, and no direct configuration update, but core workflows are well-supported.