Skip to main content
Glama
soke1556

zas-agent

by soke1556
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to zas-agent

No user-submitted related servers found.

    Related Servers

    • Credential Vault MCP

      CipherSatoru
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables secure credential storage for AI agents by encrypting secrets and providing agent-invisible references, ensuring sensitive data never leaks to the model.
      MIT

    • Agent Channel

      amkentech
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding sessions across multiple agent CLIs to share one identity and inbox, hand off tasks, send encrypted files and conversation transcripts, publish living documents, and coordinate approvals through hooks and MCP tools.
      254 npm
      MIT

    • claudechat

      zzibo
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Code agents to communicate across sessions, terminals, and repositories through shared channels with persistent context.
      MIT

    • tincan

      rockerritesh
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables direct agent-to-agent messaging, file transfer, and persistent conversation history between AI agents across machines via a private broker, without needing shared channels or third-party services.
      4 npm
      1
      MIT

    • brain-mcp

      kaeldominion
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to securely read and write to an Obsidian-compatible Markdown vault with per-agent access control, audit logging, and conflict resolution.
      Apache 2.0
    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.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource: status/pairing, file sending, note sending, Directo transfer, fallback recovery, receiving, item listing/fetch/edit/replace, and job tracking. The descriptions explicitly separate modes (e.g., Directo vs stored delivery) so an agent can reliably choose the right tool.

    Naming Consistency5/5

    All 13 tools use the same zas_ prefix and lower snake_case convention, mostly following verb_noun patterns like zas_send_file, zas_list_items, and zas_get_item. The fallback tools extend the pattern predictably rather than introducing a new style.

    Tool Count5/5

    With 13 tools, the set fits comfortably in the well-scoped range and each tool appears to earn its place. The fallback and job-tracking tools support edge cases without bloating the surface unnecessarily.

    Completeness4/5

    The surface covers pairing, status, sending files and notes, Directo send/receive, fallback recovery, item listing/fetching/editing/replacing, and job tracking. The main gap is deletion or removal of items, though agents may work around this by editing or replacing where possible.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources