get_booking_bill — Pinsvit MCP Tool Read-only
get_booking_bill
(get booking bill) is one of 32 tools on the
Pinsvit
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_booking_bill from your client
- Claude Code Pinsvit get_booking_bill run in your project directory
- Claude Desktop Pinsvit get_booking_bill ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Pinsvit get_booking_bill ~/.cursor/mcp.json
- VS Code Pinsvit get_booking_bill .vscode/mcp.json
- Zed Pinsvit get_booking_bill ~/.config/zed/settings.json
- Windsurf Pinsvit get_booking_bill ~/.codeium/windsurf/mcp_config.json
- Cline Pinsvit get_booking_bill ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Pinsvit get_booking_bill ~/.gemini/settings.json
- Grok Pinsvit get_booking_bill .mcp.json (in your project root)
- ChatGPT Pinsvit get_booking_bill Settings → Connectors → Advanced → Developer mode
- Claude.ai Pinsvit get_booking_bill Settings → Connectors → Add custom connector
- LangChain Pinsvit get_booking_bill pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http api https://pinsvit.com/api/v1/mcp
Other tools on this server
- accept_booking
- add_booking_note
- cancel_booking
- create_booking
- create_comment
- create_event
- create_post
- decline_booking
- delete_comment
- delete_post
- find_booking_times
- find_place_customers
- get_booking
- get_comments
- get_current_country_code
- get_current_user_details
- get_month_availability
- get_place
- get_place_services
- get_post
- get_publishing_media_keys
- list_my_bookings
- list_my_places
- list_place_booking_requests
- list_place_bookings
- mark_no_show
- ping
- record_bill_payment
- search_events_near
- search_places
- search_posts_near
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.