GreatWait MCP

GreatWait is a remote MCP server that enables AI agents to schedule, sign, and execute reliable HTTPS callbacks. It supports one-off delays, recurring intervals, and cron-based schedules, providing detailed logs of delivery attempts and retries to ensure agents can trigger external webhooks or reminders without managing infrastructure.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-26Operated by GreatWait

MCP endpoint (Streamable HTTP)

https://api.greatwait.dev/mcp

Vendor documentation

What you can do with it

Schedule a one-time HTTPS call to a webhook after a specific delay
Set up recurring partner data syncs at fixed intervals
Send scheduled reminders to users or guests via HTTP POST
Inspect delivery attempts and logs for failed webhook calls

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http greatwait-mcp https://api.greatwait.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add greatwait-mcp --url https://api.greatwait.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable greatwait-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "greatwait-mcp": {
      "url": "https://api.greatwait.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "greatwait-mcp": {
      "type": "streamableHttp",
      "url": "https://api.greatwait.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start greatwait-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "greatwait-mcp": {
      "type": "http",
      "url": "https://api.greatwait.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http greatwait-mcp https://api.greatwait.dev/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "greatwait-mcp": {
      "url": "https://api.greatwait.dev/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "greatwait-mcp": {
      "serverUrl": "https://api.greatwait.dev/mcp"
    }
  }
}

Ground your agent in cited data

GreatWait MCP gives your agent tools. Koskamo gives it reviewed, cited facts to check its answers against. Add it as a second MCP server; public reads need no API key.

Connect Koskamo Browse datasets

See all 1,274

Do you run GreatWait MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing