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