Skip to main content
Glama
eabz

Tirith

Official
by eabz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to Tirith

  • slm-mesh

    qualixar
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables peer-to-peer communication, discovery, shared state, and file coordination between AI coding agents across machines and sessions.
    16 npm
    17
    Elastic 2.0

  • LLM Bus

    danieldoderlein
    A
    license
    B
    quality
    B
    maintenance
    MCP server that provides a live coordination layer for AI agents, including attributable handoffs, a shared event ledger, atomic work-claiming, and advisory file leases to prevent collisions.
    27
    9
    AGPL 3.0

  • dibs

    polymatx
    A
    license
    A
    quality
    A
    maintenance
    Coordination for parallel coding agents: TTL file claims stored in the git common dir (visible across all worktrees), enforcement hooks that block colliding edits, agent presence, handoff notes, and a git-committed lessons knowledge base with BM25 search. Single static Go binary — no server, no database.
    8
    2
    MIT
  • codeswarm by aaxnet

    codeswarmofficial

    aaxnet
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables controlling an autonomous multi-agent engineering swarm from MCP clients, including starting and managing tasks, spawning agents, triggering PR reviews, and checking swarm status.
    5 npm
    MIT

Related Servers

  • dibs

    Agenxy
    A
    license
    Not graded
    quality
    A
    maintenance
    MCP server enabling AI agents to coordinate on a shared board: they can declare work, exchange typed messages, transfer files, and hold advisory claims, preventing duplicate effort across agents.
    2
    GPL 3.0

  • 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
    521
    Apache 2.0

  • Agent Claim MCP

    vk0dev
    A
    license
    Not graded
    quality
    B
    maintenance
    Use Agent Claim MCP when multiple coding agents share one worktree and you need a tiny local coordination primitive before edits, not a full orchestration framework. It gives agents one job: claim paths, detect collisions, and release ownership so parallel work stops stomping the same files.
    64 npm
    MIT

  • Synapse MCP

    holaluiz
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables multiple AI coding agents to work concurrently on the same repository by coordinating task ownership, file locks, architectural decisions, investigation gaps, handoffs, and audit activity through a local SQLite-backed MCP interface.
    7 npm
    MIT
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 23 tools

Disambiguation5/5

Each tool targets a distinct primitive and action, and descriptions explicitly cross-reference alternatives (e.g., claim vs claims_list vs renew, contract_get vs contract_list). The many similar-sounding resource tools are clearly delineated by their stated use cases, so an agent can select the right one.

Naming Consistency4/5

Compound tools follow a consistent snake_case noun_verb pattern (contract_get, decision_record, task_pull), but core primitives are single words (claim, renew, release, guide, status) and 'claims_list' uses a plural resource while most others use singular. This is mostly predictable with minor deviations.

Tool Count3/5

23 tools for a multi-agent coordination daemon spanning claims, tasks, contracts, decisions, memory, messages, notices, and meta-guidance. The breadth justifies many tools, but the count sits in the heavy 16-25 range rather than the ideal 3-15.

Completeness4/5

The surface covers lifecycle operations for claims, memory, messages, notices, and contracts (via versioned publish). Tasks and decisions lack direct get/delete or update operations for some flows, but list and update calls provide workarounds, leaving only minor gaps.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources