Skip to main content
Glama

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

Inputs: seconds (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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 recent community issues

    Related MCP Connectors

    Related MCP Servers

    • 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
      4 npm
      22
      ISC
    • 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
    • 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
      7 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      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.
      -