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-get

Sleep MCP サーバーはmcp-getを使用してインストールできます。

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

前提条件

MCP はまだ非常に新しく、進化を続けています。MCP の基本を理解して実行するには、 MCP ドキュメントに従うことをお勧めします。

必要なもの:

構成

1. Claudeデスクトップを設定する

OSに応じて次のファイルを作成します。

MacOSの場合: ~/Library/Application\ Support/Claude/claude_desktop_config.json

Windows の場合: %APPDATA%/Claude/claude_desktop_config.json

このテンプレートをファイルに貼り付けます

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

オプションで、 <MCP_SLEEP_TIMEOUT>タイムアウト (待機できる最大時間、デフォルトは 60 秒) に置き換えます。

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

2. Claude Desktopを再起動します

SSEモード

あるいは、次のコマンドを実行して、MCP サーバーを SSE モードで実行することもできます。

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に以下を追加します。

ドッカー

{
  "mcpServers": {
    "mcp-sleep": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MCP_SLEEP_TIMEOUT",
        "mcp/sleep"
      ],
      "env": {
        "MCP_SLEEP_TIMEOUT": "<MCP_SLEEP_TIMEOUT>"
      }
    }
  }
}

発達

設定

ローカルで作業している場合は、リポジトリのルートにある.envファイルに 2 つの環境変数を追加します。

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 がインスペクタに表示されます。

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