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.
    49 npm
    19
    Elastic 2.0

  • LLM Bus

    danieldoderlein
    A
    license
    B
    quality
    C
    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
    Apache 2.0

  • Foremerge

    naw103
    A
    license
    B
    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
    304
    Apache 2.0

  • Agent Claim MCP

    vk0dev
    A
    license
    Not graded
    quality
    A
    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.
    26 npm
    MIT
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 23 tools

Disambiguation5/5

Each tool maps to a distinct resource/action: lease acquisition, inspection, renewal, and release are separate, and contract, memory, decision, message, notice, and task tools are clearly scoped. Potentially overlapping pairs like contract_publish/notice_publish and memory_write/decision_record are explicitly differentiated in their descriptions.

Naming Consistency4/5

Most tools follow a clear resource_action pattern (contract_get, memory_write, task_update, notice_publish). However, bare verbs and nouns such as claim, release, renew, status, and guide, plus the plural claims_list, break the pattern slightly while remaining predictable.

Tool Count4/5

23 tools is on the heavy side, but the server covers seven distinct coordination primitives: leases, contracts, memory, decisions, messages, notices, and tasks. Each tool has a distinct job, so the count is reasonable for the scope even though it exceeds the typical concise range.

Completeness4/5

The toolset provides a usable lifecycle for each domain: claims support acquire/list/renew/release, memory supports full CRUD plus search, tasks support create/list/pull/update, and contracts support publish/list/get with versioning. Minor gaps such as the absence of a full single-task getter and no explicit contract deprecation are workable through existing update and versioning mechanisms.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources