waitLABSCO SUMMARY
One tool, no configuration, no credentials.
There is nothing to evaluate here beyond whether you need it: a deliberate pause between tool calls is something most agent runtimes have no primitive for. The progress reporting is the part that matters — a long, silent wait looks like a hang to the client.
What it is
A single-purpose server for the gap between two steps: an agent that has just triggered a build, a deploy or a background job can hold for a fixed interval instead of polling or guessing.
What you get
waittakes asecondsparameter between 0 and 30000 and reports progress for the duration of the pause
Requirements
The npm package @automation-ai-labs/mcp-wait, version 1.0.3, run over npx with TRANSPORT_TYPE set to stdio. Setting TRANSPORT_TYPE to sse and choosing a PORT serves it over SSE instead. No account, no key.
Setup effort
Add the configuration to your client
USE CASES
01
Letting a deploy settle before checking it
Pause between triggering the job and reading its status, instead of asking repeatedly and getting a stale answer.
02
Spacing out calls to a rate-limited API
Put a fixed gap between requests so the next one is not rejected.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
npx on PATH
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
MCP Clients
Claude Desktop, Cursor, ChatWise
JSON
{
"mcpServers": {
"mcp-wait": {
"command": "npx",
"args": [
"-y",
"@automation-ai-labs/mcp-wait"
],
"env": {
"TRANSPORT_TYPE": "stdio"
}
}
}
}
