mcp-metsuke-crunchtools
OfficialRelated Servers
Alternatives to mcp-metsuke-crunchtools
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceProvides persistent, searchable memory across coding projects and machines, letting agents record and retrieve projects, reusable assets, sessions, decisions, commits, and handoffs via MCP.19 PyPI2Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP agents to maintain durable, evidence-aware project knowledge, retrieve precise excerpts on demand, and track decisions, conflicts, and revisions across sessions.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides a shared, repo-local memory that lets coding agents recall relevant decisions, conventions, gotchas, and open threads, save new entries, coordinate file claims, and cache file summaries across tools and sessions.88 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables ChatGPT agents to store and retrieve reports in MongoDB Atlas, acting as a bridge between ChatGPT scheduled agents and a persistent database.-
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to locally store and share tasks, work activities, long-term memory, knowledge, and people information, while allowing users to review saved content and generate briefings or reports through a web UI.MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to search and read curated project memory before exploring code, and to record durable findings as append-only events for later Librarian auditing.92 npm3MIT
TDQS
Scored across 10 tools
Most tools target clearly distinct resources (definitions, outputs, runs, sweeps) with a clean verb split (list/get/save/delete/prune). The only mild overlap is get_output_tool vs get_sweep_tool, since both retrieve gathered data, but the descriptions distinguish compiled findings from pre-gathered sweep sections well.
Every tool follows the same verb_noun_tool pattern (list_reports_tool, get_output_tool, upsert_definition_tool, prune_outputs_tool), with consistent snake_case and singular/plural conventions (list uses plural, get/upsert use singular). No mixed styles.
Ten tools is well-scoped for a report-gathering management server, covering the full lifecycle of definitions, outputs, triggering, and sweeps without redundancy. Each tool earns its place with a distinct role.
Outputs have full lifecycle coverage (save, get, list, delete, prune) and definitions support list/get_spec/upsert, but there is no delete_definition_tool, leaving a gap in definition management. Agents can work around it, but the surface is not fully closed.