wait
Waits for a specified duration in seconds.
LABSCO SUMMARY
One tool, one parameter, and no opinion about what you are waiting for.
wait blocks for duration_seconds and returns. There is no condition to poll, nothing to cancel and no notion of what the delay is for, which means the caller decides how long is long enough and re-checks the thing it was waiting on itself. That is the whole surface, and it is worth reading as a deliberate boundary rather than a gap: a timer that knows nothing about your job cannot get your job wrong.
What it is
A single-tool server whose only tool, wait, blocks for the number of seconds given in duration_seconds.
What you get
- A pause the model can request for itself: wait takes duration_seconds and returns once that time has elapsed.
Requirements
Nothing to supply: no account, no key.
Setup effort
One command — npx -y mcp-wait-timer
USE CASES
01
Pausing between steps that need time to settle
Ask for the delay explicitly in seconds, and let the run continue when it is over.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
npx on PATH
Where it runs
All 4 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y mcp-wait-timerMCP Clients
Claude Desktop, Cline, Cursor, Windsurf
JSON
{
"mcpServers": {
"wait-timer": {
"command": "npx",
"args": [
"mcp-wait-timer"
],
"env": {},
"disabled": false,
"autoApprove": []
}
}
}
