Skip to main content
Glama

Related Servers

Alternatives to mcp-sleep

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides a simple 'wait' tool that introduces deliberate pauses into workflows executed by MCP clients, allowing time for asynchronous operations to complete before proceeding to the next step.
      1
      13 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A minimal MCP server that lets AI agents pause for a specified duration before resuming their workflow. Useful for polling patterns like waiting for PR approval or file creation.
      1
      5 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Provides tools for AI agents to take timed rest breaks and vent their thoughts to receive emotional support during complex tasks. It enables developers to implement structured delays while offering a psychological sanctuary for simulated silicon-based life.
      2
      13 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides a wait tool for AI agents to pause execution until a time duration elapses or a process terminates, useful for polling and waiting for builds/deployments.
      5 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      A minimal MCP server that gives AI agents the ability to pause execution by waiting a specified number of seconds, with support for local and AWS AgentCore deployment.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to pause execution at critical decision points and request human review before proceeding. Provides tools for creating interrupts, polling for decisions, and managing approvals through a simple REST API interface.
      4 npm
      MIT

    TDQS

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'sleep' has a single, clear purpose that cannot be confused with any other tool in this set.

    Naming Consistency5/5

    There is only one tool name, so it inherently follows a consistent pattern. The name 'sleep' is a simple verb that clearly describes the tool's function without any naming conflicts or inconsistencies.

    Tool Count2/5

    A single tool is too few for most practical server purposes, as it severely limits functionality and scope. While the tool 'sleep' might be useful in specific contexts, a server with only one tool typically feels incomplete and under-scoped for agent workflows.

    Completeness1/5

    The server's purpose appears to be time-based operations, but with only a 'sleep' tool, it is severely incomplete. There are obvious gaps, such as tools for scheduling, timing, or other time-related functions, making the surface inadequate for any meaningful domain coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues