Skip to main content
Glama
enesjakozh
automation-ai-labs

MCP-Wait

by automation-ai-labs
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

MCP-Wait

A simple MCP server that provides waiting functionality to pause until other tasks finish.

Features

  • Wait for a specified number of seconds

  • Progress reporting during waiting

  • Simple to use via CLI or as an HTTP server with SSE

Related MCP server: async-bash-mcp

Integration with Claude Desktop/Cursor/Chatwise

To use with Claude Desktop, add the following to your configuration:

{
  "mcpServers": {
    "mcp-wait": {
      "command": "npx",
      "args": [
        "-y",
        "@automation-ai-labs/mcp-wait"
      ],
      "env": {
        "TRANSPORT_TYPE": "stdio"
      }
    }
  }
}

Installation

Installing via Smithery

To install Wait for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @automation-ai-labs/mcp-wait --client claude

Manual Installation

npm install

Usage

CLI Testing

Test the server directly using the FastMCP CLI:

npm run dev

This will start the server and let you interact with it through the CLI.

Inspect with MCP Inspector

Inspect the server using the MCP Inspector web UI:

npm run inspect

Start as SSE Server

Start the server with SSE support for integrating with other applications:

TRANSPORT_TYPE=sse PORT=8080 npm start

Wait Tool

The server provides a simple wait tool that accepts a seconds parameter:

  • seconds: The number of seconds to wait (0-30000)

Example:

{
  "seconds": 5
}

This will wait for 5 seconds and report progress during the wait.

Available Tools

1 tool
waitB

Wait for a specified number of seconds, useful for waiting for other tasks to finish

ParametersJSON Schema
NameRequiredDescriptionDefault
secondsYesThe number of seconds to wait (0-300)

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the tool's utility but fails to describe key behavioral traits such as whether the wait is blocking, if it can be interrupted, error handling, or side effects. This is a significant gap for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded, consisting of a single, efficient sentence that conveys the core purpose. There is no wasted text, though it could be slightly more structured for clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity and 100% schema coverage, the description is somewhat adequate but incomplete. It lacks details on behavioral aspects (e.g., blocking nature, error handling) and output (no output schema provided), which are important for a wait tool with no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, with the parameter 'seconds' fully documented in the schema (type, range, description). The description adds no additional meaning beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without extra param info.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('wait') and resource ('seconds'), and explains its utility ('useful for waiting for other tasks to finish'). It distinguishes the tool's function effectively, though it lacks explicit differentiation from siblings (none provided).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context ('waiting for other tasks to finish'), providing some guidance on when to use the tool. However, it does not offer explicit alternatives, exclusions, or detailed prerequisites, leaving room for clearer operational guidelines.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0
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

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • 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
    6
    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

  • mcp-wait

    lzientek
    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
    17
    MIT

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

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/automation-ai-labs/mcp-wait'

If you have feedback or need assistance with the MCP directory API, please join our Discord server