No user-submitted related servers found.
Scored across 37 tools
Several tools have overlapping purposes: mcp_m7_validate, mcp_m7_validate_implementation, mcp_m7_safety_verify, mcp_m7_check_tech_stack, mcp_m7_style_guardian.validate/check, and mcp_m7_error_database.check all perform some form of code checking or validation. mcp_m7_impact overlaps with mcp_m7_knowledge_graph's impact action, and multiple knowledge/memory tools (memory, knowledge_hub, cross_session, knowledge_graph) are hard to distinguish at a glance.
All tool names use snake_case with a consistent mcp_m7_ prefix, which is readable and predictable. However, the naming mixes verb-style names (analyze_task, check_errors, create_structure) with noun-style names (schema, mesh, memory, session, console, contracts, telemetry), so the pattern is not fully consistent.
With 37 tools, the surface is heavy for a methodology/workflow server, and many tools are mega-tools exposing 8-20 internal actions. The count feels excessive and increases selection burden rather than being a tightly scoped set.
The tool set covers a broad M7 lifecycle: project initialization, cycle management, task analysis, scoping, session tracking, memory, knowledge graph, contracts, validation, safety, style, telemetry, DevOps, and visualization. Minor gaps exist around clear CRUD-style operations for some registries, but core workflows appear covered.
