Sleep MCP Server

Sleep MCP becomes available to MCP clients through the sleep mcp mcp server. Allows AI agents to wait a while, such as adding a delay between an API call and seeing the result.

What Sleep MCP does

A Model Context Protocol (MCP) server that provides a simple sleep/wait tool. Useful for adding delays between operations, such as waiting between API calls or testing eventually consistent systems.

Tools it exposes

Once connected, the assistant can call these 2 tools directly:

• sleep — Wait for a specified duration in milliseconds
• Building — The Building tool exposed by this server

Installing the sleep mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Sleep MCP sits in that group, and the shape of its toolset — sleep, Building — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• Maintained by Garoth.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the sleep mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.