by agentsworkingtogether
Sleep enables AI systems to add timed pauses with configurable limits for time-based coordination and rate limiting via
Adds a simple sleep function that pauses AI execution for a specified number of seconds. Useful for controlling timing and flow in automated workflows.
Sleep is a community-built MCP server published by agentsworkingtogether that provides AI assistants with tools and capabilities via the Model Context Protocol. Sleep enables AI systems to add timed pauses with configurable limits for time-based coordination and rate limiting via It is categorized under developer tools. This server exposes 1 tool that AI clients can invoke during conversations and coding sessions.
You can install Sleep in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
Apache-2.0
Sleep is released under the Apache-2.0 license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Sleep has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Sleep reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Sleep is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
I recommend Sleep for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Sleep surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We wired Sleep into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We evaluated Sleep against two servers with overlapping tools; this profile had the clearer scope statement.
Useful MCP listing: Sleep is the kind of server we cite when onboarding engineers to host + tool permissions.
Sleep is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Sleep is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
showing 1-10 of 32
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.
<a href="https://glama.ai/mcp/servers/@AgentsWorkingTogether/mcp-sleep"> <img width="380" height="200" src="https://glama.ai/mcp/servers/@AgentsWorkingTogether/mcp-sleep/badge" alt="Sleep MCP Server" /> </a>Smithery
To install Sleep MCP for Claude Desktop automatically via Smithery:
npx @smithery/cli install @AgentsWorkingTogether/mcp-sleep --client claude
mcp-get
You can install the Sleep MCP server using mcp-get:
npx @michaellatman/mcp-get@latest install mcp-sleep
MCP 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 sse
This mode is useful to integrate with an MCP client that supports SSE (like a web app).
sleep
seconds (number, max timeout config value): Seconds it will take me to tell you to continueTo 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"
]
}
}
}
<details>
<summary>Published Servers Configuration</summary>
"mcpServers": {
"mcp-sleep": {
"command": "uvx",
"args": [
"mcp-sleep"
]
}
}
</details>
To prepare the package for distribution:
uv sync
uv build
This will create source and wheel distributions in the dist/ directory.
uv publish
Note: You'll need to set PyPI credentials via environment variables or command flags:
--token or UV_PUBLISH_TOKEN--username/UV_PUBLISH_USERNAME and --password/UV_PUBLISH_PASSWORDDocker 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-sleep
Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.