Skip to main content
Glama
onicarps

agentbus

by onicarps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agentbus

No user-submitted related servers found.

    Related Servers

    • Frontispice

      bhind
      A
      license
      A
      quality
      B
      maintenance
      MCP server for local-first agent handoff: enables AI sessions to publish curated context, list/read updates, route handoffs to specialists, and advance per-consumer cursors, with SQLite persistence and no shell or network access.
      8
      Apache 2.0

    • Claude State MCP Server

      mfitzhenry
      F
      license
      Not graded
      quality
      D
      maintenance
      SQLite-backed MCP server for Claude Code session persistence and multi-agent coordination. Provides tools for session management, event logging, decision tracking, file locking, agent registry, and plan tracking.
      -

    • nuzo-memory

      fabionfsc
      A
      license
      Not graded
      quality
      F
      maintenance
      Local-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.
      2
      Apache 2.0
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: publishing vs polling events, reviewing/approving/rejecting pending events, and lock status/acquire/release/renew are all separate actions. No two tools overlap in function.

    Naming Consistency4/5

    All tools use the 'agentbus_' prefix consistently, but the verb/noun order is not uniform. Event-related tools are verb-only (publish, poll, review), while lock tools use noun-first (lock_acquire, lock_release) and status tools are noun-only (status, lock_status). Despite this, the naming is still predictable and readable.

    Tool Count5/5

    10 tools is well-scoped for the domain of an agent communication bus. It covers the core event lifecycle (publish/poll), human approval workflow (review/approve/reject), and advisory locking (acquire/release/renew/status) without unnecessary bloat.

    Completeness5/5

    The tool set covers the full event bus lifecycle: publishing, polling, and health status. The approval workflow is complete with review, approve, and reject. Locking includes status, acquire, release, and renew, leaving no obvious gaps for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources