Skip to main content
Glama
Garoth

Sleep MCP Server

by Garoth
README.md
# Sleep MCP Server

<img src="assets/sleep-server.png" width="256" alt="Sleep MCP Logo" />

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.

## Available Tools

- `sleep`: Wait for a specified duration in milliseconds

## Installation

```bash
git clone https://github.com/Garoth/sleep-mcp.git
npm install
```

## Configuration

Add to your Cline MCP settings file (ex. ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json):

```json
{
  "mcpServers": {
    "sleep": {
      "command": "node",
      "args": ["/path/to/sleep-server/build/index.js"],
      "disabled": false,
      "autoApprove": [],
      "timeout": 300
    }
  }
}
```

> **Note:** The `timeout` parameter specifies the maximum time (in milliseconds) that the MCP server will wait for a response before timing out. This is particularly important for the sleep tool, as setting a timeout that's shorter than your sleep duration will cause the operation to fail. Make sure your timeout value is always greater than the maximum sleep duration you plan to use.

## Development

### Setting Up Tests

The tests verify the sleep functionality with various durations:

```bash
npm test
```

### Building

```bash
npm run build
```

## License

MIT

TDQS

B3.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it to. The tool's purpose is singular and clearly defined, eliminating any ambiguity.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other names to compare it against. The tool name 'sleep' is straightforward and follows a simple verb pattern, which is consistent in this minimal context.

Tool Count2/5

A single tool for a server named 'Sleep MCP Server' feels thin and under-scoped, as it only provides a basic waiting function without any related operations like scheduling, monitoring, or configuration. This minimal set may not fully represent a server's purpose beyond a trivial utility.

Completeness1/5

The server is severely incomplete for any meaningful domain beyond a simple delay function; there are no tools for related tasks such as setting alarms, managing sleep schedules, or handling interruptions. This single tool offers no coverage for a broader sleep-related workflow, leading to significant gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues