Skip to main content
Glama
vorluno

batuta-mcp

by vorluno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to batuta-mcp

No user-submitted related servers found.

    Related Servers

    • Foremerge

      naw103
      A
      license
      A
      quality
      A
      maintenance
      Coordination 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'
      18
      267
      Apache 2.0

    • wt-mcp

      felipemdf
      A
      license
      B
      quality
      C
      maintenance
      MCP server for managing git worktrees per product, enabling agents to create, list, sync, and open tasks with multiple projects, reusable YAML config, and auto-generated Cursor/VS Code workspaces.
      13
      1
      MIT

    • agent-locks

      luohoa97
      A
      license
      A
      quality
      D
      maintenance
      A filesystem-based MCP server for AI coding agents to coordinate work across git worktrees by claiming files, checking for conflicts, and logging progress without affecting the repository's git history.
      5
      MIT

    • taskops

      bernatch22
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Claude Code agents to manage persistent shared task boards with dependency graphs, atomic claims, and git-bound tasks.
      11
      123 PyPI
      MIT

    This server cannot be deployed

    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: checking overlaps, decomposing input, and scaffolding worktrees. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case, making them predictable and easy to understand.

    Tool Count5/5

    Three tools is exactly right for the focused domain of plan decomposition and worktree setup. The scope is well-defined.

    Completeness5/5

    The tool set covers the full workflow: validation (check), creation (decompose), and execution (scaffold). There are no obvious gaps for its stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources