Skip to main content
Glama
Sign In
metabolism-tools

workspace-metabolism

by metabolism-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to workspace-metabolism

No user-submitted related servers found.

    Related Servers

    • toolwrit

      emektor
      A
      license
      Not graded
      quality
      A
      maintenance
      Policy sidecar for any MCP server: deny-by-default tool allowlist with argument rules, call and USD budget caps, and a hash-chained audit log with RFC 3161 timestamps.
      9
      Apache 2.0

    • CodexPro Runtime

      Menglook
      A
      license
      B
      quality
      D
      maintenance
      A 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.
      33
      MIT

    • Kadhai

      Madhuhas
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables external MCP clients like Claude Desktop, Claude Code, Cursor and Zed to hand work to a local crew of AI agents that plan, write, check and fix code in a folder, while also acting as an MCP client that can use their tools. Runs locally with user-supplied keys, approval-gated commands, diffable and undoable runs.
      AGPL 3.0

    • okgate

      ubukhari
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP policy proxy that sits between AI agents and their upstream MCP servers to enforce hard spend and blast-radius caps, human approvals for destructive tools, a kill switch, scoped per-agent credentials, dry-run writes with mutation diffs, semantic loop breaking, and a hash-chained audit log. It also offers hook mode that applies the same policy to coding agents' own shell commands and file edits.
      MIT

    • my-pi

      BoxBoxmari
      A
      license
      C
      quality
      B
      maintenance
      Local-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.
      13
      3
      MIT

    • viberevert

      madeinplutofabio
      A
      license
      A
      quality
      B
      maintenance
      Local 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.
      8
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources