This MCP server attempts to pause execution for a specified duration to control the flow of your agents. Enhance your automation by introducing timed delays, ensuring tasks are executed in the desired sequence. Ideal for managing workflows that require waiting periods between actions.
Smithery
To install Sleep MCP for Claude Desktop automatically via Smithery:
npx @smithery/cli install @AgentsWorkingTogether/mcp-sleep --client claudemcp-get
You can install the Sleep MCP server using mcp-get:
npx @michaellatman/mcp-get@latest install mcp-sleepMCP is still very new and evolving, we recommend following the MCP documentation to get the MCP basics up and running.
You'll need:
Create the following file depending on your OS:
On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
Paste this template in the file
{
"mcpServers": {
"mcp-sleep": {
"command": "uvx",
"args": [
"mcp-sleep"
],
}
}
}Optionally, it replace <MCP_SLEEP_TIMEOUT> with your timeout ( maximum time allowed to wait, default 60 seconds ):
{
"mcpServers": {
"mcp-sleep": {
"command": "uvx",
"args": [
"mcp-sleep"
],
"env": {
"MCP_SLEEP_TIMEOUT": "<MCP_SLEEP_TIMEOUT>"
}
}
}
}Alternatively, you can run the MCP server in SSE mode by running the following command:
uvx mcp-sleep --transport sseThis mode is useful to integrate with an MCP client that supports SSE (like a web app).
sleep- Pause execution for a specified duration to control the flow of your agents.
- Inputs:
seconds(number, max timeout config value): Seconds it will take me to tell you to continue
- Returns: You will receive the sentence after {seconds} "You can continue to do your task after you've been waiting {seconds} seconds". If you enter a waiting time greater than the maximum time the result will be "My configuration does not allow me to make you wait more than {ctx.sleep.config.timeout} seconds"
To use this with Claude Desktop, add the following to your claude_desktop_config.json:
{
"mcpServers": {
"mcp-sleep": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MCP_SLEEP_TIMEOUT",
"mcp/sleep"
],
"env": {
"MCP_SLEEP_TIMEOUT": "<MCP_SLEEP_TIMEOUT>"
}
}
}
}If you are working locally add two environment variables to a .env file in the root of the repository:
MCP_SLEEP_TIMEOUT=For local development, update your Claude Desktop configuration:
{
"mcpServers": {
"mcp-sleep_local": {
"command": "uv",
"args": [
"run",
"--directory",
"/path/to/your/mcp-sleep",
"run",
"mcp-sleep"
]
}
}
}Published Servers Configuration
"mcpServers": {
"mcp-sleep": {
"command": "uvx",
"args": [
"mcp-sleep"
]
}
}To prepare the package for distribution:
- Sync dependencies and update lockfile:
uv sync- Build package distributions:
uv buildThis will create source and wheel distributions in the dist/ directory.
- Publish to PyPI:
uv publishNote: You'll need to set PyPI credentials via environment variables or command flags:
- Token:
--tokenorUV_PUBLISH_TOKEN - Or username/password:
--username/UV_PUBLISH_USERNAMEand--password/UV_PUBLISH_PASSWORD
Docker build:
docker build -t mcp/sleep -f Dockerfile .Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.
You can launch the MCP Inspector via npm with this command:
npx @modelcontextprotocol/inspector uv --directory /path/to/your/mcp-sleep run mcp-sleepUpon launching, the Inspector will display a URL that you can access in your browser to begin debugging.