architect-anything-mcp
Related Servers
Alternatives to architect-anything-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server that provides audit and safety-check tools for enterprise SDLC code integrity, enabling AI agents to scan workspaces for lifecycle gaps, mock-theater tests, DRY violations, and language-specific issues in shell, JavaScript/HTML, and Python.414 npmMIT
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.10 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides a provider-agnostic MCP server that owns task claims, action logs, role handoffs, and health-gate results so AI coding agents can move work through use-case, spec, design, build, and review stages with server-enforced evidence. It also exposes read-only skills for drafting use cases and specs, triaging bugs, answering code questions, and auditing itself.29 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides a stdio MCP server that drives structured multi-agent development workflows: claiming and updating tracked tasks, logging actions and handoffs, gating work on server-owned health checks, and managing use-case, functional, and technical specification documents on the filesystem. It also exposes read-only skills for triage, consultation, review, and product guidance while enforcing approval and repair authorizations.29 npmMIT
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server that lets an agent audit its own environment by discovering local MCP configurations and skill folders on Windows, macOS, and Linux and running offline static checks for prompt injection, hidden instructions, hardcoded secrets, dangerous commands, unpinned packages, and excessive filesystem or transport permissions. It exposes tools to scan everything discovered, list configurations, vet a single skill, or analyze supplied text, returning text, JSON, SARIF, or HTML findings with CI-friendly severity levels.14 npmMIT
- AlicenseNot gradedqualityBmaintenanceA stdio MCP server providing everyday tools and Markdown skills for the Sesha agent, enabling notes, web research, coding, docs, scheduling, and safety/governance.GPL 3.0
TDQS
Scored across 16 tools
Most tools target distinct resources or lifecycle stages: investigation setup, checklist, citations, claims, sections, diagrams, validation, publishing, inventories, comparison, schema, and REA CLI operations. The main ambiguity is between aa_finish and aa_render, since both publish reports, though their descriptions distinguish workspace-backed vs workspace-free publishing. aa_status and aa_rea_status are also close in naming but clearly separate investigation status from REA CLI probing.
All tools share the aa_ prefix and use readable snake_case, with a predictable verb_noun pattern for most operations such as aa_upsert_claim and aa_set_run_meta. Minor deviations appear in noun-only names like aa_status, aa_checklist, aa_inventory, and aa_schema, but the overall convention remains consistent.
Sixteen tools are slightly over the typical comfortable range, but the server covers several related workflows: investigation setup, report authoring, validation/publishing, inventory comparison, schema introspection, and REA CLI integration. Each tool appears to have a concrete role rather than being redundant padding.
The surface covers the main lifecycle from investigation setup through checklist tracking, evidence citation, report authoring, validation, and publishing, plus inventory/comparison and REA CLI helpers. Minor gaps exist around explicit deletion or listing of existing investigations/reports and removing individual report elements, but core workflows are well supported.