Skip to main content
Glama
naw103

Foremerge

by naw103
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to Foremerge

No user-submitted related servers found.

    Related Servers

    • Vibechemy

      DiamondAlchemy
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server for orchestrating a fleet of CLI coding agents in isolated git worktrees. It exposes tools for spawning workers, sending instructions, reviewing diffs, and merging changes, with full terminal visibility.
      11 npm
      4
      MIT
    • STMA by Matte-AI-LLC

      STMAofficial

      Matte-AI-LLC
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI coding agents to coordinate by sharing environment snapshots and diffs, surfacing overlapping work, exchanging debug-session messages, handing off tasks, and enforcing policy preflight checks.
      -

    • 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

    • uacos

      caotiensinh
      A
      license
      Not graded
      quality
      C
      maintenance
      Local-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.
      1
      MIT

    • batuta-mcp

      vorluno
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server that decomposes tasks into plans with disjoint file boundaries, validates overlaps, and creates git worktrees with a ready prompt per plan.
      3
      28 npm
      Apache 2.0
    Deploy Server
    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

    A4.5/5.0

    Scored across 18 tools

    Disambiguation5/5

    Every tool targets a distinct resource or lifecycle step: reads are separated by entity (intent, changeset, overview/search), and state transitions have explicit sequential roles. The overlap among publish/claim/start/verify/accept/record is intentional and clearly sequenced, so an agent should not confuse one for another.

    Naming Consistency5/5

    All tools use lower_snake_case and follow a predictable verb_noun pattern (get_intent, publish_changeset, resolve_conflict, run_verification), with only status as a noun-only outlier. There is no mixing of camelCase, bare generic verbs, or multiple verbs for the same action.

    Tool Count3/5

    At 18 tools the server sits in the 16–25 range that feels heavy for an MCP toolset, even though the coordination workflow genuinely needs most of them. The count is defensible, but it is borderline rather than lean.

    Completeness4/5

    The full lifecycle is covered: register, publish intent, assess/claim/start, publish changeset, verify, accept, and record commit, with conflict and overview tools throughout. The main gap is that coordinated messages cannot be read through MCP, only sent, so an agent must use the CLI to receive the other side of the conversation.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources