workspace-metabolism
Related Servers
Alternatives to workspace-metabolism
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceA local, evidence-driven MCP runtime and control plane for open-source maintainers that provides workspace-bounded tools including controlled file operations, command execution, validation primitives, durable execution records, and human review workflows via stdio and Streamable HTTP transports.33MIT
- AlicenseCqualityBmaintenanceLocal-first MCP runtime for coding agents with bounded workspace access, content-preconditioned writes, AST search, LSP navigation and diagnostics, and Git status/diff. Designed to give coding agents useful repository access without treating unrestricted shell access as the default integration boundary.2132MIT
- AlicenseAqualityBmaintenanceLocal MCP server for AI agents and vibe coding safety: deterministic risk checks (payments, auth, database, secrets, infrastructure), sessions, checkpoints, policy inspection, and fix prompts. Runs over stdio against a local git repository; no language model judges risk.81Apache 2.0
- AlicenseAqualityAmaintenanceCoordination protocol for parallel coding agents, built above Git. The MCP server exposes the full 17-tool lifecycle over stdio: register agents, publish intents with semantic scopes and declared operations, claim work, check for conflicts before code is written, publish ChangeSets, run trusted named verification checks, and record accepted work. Deterministic rules raise findings when two agents'18267Apache 2.0
- FlicenseAqualityBmaintenanceA local-first MCP server that handles daily work tasks through your AI assistant: converts meeting notes into todos, manages todo lifecycle, tracks work hours, generates daily/weekly reports, organizes files via move-only operations, and diagnoses dev environments, all guarded by a human-maintained preview/apply safety model.25-
- AlicenseAqualityBmaintenanceDefault-deny action registry, append-only spend ledger, and human sign-off audit trail (MCP tools).6MIT
TDQS
Scored across 9 tools
Each tool targets a distinct operation: db_check inspects the registered SQLite resource, health/audit/explain provide different report granularities, clean/rollback execute and undo changes, govern checks policy decisions, init scaffolds, and verify checks journal integrity. The read-only reporting tools overlap in spirit, but their outputs and use cases are clearly separated.
All tools share the wm_ prefix and lowercase snake_case, which is predictable and consistent. Most are verb-first (clean, explain, govern, init, verify), but health, audit, and db_check are noun-led or object-verb, so the pattern is not uniformly verb_noun.
Nine tools is well within the ideal range and each maps to a distinct phase of the metabolism-policy workflow: init, inspect, act, undo, verify, and govern. No tool feels redundant or like padding.
The core lifecycle is covered: policy creation, audit/health reporting, path explanation, cleanup planning/execution, rollback, governance checks, and journal verification. The main gap is the lack of a tool to update or evolve the policy itself, but that can be worked around by editing the policy file and re-auditing.