list_booking_services — MONO Social MCP Tool Read-only
list_booking_services
(list booking services) is one of 26 tools on the
MONO Social
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_booking_services from your client
- Claude Code MONO Social list_booking_services run in your project directory
- Claude Desktop MONO Social list_booking_services ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MONO Social list_booking_services ~/.cursor/mcp.json
- VS Code MONO Social list_booking_services .vscode/mcp.json
- Zed MONO Social list_booking_services ~/.config/zed/settings.json
- Windsurf MONO Social list_booking_services ~/.codeium/windsurf/mcp_config.json
- Cline MONO Social list_booking_services ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MONO Social list_booking_services ~/.gemini/settings.json
- Grok MONO Social list_booking_services .mcp.json (in your project root)
- ChatGPT MONO Social list_booking_services Settings → Connectors → Advanced → Developer mode
- Claude.ai MONO Social list_booking_services Settings → Connectors → Add custom connector
- LangChain MONO Social list_booking_services pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mono-juno-ventures https://mono.juno.ventures/mcp
Other tools on this server
- get_site_info
- list_categories
- search_places
- get_place
- list_events
- list_guides
- get_availability
- create_booking
- reserve_event_tickets
- request_reservation
- rsvp_event
- get_event_tickets
- list_products
- create_checkout
- get_restaurant_menus
- search_dishes
- list_pricing_plans
- get_reviews
- list_blog_posts
- list_faqs
- list_forms
- submit_form
- get_loyalty_info
- list_offers
- list_profiles
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.