Home / MCP / MCP Wait Timer Server
Provides a simple MCP wait tool to pause execution for a specified duration.
Configuration
View docs{
"mcpServers": {
"wait_timer": {
"command": "npx",
"args": [
"mcp-wait-timer"
]
}
}
}The MCP Wait Timer Server provides a simple wait tool that lets MCP clients pause execution for a specified number of seconds. This helps ensure time-dependent actions have finished before the next step runs, improving reliability in automated workflows.
You can instruct your MCP client to pause before continuing a sequence by prompting with a message like “Please wait for 10 seconds before proceeding.” The AI within your client should interpret this as a request to call the wait tool with duration_seconds set to 10. Use this approach to synchronize steps such as web page rendering, background tasks, or file operations that may still be in progress after an initial action.
Prerequisites: ensure you have Node.js version 16 or higher installed on your system.
Step 1. Configure your MCP client by adding the following block to the client’s MCP configuration. This enables the wait timer server as an available MCP endpoint.
{
"wait-timer": {
"command": "npx",
"args": ["mcp-wait-timer"],
"env": {},
"disabled": false,
"autoApprove": []
}
}Step 2. Save your changes and fully restart your MCP client application for the changes to take effect. When the client starts the server for the first time, npx will automatically download the mcp-wait-timer package if it is not already cached.
The server exposes a single stdio MCP connection named wait-timer. It is configured to run via npx with the argument mcp-wait-timer. The runtime environment is kept minimal, and no environment variables are required by default.
To use the tool, prompt the MCP client with a request such as “Please wait for 5 seconds before proceeding.” The client should then call the tool with duration_seconds set to 5, pausing the workflow for that duration.
This server is designed to help you synchronize sequential steps in MCP-powered workflows by introducing explicit delays. It is particularly useful when dealing with asynchronous actions, rendering delays, or long-running background tasks.
Pauses execution for a specified number of seconds.