Skip to main content
Glama
enesjakozh
AgentsWorkingTogether

mcp-sleep

by AgentsWorkingTogether
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

睡眠 MCP 服务器

铁匠徽章

此 MCP 服务器会尝试暂停执行指定时间，以控制代理的流量。通过引入定时延迟来增强自动化，确保任务按所需顺序执行。非常适合管理操作之间需要等待一段时间的工作流。

设置

安装

使用 MCP 包管理器

锻造工艺

要通过Smithery自动为 Claude Desktop 安装 Sleep MCP：

npx @smithery/cli install @AgentsWorkingTogether/mcp-sleep --client claude

mcp-获取

您可以使用mcp-get安装 Sleep MCP 服务器：

npx @michaellatman/mcp-get@latest install mcp-sleep

先决条件

MCP 仍然非常新并且正在不断发展，我们建议遵循MCP 文档来了解并运行 MCP 基础知识。

你需要：

配置

1.配置Claude桌面

根据您的操作系统创建以下文件：

在 MacOS 上： ~/Library/Application\ Support/Claude/claude_desktop_config.json

在 Windows 上： %APPDATA%/Claude/claude_desktop_config.json

将此模板粘贴到文件中

{
    "mcpServers": {
        "mcp-sleep": {
            "command": "uvx",
            "args": [
                "mcp-sleep"
            ],
        }
    }
}

或者，用您的超时值（允许等待的最长时间，默认为 60 秒）替换<MCP_SLEEP_TIMEOUT> ：

{
    "mcpServers": {
        "mcp-sleep": {
            "command": "uvx",
            "args": [
                "mcp-sleep"
            ],
            "env": {
                "MCP_SLEEP_TIMEOUT": "<MCP_SLEEP_TIMEOUT>"
            }
        }
    }
}

2. 重启 Claude Desktop

SSE 模式

或者，您可以通过运行以下命令以 SSE 模式运行 MCP 服务器：

uvx mcp-sleep --transport sse

此模式对于与支持 SSE 的 MCP 客户端（如 Web 应用程序）集成很有用。

Related MCP server: Treehole MCP Server

工具

  1. sleep

    • 暂停执行指定的时间以控制代理的流量。

    • 输入：

      • seconds （数字，最大超时配置值）：我需要多少秒才能告诉您继续

    • 返回：{seconds} 秒后，您将收到“您可以等待 {seconds} 秒后继续执行您的任务”的语句。如果您输入的等待时间大于最大时间，则结果将为“我的配置不允许我让您等待超过 {ctx.sleep.config.timeout} 秒”。

与 Claude Desktop 一起使用

要将其与 Claude Desktop 一起使用，请将以下内容添加到您的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>"
      }
    }
  }
}

发展

配置

如果您在本地工作，请将两个环境变量添加到存储库根目录中的.env文件：

MCP_SLEEP_TIMEOUT=

对于本地开发，请更新您的 Claude Desktop 配置：

{
  "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"
    ]
  }
}

构建和发布

准备分发包：

  1. 同步依赖项并更新锁文件：

uv sync

  1. 构建软件包分发版：

uv build

这将在dist/目录中创建源和轮子分布。

  1. 发布到 PyPI：

uv publish

注意：您需要通过环境变量或命令标志设置 PyPI 凭据：

  • 令牌： --token或UV_PUBLISH_TOKEN

  • 或用户名/密码： --username / UV_PUBLISH_USERNAME和--password / UV_PUBLISH_PASSWORD

Docker 构建：

docker build -t mcp/sleep -f Dockerfile .

调试

由于 MCP 服务器通过 stdio 运行，调试起来可能颇具挑战性。为了获得最佳调试体验，我们强烈建议使用MCP Inspector 。

您可以使用以下命令通过npm启动 MCP Inspector：

npx @modelcontextprotocol/inspector uv --directory /path/to/your/mcp-sleep run mcp-sleep

启动后，检查器将显示一个 URL，您可以在浏览器中访问该 URL 以开始调试。

Available Tools

1 tool
sleepC

If you need to wait for a few seconds to continue with the task you are performing .

ParametersJSON Schema
NameRequiredDescriptionDefault
secondsYesseconds it will take me to tell you to continue.

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It mentions waiting behavior but omits key details: whether it blocks execution, if it's synchronous/asynchronous, error handling, or side effects. The phrase 'tell you to continue' hints at notification but is ambiguous. For a tool with no annotation coverage, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's function. It's appropriately sized for a simple tool, with no redundant or verbose phrasing. However, it could be more front-loaded by starting with the core action (e.g., 'Pauses execution for a specified duration').

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (one parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on behavior, return values, or error cases. With no output schema, it should ideally hint at what happens after waiting (e.g., resumes task). It's complete enough for a simple tool but has room for improvement.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the parameter 'seconds' well-documented in the schema (type, range, purpose). The description adds no parameter-specific information beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without compensating value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose as waiting/pausing execution ('wait for a few seconds'), which is clear but somewhat vague. It doesn't specify what resource or system it operates on, and with no sibling tools, differentiation isn't needed. The description avoids tautology by explaining function rather than just restating the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides implied usage context ('to continue with the task you are performing'), suggesting it's for pacing or timing in workflows. However, it lacks explicit guidance on when to use vs. alternatives (though none exist), prerequisites, or specific scenarios. The guidance is functional but minimal.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedsleep
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness1/5

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

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • MCP Wait Timer Server

    199-mcp
    A
    license
    A
    quality
    D
    maintenance
    Provides 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.
    1
    32 npm
    1
    MIT

  • Treehole MCP Server

    jeffkit
    A
    license
    B
    quality
    C
    maintenance
    Provides 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.
    2
    18 npm
    4
    MIT

  • LoopIn MCP Server

    nicholasemccormick
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables 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.
    9 npm
    MIT

  • mcp-wait

    AaLexUser
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides 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.
    11 npm
    MIT