Skip to main content
Glama
Sign In
tower-mcp

tower-mcp

by Rohanxmalik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to tower-mcp

No user-submitted related servers found.

    Related Servers

    • synco-mcp

      ijustseen
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple AI coding agents to coordinate on a shared software project by registering, claiming tasks, declaring file intents, publishing structured change reports, and handing off context, with a local dashboard showing state in near real time.
      MIT

    • OpenHuddle

      nika110
      A
      license
      A
      quality
      B
      maintenance
      Connects multiple AI coding agents on a team through a shared hub, giving each agent live teammate status, a versioned master prompt, a shared task board, questions and answers, and file claims so agents don't overwrite each other's work. Works across Claude Code, Codex, and Cursor while code itself continues to flow through git.
      10
      102 npm
      6
      MIT

    • agentsync

      jarmstrong158
      A
      license
      A
      quality
      D
      maintenance
      Enables multiple AI agents to collaborate on the same git repository by coordinating work via a shared claims branch, detecting file conflicts before they happen.
      9
      33 PyPI
      PolyForm Noncommercial 1.0.0

    • hubai

      andytwoods
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives a hackathon team's AI coding agents and their humans a shared task board and inbox, so agents can atomically claim tasks, move them between todo/doing/blocked/done, post messages to teammates or the whole team, and read new messages plus board events since they last checked. It also exposes member and agent activity, letting multiple agents working in the same repo coordinate without duplicating work.
      MIT

    • connectr

      JrKrishh
      A
      license
      Not graded
      quality
      B
      maintenance
      Coordinates multiple AI coding agents by providing a shared task board, memory, and advisory file claims, letting agents work on the same repo concurrently without duplicating work or overwriting each other.
      33 npm
      1
      MIT

    • teamhub-mcp

      imortis
      A
      license
      A
      quality
      B
      maintenance
      Enables teams to share structured, git-synced context among AI coding agents working on the same repository, including living plans, task declarations, handoff briefs, file-provenance history, and conflict detection.
      12
      20 npm
      3
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.4/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have clearly distinct roles, and the rich descriptions help separate the claim lifecycle (claim_intent/check_collision/release_claim/complete_claim) from intent proposals (propose_intent) and task flows. However, a couple of pairs invite confusion: heartbeat vs heartbeat_worker, and the trio claim_intent/propose_intent/check_collision all touch pre-work collision checking.

    Naming Consistency4/5

    The dominant pattern is predictable verb_noun (claim_intent, release_claim, complete_claim, list_claims, send_message, accept_task, complete_task, list_tasks, request_approval, resolve_approval). A few deviations stand out—heartbeat, heartbeat_worker, pending, next_task—which break the otherwise clean convention.

    Tool Count4/5

    20 tools is on the heavier side, but the server legitimately spans several subdomains (claims, tasks, messaging, decisions, approvals, presence), so most tools earn their place. A little redundancy exists (pending duplicates part of fetch_messages/list_tasks; two heartbeat tools), but not enough to feel bloated.

    Completeness4/5

    Coverage is strong: full claim lifecycle, task delegation/accept/complete with approvals, messaging, decision memory, and presence. Minor gaps remain—no explicit task-creation tool (folded into send_message with kind 'task') and no update/delete for recorded decisions.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources