check_booking_status — claw.cleaning MCP Tool Read-only
check_booking_status
(check booking status) is one of 3 tools on the
claw.cleaning
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_booking_status from your client
- Claude Code claw.cleaning check_booking_status run in your project directory
- Claude Desktop claw.cleaning check_booking_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor claw.cleaning check_booking_status ~/.cursor/mcp.json
- VS Code claw.cleaning check_booking_status .vscode/mcp.json
- Zed claw.cleaning check_booking_status ~/.config/zed/settings.json
- Windsurf claw.cleaning check_booking_status ~/.codeium/windsurf/mcp_config.json
- Cline claw.cleaning check_booking_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI claw.cleaning check_booking_status ~/.gemini/settings.json
- Grok claw.cleaning check_booking_status .mcp.json (in your project root)
- ChatGPT claw.cleaning check_booking_status Settings → Connectors → Advanced → Developer mode
- Claude.ai claw.cleaning check_booking_status Settings → Connectors → Add custom connector
- LangChain claw.cleaning check_booking_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http claw-cleaning https://claw.cleaning/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.