Sleep Mcp Server

Created By
erichung906010 months ago
A lightweight MCP server providing a sleep tool for LLMs to wait for specified durations. Perfect for API response delays and controlled timing in AI workflows.
Overview

what is Sleep MCP Server?

Sleep MCP Server is a lightweight MCP server that provides a sleep tool for LLMs (Large Language Models) to wait for specified durations, making it ideal for managing API response delays and controlling timing in AI workflows.

how to use Sleep MCP Server?

To use Sleep MCP Server, configure it in your MCP client settings by adding the sleep command, and then you can call the sleep function with the desired number of seconds to wait.

key features of Sleep MCP Server?

  • Simple sleep functionality for LLMs
  • Configurable in MCP client settings
  • Supports waiting for specified durations to manage timing in workflows

use cases of Sleep MCP Server?

  1. Introducing delays in API calls to avoid rate limits.
  2. Waiting for new data to become available before processing.
  3. Synchronizing tasks in AI workflows that require timed execution.

FAQ from Sleep MCP Server?

  • What is the purpose of the Sleep MCP Server?

It allows LLMs to pause execution for a specified duration, which is useful for managing timing in various workflows.

  • How do I install Sleep MCP Server?

You can install it by cloning the repository and running the installation commands provided in the documentation.

  • Can I contribute to the Sleep MCP Server?

Yes! Contributions are welcome, and you can submit a Pull Request on GitHub.

Server Config

{
  "mcpServers": {
    "sleep": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "sleep-mcp"
      ]
    }
  }
}
Project Info
Hosted
Created At
10 months ago
Updated At
10 months ago
Author Name
erichung9060
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago