Skip to main content
Glama
lokeshrana9999

claude-session-manager

Related Servers

Alternatives to claude-session-manager

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact programmatically with Claude Code CLI, managing sessions, streaming outputs, and handling permission requests.
      7
      6 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables a Claude Desktop or Claude Code session to start, drive, and supervise interactive Claude Code CLI worker runs, including sending prompts, reading terminal output, waiting for completion, stopping runs, and managing settings and permissions.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables ISLI agents and MCP clients to dispatch natural-language coding and terminal tasks to a locally-installed Claude Code CLI, supporting both one-shot execution and persistent sessions with workspace and security controls.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Wraps Claude Code as tools for MCP clients, enabling autonomous coding tasks via a 4-tool lifecycle with session management, async polling, and permission controls.
      4
      40 npm
      20
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Lets AI agents create and drive Claude Code cloud sessions natively over stdio, exposing typed tools to start a session from a task description, queue follow-up messages into an existing session, and check the CLI's sign-in state. Each tool maps to a fixed Claude Code CLI invocation with strict schemas and structured JSON results, so agents never write shell commands or run local sessions.
      3
      48 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool has a distinct lifecycle role: start vs send, stop vs ack, and list vs status vs tail vs result vs wait are differentiated in the descriptions. The main potential confusion is among the read-oriented tools (status, result, tail, wait), but the wording makes their boundaries reasonably clear.

    Naming Consistency5/5

    All nine tools use the same session_<verb> convention, with clear and predictable verbs. There are no mixed casing or naming style deviations.

    Tool Count5/5

    Nine tools is a well-scoped set for a session manager, covering creation, observation, follow-up, stopping, and acknowledgment. No tool appears redundant or out of place.

    Completeness4/5

    The set covers the core session lifecycle: start, list, status, tail, result, follow-up, stop, wait, and ack. Minor gaps exist around full transcript access or explicit history cleanup/deletion, but agents can work around these for typical session management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues