Skip to main content
Glama
adlternative

await-mcp

by adlternative
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to await-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-wait

      AaLexUser
      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

    • MCP Wait Timer Server

      199-mcp
      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

    • 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

    • goal-engine

      melihzafer
      F
      license
      A
      quality
      D
      maintenance
      Provides persistent goal-tracking with external evaluation for agentic CLIs, enabling run-until-done loops where an agent works across turns until a condition is met.
      4
      -

    • glasspulse

      MountainLabsDE
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query and monitor service status, latency, and performance through configurable checks (HTTP, TCP, SSL, keyword, JSON-path) and exposes tools for listing services, retrieving metrics, and running on-demand checks.
      Apache 2.0
    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

    A4.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct condition type: shell command, URL, or file. The purpose of each is clear, and there is no meaningful overlap in their intended use cases. An agent can easily select the right tool based on the resource it needs to wait on.

    Naming Consistency5/5

    All tools follow the consistent verb_noun pattern of 'await_' followed by the target resource (command, url, file). This makes the tool names predictable and easy to remember. The naming convention is uniform throughout the set.

    Tool Count5/5

    With three tools, the server is well-scoped for its purpose of providing wait-for-condition primitives. Each tool covers a distinct and common category of waiting (shell, HTTP, file), so the count feels neither thin nor excessive for the domain.

    Completeness5/5

    The three tools cover the primary methods for blocking on external signals: command exit status, URL availability/response, and file presence/content. This set provides a solid foundation for waiting on common CI/CD, deployment, and build scenarios. While a generic 'sleep' tool is absent, the command-based approach can handle arbitrary delays, making the surface reasonably complete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources