Skip to main content
Glama
zxc972

Local AI Relay

by zxc972
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Local AI Relay

No user-submitted related servers found.

    Related Servers

    • agent-bus-mcp

      tulong66
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents from different frameworks to communicate asynchronously via a persistent SQLite-backed bus, with doorbell wakeups for sub-second notifications and full message history.
      6
      MIT

    • Guichet

      valx-vex
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding-agent sessions to post and collect durable letters through a fully local, SQLite-backed post office, with delivery retried across restarts until the recipient acknowledges. Any MCP client or shell-capable agent can use it to send, read, acknowledge, and review the history of messages between sessions.
      32 npm
      AGPL 3.0

    • GhostPaw Email

      GhostPawJS
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM agents to sync and manage IMAP/SMTP mailboxes through a local SQLite cache, covering folder and thread reading, FTS5 search, composing, replying, forwarding, and flag/label organization. Works without credentials for cached reads and supports a CLI tool surface alongside the MCP interface.
      1,498 npm
      1
      MIT

    • Durebak

      ggujunhi247
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding-agent sessions on the same machine to collaborate locally and durably by exchanging requests, replies, and task results through an authenticated loopback server with SQLite-backed storage, joined via CLI or an MCP stdio bridge. It also handles message delivery by priority and wait time, deduplicates idempotent sends, enforces task versioning, and preserves artifacts by content hash.
      10 npm
      Apache 2.0
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool targets a distinct phase of the chat lifecycle, and the dense descriptions explicitly contrast the risky pairs: chat_receive (claim once) vs chat_context (read without ACK), and chat_ack vs chat_send's implicit reply_to/delivery_id confirmation. The overlap between chat_send's built-in ACK and chat_ack, plus the read-oriented split between receive/context, means an agent can still misselect without reading the fine print, but boundaries are documented.

    Naming Consistency5/5

    All nine tools use the same chat_<verb> snake_case pattern (create, join, status, send, receive, ack, context, checkpoint, leave). No mixed conventions or vague verbs; names map cleanly onto the described actions.

    Tool Count5/5

    Nine tools is well-scoped for a relay/chat-room protocol: session lifecycle (create/join/leave), messaging (send/receive/ack), and state (status/context/checkpoint). Nothing appears redundant at the surface level given the v2 protocol's deliberate send/receive/ack split.

    Completeness4/5

    Coverage of the agent-facing chat loop is strong: create, join, leave, send, receive, ack, inspect status, restore context, and checkpoint. Gaps are minor — there is no room discovery/listing tool (join presumes a known room id), no member management (invite/kick), and no room teardown, which agents must work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources