A
licenseB
qualityD
maintenanceA 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.
1
6
21
ISC
mcp-wait
by lzientek
Allows the agent to pause for a specified duration, useful for waiting for a Slack response before continuing a conversation.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-waitwait 120 seconds for PR approval"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-wait
A minimal MCP server that lets AI agents pause for a specified duration before resuming their workflow. Useful for polling patterns: check a condition, wait, retry.
Use cases
Wait for a PR to be approved before merging
Wait for a Slack response before continuing a conversation
Wait for a file to be created by an external process
Any retry/polling loop where the agent needs to back off
Related MCP server: MCP-Wait
Tool: wait
Parameter | Type | Required | Description |
| number | yes | Seconds to wait (1–600, max 10 min) |
| string | no | Why you're waiting (for logging) |
Returns a confirmation message once the delay has elapsed.
Quick start with npx
No installation needed — just add to your MCP configuration:
{
"mcpServers": {
"mcp-wait": {
"command": "npx",
"args": ["-y", "@lzientek/mcp-wait"]
}
}
}Install globally
npm install -g @lzientek/mcp-waitThen use in your MCP config:
{
"mcpServers": {
"mcp-wait": {
"command": "mcp-wait"
}
}
}Example agent flow
1. Check PR status → not approved
2. Call wait(seconds: 180, reason: "waiting for PR approval")
3. (3 minutes pass)
4. Check PR status again → approved ✓
5. Proceed with mergeLicense
MIT
Available Tools
1 toolwaitA
Wait for a specified duration before returning. Use this to pause between retries when polling for a condition (PR approval, Slack response, file creation, etc.).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | Optional: why you are waiting (for logging clarity) | |
| seconds | Yes | Number of seconds to wait (max 600 = 10 minutes) |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description fully carries the burden. It clearly discloses the action: waits for a duration and then returns. It implies blocking behavior and no side effects, which is complete for a simple non-destructive tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the essential action, and no extraneous words. Every sentence earns its place, delivering clear instruction without verbosity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with two parameters (fully described in schema) and no output schema, the description is complete. It explains what the tool does, when to use it, and implicitly covers behavioral expectations. No additional context is needed.
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%; both parameters ('seconds' and 'reason') have descriptions in the schema. The description does not add any additional meaning or context beyond what the schema provides, so baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Wait for a specified duration before returning.' It uses a specific verb ('wait') and resource ('specified duration'), and the purpose is unmistakable. With no sibling tools, no differentiation is needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly advises when to use the tool: 'Use this to pause between retries when polling for a condition' and provides concrete examples (PR approval, Slack response, file creation). This gives excellent usage context, though alternative tools are not mentioned (not necessary here).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
A4.8/5.0
Disambiguation5/5
With only one tool, there is no possibility of overlap or confusion. The tool's purpose is clearly defined and distinct by default.
Naming Consistency5/5
A single tool named 'wait' follows a simple verb pattern. Consistency is trivially maintained as there is only one tool.
Tool Count5/5
One tool is perfectly appropriate for a utility focused on waiting. The tool earns its place by providing a clear, single function.
Completeness5/5
The server's domain is limited to waiting for a duration. The single tool fully covers this purpose with no missing functionality.
Maintenance
ActivityStale
ResponsivenessSyncing
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Remote MCP server for The Colony — a social network for AI agents (posts, DMs, search, marketplace).
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
Related MCP Servers
- AlicenseBqualityDmaintenanceA simple MCP server that provides waiting functionality to pause until other tasks finish, with progress reporting and support for CLI or HTTP server with SSE.1245MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to pause and request human approval or information via Slack, Telegram, or macOS dialogs before proceeding with actions.15Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA robust, lightweight Model Context Protocol (MCP) server designed to empower your AI Agents with context-awareness, safe execution sandboxes, and dedicated thought logs.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lzientek/mcp-wait'
If you have feedback or need assistance with the MCP directory API, please join our Discord server