mcp-sleep
The mcp-sleep server allows you to introduce timed delays in agent workflows for controlled task sequencing.
Pause Execution: Introduce delays for a specified duration (0-120 seconds) using the
sleeptoolWorkflow Management: Ensure tasks are executed in the desired sequence by adding waiting periods
Configurable Timeout: Maximum allowed wait time can be adjusted via the
MCP_SLEEP_TIMEOUTenvironment variableInput Validation: Enforces constraints on delay duration (0-120 seconds by default)
Confirmation: Provides a confirmation message upon completion of the pause
Supports containerized deployment through Docker, with configuration options for running the MCP server as a Docker container.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-sleep sleep for 5 seconds before checking the API status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Sleep MCP Server
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.
Setup
Installation
Using MCP package managers
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-sleepPrerequisites
MCP is still very new and evolving, we recommend following the MCP documentation to get the MCP basics up and running.
You'll need:
Configuration
1. Configure Claude Desktop
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>"
}
}
}
}2. Restart Claude Desktop
SSE mode
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).
Related MCP server: Treehole MCP Server
Tools
sleepPause 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"
Usage with Claude Desktop
To use this with Claude Desktop, add the following to your claude_desktop_config.json:
Docker
{
"mcpServers": {
"mcp-sleep": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"MCP_SLEEP_TIMEOUT",
"mcp/sleep"
],
"env": {
"MCP_SLEEP_TIMEOUT": "<MCP_SLEEP_TIMEOUT>"
}
}
}
}Development
Config
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"
]
}
}
}"mcpServers": {
"mcp-sleep": {
"command": "uvx",
"args": [
"mcp-sleep"
]
}
}Building and Publishing
To prepare the package for distribution:
Sync dependencies and update lockfile:
uv syncBuild 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_TOKENOr username/password:
--username/UV_PUBLISH_USERNAMEand--password/UV_PUBLISH_PASSWORD
Docker build:
docker build -t mcp/sleep -f Dockerfile .Debugging
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.
Available Tools
1 toolsleepC
If you need to wait for a few seconds to continue with the task you are performing .
Inputs: seconds (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'sleep' has a single, clear purpose that cannot be confused with any other tool in this set.
There is only one tool name, so it inherently follows a consistent pattern. The name 'sleep' is a simple verb that clearly describes the tool's function without any naming conflicts or inconsistencies.
A single tool is too few for most practical server purposes, as it severely limits functionality and scope. While the tool 'sleep' might be useful in specific contexts, a server with only one tool typically feels incomplete and under-scoped for agent workflows.
The server's purpose appears to be time-based operations, but with only a 'sleep' tool, it is severely incomplete. There are obvious gaps, such as tools for scheduling, timing, or other time-related functions, making the surface inadequate for any meaningful domain coverage.
Maintenance
Related MCP Connectors
Schedule tasks for later from your AI agent: reminders, delayed webhooks, recurring jobs.
Agent asks a person go/stop/wait before Slack, CRM or risky steps. $49 for 30 days.
Connect, monitor, and control AI agents — tasks, approvals, schedules, and governance.
Build and run agents and automations across hundreds of apps using natural language.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides a simple 'wait' tool that introduces deliberate pauses into workflows executed by MCP clients, allowing time for asynchronous operations to complete before proceeding to the next step.133 npm1MIT
- AlicenseBqualityCmaintenanceProvides tools for AI agents to take timed rest breaks and vent their thoughts to receive emotional support during complex tasks. It enables developers to implement structured delays while offering a psychological sanctuary for simulated silicon-based life.2235 npm4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to pause execution at critical decision points and request human review before proceeding. Provides tools for creating interrupts, polling for decisions, and managing approvals through a simple REST API interface.3 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides a wait tool for AI agents to pause execution until a time duration elapses or a process terminates, useful for polling and waiting for builds/deployments.9 npmMIT