Skip to main content
Glama
automation-ai-labs

MCP-Wait

by automation-ai-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to MCP-Wait

No user-submitted related servers found.

    Related Servers

    • timer-mcp

      tharun52
      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.
      -

    • mcp-wait

      lzientek
      A
      license
      A
      quality
      D
      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
      2 npm
      MIT

    • Sleep MCP Server

      Garoth
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides a simple sleep/wait tool, useful for adding delays between operations such as waiting between API calls or testing eventually consistent systems.
      1
      10 npm
      21
      ISC

    • async-bash-mcp

      xhuw
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for spawning and managing bash commands asynchronously. Run multiple shell commands in parallel and check their progress independently.
      6
      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 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.

    Naming Consistency5/5

    Since there is only one tool, it inherently follows a consistent naming pattern with itself. The name 'wait' is straightforward and matches the verb_noun style, though no pattern can be assessed across multiple tools.

    Tool Count2/5

    A single tool is generally too few for most server purposes, as it limits functionality and suggests a very narrow scope. While the tool is useful for waiting, it lacks companion tools for broader task management or integration, making the server feel incomplete.

    Completeness1/5

    The server's purpose appears to be related to task management or timing, but with only a 'wait' tool, there are significant gaps. There are no tools for starting, monitoring, or canceling tasks, making the surface severely incomplete for any practical workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources