@skeletiq/mcp
Related Servers
Alternatives to @skeletiq/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to enforce architecture standards by checking repositories against overridable rules and adapter results over MCP.5 npmMIT
- AlicenseNot gradedqualityBmaintenanceServes coding agents with project-specific knowledge (decisions, conventions, constraints) over MCP and provides verification verdicts on whether code still complies.365 npmAGPL 3.0
- AlicenseAqualityBmaintenanceServes reusable SDLC agent roles and review checklists over MCP, enabling AI coding agents to execute structured product analysis, solution architecture, code review, and release management tasks in GitHub-first projects.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI agents to read and store architecture decisions, constraints, and research from a private Solveaux workspace, keeping generated code aligned with team-approved technical direction.338 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to take and progress tasks, hand in completed work with evidence, and enables users to publish, search, and retrieve guides, file bugs, manage inbox/board/activity/logs, and plan tasks over MCP.MIT

wellwornofficial
FlicenseNot gradedqualityDmaintenanceProvides coding agents with verified recommendations, version-specific breakage traps, design systems, and installable skills over MCP, enabling safer stack and dependency decisions without requiring an API key.-
TDQS
Scored across 6 tools
Each tool occupies a clearly distinct role: listing projects, reading existing designs, generating new ones, polling generation status, critiquing a design, and checking drift. There is no meaningful overlap between any pair.
All tool names follow the same lowercase snake_case verb_noun pattern (list_projects, get_design, generate_architecture, get_generation_status, critique_architecture, check_drift). The verbs are specific and consistently placed.
Six tools is a well-scoped size for an architecture design assistant. Each tool covers a distinct stage in the workflow without redundancy or bloat.
The surface covers the full lifecycle an agent needs: discover projects, read designs, kick off generation, poll for completion, critique a proposed design, and verify built code against the design. No operation essential to the stated purpose is missing.