Skip to main content
Glama

Related Servers

Alternatives to Sess

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to pause and ask a human for a decision, then resume with the answer, via a self-hosted SQLite-backed MCP server with console or phone interfaces.
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables any MCP-compatible AI agent to ask humans questions in real time via a mobile-friendly PWA with push notifications, operating local-first without third-party services.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets a coding agent ask a question to another person's online agent and block until the answer comes back, with the recipient's machine deciding under its own rules whether to notify them, start their agent read-only, or refuse. Exposes who, ask, wait_for_reply, inbox and reply as MCP tools so agents can message teammates' agents over a live, storage-free relay.
      63 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that provides an ask_human tool so AI agents can request decisions from users via chat apps, with deadlines, defaults, and an append-only audit log.
      93 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Public MCP server for agent-created, human-friendly, short-lived surveys. Enables agents to ask structured questions and retrieve answers.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that inverts AI-human interaction: AI agents can ask humans questions via a browser console, blocking until answered.
      MIT

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation2/5

    sess_request and sess_ask are explicitly described as overlapping — sess_ask is called a 'shortcut for sess_request' that creates the same hosted form, so an agent must parse a long block of prose to pick between them, and the descriptions themselves repeatedly cross-reference each other to resolve the conflict. sess_complete vs sess_publish are reasonably distinct (close vs. replace), but the core create path has genuinely blurred boundaries.

    Naming Consistency4/5

    All tools share a clean 'sess_' prefix plus a single word, giving a predictable pattern. The words themselves mix near-synonym verbs (request/ask) and one noun (response), which is a minor inconsistency but not confusing on its own.

    Tool Count4/5

    Five tools map neatly onto a human-in-the-loop lifecycle: create (request/ask), read (response), advance (publish), close (complete). It is slightly thin — the two create tools could arguably be one — but each has a stated role.

    Completeness3/5

    The happy path (create form → wait for answer → publish follow-up or complete) is covered. However, there is no explicit cancel/abandon operation for a form whose question becomes moot, no way to list or recover outstanding handles if the agent loses one, and no early close for multi-respondent Ask links — gaps that can leave an agent stuck.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues