- Home
- MCP servers
- MCP-Wait
MCP-Wait
- javascript
5
GitHub Stars
javascript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"automation-ai-labs-mcp-wait": {
"command": "npx",
"args": [
"-y",
"@automation-ai-labs/mcp-wait"
],
"env": {
"TRANSPORT_TYPE": "stdio"
}
}
}
}MCP-Wait is a compact MCP server that pauses execution for a specified duration while providing progress updates. It’s useful for coordinating tasks in an MCP workflow where one step must wait for others to finish before continuing.
How to use
You can integrate MCP-Wait into your workflow as a stdio MCP server or test it locally via the CLI. It supports waiting for a defined number of seconds and reporting progress during the wait. The server can also run as an SSE-enabled HTTP endpoint for easy integration with other applications.
How to install
Prerequisites you need on your system before installing MCP-Wait:
- Node.js and npm installed
- Network access to install npm packages
Step 1: Install MCP-Wait via Smithery (recommended for Claude Desktop integration):
npx -y @smithery/cli install @automation-ai-labs/mcp-wait --client claude
Step 2: Manual installation (useful if you prefer local setup):
npm install
Additional setup and run instructions
To run and test MCP-Wait locally, you have several options depending on how you want to integrate it with your tooling.
# Start the server for CLI testing (uses the package’s dev script)
npm run dev
Inspect the server’s status and capabilities with the MCP Inspector web UI (CLI-based inspection command):
npm run inspect
Start the server with SSE support for integration with other applications (example shows setting transport type and port):
TRANSPORT_TYPE=sse PORT=8080 npm start
Wait Tool
The server provides a wait tool that pauses for a given number of seconds and reports progress along the way. You can configure the duration in seconds (0–30000).
{
"seconds": 5
}