Skip to main content
Glama
Dicklesworthstone

MCP Agent Mail

by Dicklesworthstone
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to MCP Agent Mail

No user-submitted related servers found.

    Related Servers

    • MCP Agent Mail

      OmelchMichael
      A
      license
      Not graded
      quality
      D
      maintenance
      A coordination layer for coding agents that provides identities, message threading, and searchable history. It features file reservation leases to prevent agents from overwriting each other's work in multi-agent environments.
      1
      MIT

    • mcp_mail

      jleechanorg
      A
      license
      Not graded
      quality
      F
      maintenance
      A mail-like coordination layer for coding agents, providing identities, inbox/outbox, searchable threads, and advisory file reservations to prevent conflicts in multi-agent workflows.
      34 PyPI
      1
      MIT

    • 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

    • Shift MCP Server

      cyanheads
      A
      license
      Not graded
      quality
      A
      maintenance
      A lightweight coordination layer for multiple AI agents working on the same codebase, providing check-in and check-out tools via STDIO or Streamable HTTP.
      70 npm
      1
      Apache 2.0

    • MCP Agent Mail

      WhienLiou
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a mail-like coordination layer for coding agents, enabling them to register identities, exchange messages through inbox/outbox, search threaded history, and declare advisory file reservations to prevent conflicts.
      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

    B3.2/5.0

    Scored across 41 tools

    Disambiguation3/5

    Most tools target distinct resources and actions, but several clusters overlap: agent lifecycle (register/create/deregister/retire/unretire), message state (mark read vs acknowledge), summary views (fetch/summarize thread/recent), and macro helpers duplicate lower-level operations. Detailed descriptions disambiguate some overlaps, but the set still requires careful selection.

    Naming Consistency4/5

    Nearly all names use snake_case and follow verb_noun or resource_action patterns, such as ensure_project, send_message, and release_file_reservations. Minor deviations like whois and a few long macro_* names slightly reduce predictability, but overall the naming is consistent.

    Tool Count2/5

    41 tools is far above a well-scoped set for one MCP server; it mixes core messaging, admin, contact, reservation, summary, guard, and macro operations. Although each tool may earn its place, the volume increases selection burden and feels heavy for the domain.

    Completeness4/5

    The surface covers project and agent lifecycle, messaging, contacts, file reservations, summaries, and pre-commit guards comprehensively. Minor gaps include no direct list_projects/list_agents tool and no edit/delete individual message, but resource-based discovery and purge/archive paths mitigate these.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources