start_booking_payment — TaskMan of London MCP Tool Mutating
start_booking_payment
(start booking payment) is one of 20 tools on the
TaskMan of London
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call start_booking_payment from your client
- Claude Code TaskMan of London start_booking_payment run in your project directory
- Claude Desktop TaskMan of London start_booking_payment ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TaskMan of London start_booking_payment ~/.cursor/mcp.json
- VS Code TaskMan of London start_booking_payment .vscode/mcp.json
- Zed TaskMan of London start_booking_payment ~/.config/zed/settings.json
- Windsurf TaskMan of London start_booking_payment ~/.codeium/windsurf/mcp_config.json
- Cline TaskMan of London start_booking_payment ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TaskMan of London start_booking_payment ~/.gemini/settings.json
- Grok TaskMan of London start_booking_payment .mcp.json (in your project root)
- ChatGPT TaskMan of London start_booking_payment Settings → Connectors → Advanced → Developer mode
- Claude.ai TaskMan of London start_booking_payment Settings → Connectors → Add custom connector
- LangChain TaskMan of London start_booking_payment pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http home-services https://taskman.london/mcpOther tools on this server
- find_services
- check_service_area
- get_quote_estimate
- check_availability
- match_providers
- create_booking_request
- get_booking_status
- start_trusted_phone_session
- start_customer_verification
- verify_customer_otp
- verify_magic_link_token
- get_customer_profile
- list_customer_addresses
- list_service_types
- get_customer_availability
- get_booking_payment_status
- create_customer_booking
- update_contact_note
- tag_contact
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.