get_live_waits — mouseedge skipper MCP Tool Read-only
get_live_waits
(get live waits) is one of 13 tools on the
mouseedge skipper
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_live_waits from your client
- Claude Code mouseedge skipper get_live_waits run in your project directory
- Claude Desktop mouseedge skipper get_live_waits ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mouseedge skipper get_live_waits ~/.cursor/mcp.json
- VS Code mouseedge skipper get_live_waits .vscode/mcp.json
- Zed mouseedge skipper get_live_waits ~/.config/zed/settings.json
- Windsurf mouseedge skipper get_live_waits ~/.codeium/windsurf/mcp_config.json
- Cline mouseedge skipper get_live_waits ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mouseedge skipper get_live_waits ~/.gemini/settings.json
- Grok mouseedge skipper get_live_waits .mcp.json (in your project root)
- ChatGPT mouseedge skipper get_live_waits Settings → Connectors → Advanced → Developer mode
- Claude.ai mouseedge skipper get_live_waits Settings → Connectors → Add custom connector
- LangChain mouseedge skipper get_live_waits pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mouseedge-skipper https://mouseedge.com/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.