MCP-Wait is an MCP server that pauses execution within an agentic workflow to allow external tasks or asynchronous processes to finish. Developed by automation-ai-labs, the server exposes a simple delay mechanism designed for integration with AI assistants like Claude Desktop, Cursor, and Chatwise. Developers and automation engineers use it when coordinating multi-step agent actions that depend on long-running background jobs, build scripts, API rate-limit delays, or web scraping cycles. Instead of forcing an LLM to hallucinate polling logic or fail due to timing mismatches, MCP-Wait provides a structured tool to pause execution for a designated duration. During the pause, the tool provides continuous progress updates back to the client interface. The server supports standard standard-input/output (stdio) communication for local desktop clients and Server-Sent Events (SSE) mode for remote network architectures.
Category: Developer Tools & Code Intelligence
Tags: automation, task-scheduling, utility, workflow
Follow these steps to configure MCP-Wait in Claude Desktop: 1. Open your Claude Desktop configuration file (claude_desktop_config.json). 2. Add the mcp-wait configuration under the mcpServers object: json { "mcpServers": { "mcp-wait": { "command": "npx", "args": [ "-y", "@automation-ai-labs/mcp-wait" ], "env": { "TRANSPORT_TYPE": "stdio" } } } } 3. Alternatively, install automatically using the Smithery CLI by running npx -y @smithery/cli install @automation-ai-labs/mcp-wait --client claude. 4. Restart Claude Desktop to start using the wait tool.
Part of MCP Servers
You can install MCP-Wait automatically for Claude Desktop using the Smithery CLI by running the command npx -y @smithery/cli install @automation-ai-labs/mcp-wait --client claude. Alternatively, you can add it directly to your configuration using npx to execute @automation-ai-labs/mcp-wait, or clone the repository and run npm install.
MCP-Wait exposes a wait tool that halts tool execution for a specified number of seconds ranging from 0 to 30000. While the pause is active, the server transmits ongoing progress reporting back to the client, preventing connection timeouts during delayed agent workflows.
MCP-Wait works with any Model Context Protocol compliant client that supports stdio or SSE transports. Explicit support and tested configurations include Claude Desktop, Cursor, and Chatwise. You can also test and inspect it directly with the FastMCP CLI or the MCP Inspector UI.
Yes, MCP-Wait can be deployed as an HTTP server running Server-Sent Events rather than local stdio. Setting the environment variable TRANSPORT_TYPE to sse and defining a PORT allows external or networked applications to connect directly to the server.