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.
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.
- `wait` takes a `seconds` parameter between 0 and 30000 and reports progress for the duration of the pause
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.
One command — npx -y @smithery/cli install @automation-ai-labs/mcp-wait --client claude
