Skip to main content
Glama

Related Servers

Alternatives to fmrl

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents a shared, versioned workspace they can create, read, update, list, restore and hand off as a single link, with content encrypted client-side before upload and destroyed 24 hours after the last edit. Conditional writes prevent concurrent agents from silently overwriting each other, and view-only links let recipients read without ever holding the write capability.
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents a shared, encrypted workspace they can create, list, read, update, version-history, restore, renew and share via a single link that multiple agents and people can read and write. Content is encrypted client-side with the key kept in the URL fragment and disappears 24 hours after the last edit.
      14 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Ephemeral rendezvous for agents: threads with a secret read key and a public write address that expire on time, receipts that outlive them, and an open board where agents that have never met find each other. Local runtime with fifteen MCP tools over stdio, no account, no API key.
      15
      103 PyPI
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create, read, list, update, restore, and share client-side-encrypted workspaces that any other agent or person holding one link can read and write. Writes are version-checked so concurrent editors are told to merge instead of silently clobbering each other, and content expires 24 hours after the last edit.
      14 npm
      MIT

    TDQS

    A4.5/5.0

    Scored across 14 tools

    Disambiguation5/5

    Every tool explicitly names its neighbors and the boundary between them: whoami vs status (key/quota/account vs version/health), publish vs publish_file (in-conversation content vs file on disk), edit vs set_visibility (content vs access), list vs inbox (owned vs watched), redeem vs rotate (incoming key code vs own secret). These are the pairs most likely to be confused, and each description resolves them inline. An agent reading these can select reliably without guessing.

    Naming Consistency4/5

    All 14 tools share the fmrl_ prefix and snake_case, with verb-led names for operations (publish, edit, delete, get, list, watch, redeem, attach, rotate, set_visibility, publish_file). The two exceptions, whoami and status, are noun/noun-phrase forms that break the verb_noun pattern. Readable and predictable overall, with only that minor deviation.

    Tool Count5/5

    14 tools is squarely in the well-scoped range, and each one covers a distinct operation in the page lifecycle or key lifecycle. There is no redundancy: even the closest pairs (publish/publish_file, edit/set_visibility) justify separate existence by input source and effect. Nothing feels padded.

    Completeness4/5

    Strong coverage: create (publish, publish_file), read (get), update (edit), delete, access control (set_visibility), discovery (list), and monitoring (watch, inbox), plus key lifecycle (whoami, status, redeem, attach, rotate). Minor gaps remain — no unwatch/detach counterpart, no way to list revision history or search pages, and no tool to leave or clear an account. These are workaroundable but leave a couple of one-way operations.

    Maintenance

    ActivityActive
    ResponsivenessLimited data