Skip to main content
Glama
199-mcp

MCP Wait Timer Server

by 199-mcp

MCP Wait Timer Server

An MCP (Model Context Protocol) server providing a simple wait tool.

Watch the demo video: https://www.youtube.com/watch?v=TaF_j9wrWVw

Overview

This server exposes a single tool, wait, designed to introduce deliberate pauses into workflows executed by MCP clients (e.g., Cline, Claude Desktop, Cursor).

Related MCP server: mcp-sleep

Problem Solved

MCP clients and the AI models driving them often operate sequentially. After executing a command or action (like a web request, file operation, or API call), the model might proceed to the next step immediately. However, some actions require additional time to fully complete their effects (e.g., background processes finishing, web pages fully rendering after JavaScript execution, file system propagation).

Since the model cannot always reliably detect when these asynchronous effects are complete, it might proceed prematurely, leading to errors or incorrect assumptions in subsequent steps.

Solution: The wait Tool

This server provides a wait tool that allows the user or the AI prompt to explicitly instruct the client to pause for a specified duration before continuing. This ensures that time-dependent operations have sufficient time to complete.

Tool: wait

  • Description: Pauses execution for a specified number of seconds.

  • Input Parameter:

    • duration_seconds (number, required): The duration to wait, in seconds. Must be a positive number.

Use Cases

  • Web Automation: Ensure dynamic content loads or scripts finish executing after page navigation or element interaction.

    Example Prompt: "Navigate to example.com, fill the login form, click submit, then wait for 5 seconds and capture a screenshot."
  • Command Line Operations: Allow time for background tasks, file writes, or service startups initiated by a shell command.

    Example Prompt: "Run 'npm run build', wait for 15 seconds, then check if the 'dist/app.js' file exists."
  • API Interaction: Add delays between API calls to handle rate limiting or wait for asynchronous job completion.

  • Workflow Debugging: Insert pauses to observe the state of the system at specific points during a complex task.

Installation & Setup

This server requires Node.js (version 16 or higher).

Step 1: Configure Your MCP Client

Add the following JSON block within the "mcpServers": {} object in your client's configuration file. Choose the file corresponding to your client and operating system:

Configuration Block:

    "wait-timer": {
      "command": "npx",
      "args": ["mcp-wait-timer"],
      "env": {},
      "disabled": false,
      "autoApprove": []
    }

Client Configuration File Locations:

  • Claude Desktop:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%\Claude\claude_desktop_config.json

    • Linux: ~/.config/Claude/claude_desktop_config.json (Path may vary slightly)

  • VS Code Extension (Cline / "Claude Code"):

    • macOS: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

    • Windows: %APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json

    • Linux: ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

  • Cursor:

    • Global: ~/.cursor/mcp.json

    • Project-Specific: Create a file at .cursor/mcp.json within your project folder.

  • Windsurf:

    • ~/.codeium/windsurf/mcp_config.json

  • Other Clients:

    • Consult the specific client's documentation for the location of its MCP configuration file. The JSON structure shown in the "Configuration Block" above should generally work.

Step 2: Restart Client

After adding the configuration block and saving the file, fully restart your MCP client application for the changes to take effect. The first time the client starts the server, npx will automatically download the mcp-wait-timer package if it's not already cached.

Usage Example

Once installed and enabled, you can instruct your MCP client:

"Please wait for 10 seconds before proceeding."

The client's AI model should recognize the intent and call the wait tool with duration_seconds: 10.

Developed By

This tool was developed as part of the initiatives at 199 Longevity, a group focused on extending the frontiers of human health and longevity.

Learn more about our work in biotechnology at 199.bio.

Project contributor: Boris Djordjevic

License

This project is licensed under the MIT License - see the LICENSE file for details.

Available Tools

1 tool
waitA

Waits for a specified duration in seconds.

ParametersJSON Schema
NameRequiredDescriptionDefault
duration_secondsYes

TDQS

A3.7/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 the full burden of behavioral disclosure. It states the action ('waits') but does not explain how the wait is implemented (e.g., blocking vs. non-blocking), potential side effects, or error handling. This leaves gaps in understanding the tool's behavior beyond the basic action.

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 a single, clear sentence that efficiently conveys the tool's function without unnecessary details. It is front-loaded and wastes no words, making it easy to understand at a glance.

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 but lacks depth. It covers the basic action but does not address behavioral aspects like implementation details or error scenarios, which could be important for a wait function in some contexts.

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

Parameters4/5

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

The description adds meaning by specifying that the parameter is for 'duration in seconds,' which clarifies the unit and purpose beyond the schema's description ('The number of seconds to wait'). With 0% schema description coverage, the description compensates well by providing essential context, though it could note the minimum value constraint from the schema.

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 purpose with a specific verb ('waits') and resource ('duration in seconds'), making it immediately understandable. It distinguishes itself by focusing solely on time-based waiting functionality, which is straightforward given there are no sibling tools to differentiate from.

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 implies usage for delaying execution by a specified time, but provides no explicit guidance on when to use this tool versus alternatives or any prerequisites. With no sibling tools, the context is limited, but it lacks details on scenarios where waiting is appropriate or any constraints.

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

TDQS

A3.6/5.0
Disambiguation5/5

With only one tool, there is no possibility for ambiguity or overlap between tools. The tool 'wait' has a single, clear purpose that cannot be confused with any other tool in this set.

Naming Consistency5/5

The naming is trivially consistent as there is only one tool. The tool name 'wait' follows a simple verb pattern, and there are no other tools to create inconsistency or mixed conventions.

Tool Count2/5

A single tool is too few for most server purposes, making the server feel thin and limited in scope. While a timer server might logically have few tools, one tool is borderline minimal and may not cover all expected timer-related operations, such as cancelling or listing waits.

Completeness2/5

The tool set is severely incomplete for a timer server. It only provides a wait function, missing obvious operations like cancelling an active wait, checking wait status, or managing multiple timers, which are common in timer-related domains.

Maintenance

ActivityInactive
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

Related MCP Servers

  • A
    license
    B
    quality
    D
    maintenance
    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.
    1
    6
    21
    ISC
  • A
    license
    B
    quality
    D
    maintenance
    A 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.
    1
    24
    5
    MIT
  • 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.
    15
    MIT

Latest Blog Posts

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/199-mcp/mcp-wait-timer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server