refresh_business_website — Latchbell MCP Tool
refresh_business_website
(refresh business website) is one of 96 tools on the
Latchbell
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call refresh_business_website from your client
- Claude Code Latchbell refresh_business_website run in your project directory
- Claude Desktop Latchbell refresh_business_website ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Latchbell refresh_business_website ~/.cursor/mcp.json
- VS Code Latchbell refresh_business_website .vscode/mcp.json
- Zed Latchbell refresh_business_website ~/.config/zed/settings.json
- Windsurf Latchbell refresh_business_website ~/.codeium/windsurf/mcp_config.json
- Cline Latchbell refresh_business_website ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Latchbell refresh_business_website ~/.gemini/settings.json
- Grok Latchbell refresh_business_website .mcp.json (in your project root)
- ChatGPT Latchbell refresh_business_website Settings → Connectors → Advanced → Developer mode
- Claude.ai Latchbell refresh_business_website Settings → Connectors → Add custom connector
- LangChain Latchbell refresh_business_website pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http latchbell https://latchbell.com/mcp/agentsOther tools on this server
- find_services
- find_businesses
- business_info
- find_times
- book
- request_booking
- booking_status
- my_bookings
- reschedule_booking
- cancel_booking
- check_in
- products
- estimate_order
- request_order
- checkout_order
- catalog
- quote
- contact_business
- search_business_info
- read_business_info
- inquiry_status
- update_conversation_customer
- follow_up_business
- ask_business
- my_inquiries
- register_business
- confirm_business_email
- my_business
- call_brief
- set_customer_notes
- receptionist_readiness
- receptionist_service
- receptionist_checkout
- cancel_receptionist_checkout
- receptionist_top_up
- receptionist_buy_minutes
- receptionist_billing_portal
- receptionist_limits
- customer_payment_onboarding
- receptionist_refresh
- receptionist_call_voice
- phone_numbers
- activate_phone_number
- phone_portability
- prepare_number_port
- place_phone_call
- phone_call
- coach_phone_call
- phone_calls
- pair_phone
- text_phones
- send_text
- service_setup
- update_team
- update_booking_rules
- update_catalog
- update_products
- front_desk
- update_front_desk
- read_website_again
- receptionist
- add_receptionist_source
- edit_receptionist_source
- update_receptionist
- update_business
- my_page
- update_page
- publish_page
- my_website
- upload_site_pages
- upload_site_photo
- remove_site_photo
- publish_website
- site_designer_chat
- approve_own_change
- note_to_owner
- save_inquiry_contact
- log_lead
- follow_ups_due
- update_lead
- flag_bad_lead
- message_customer
- inquiries
- close_inquiry
- updates
- set_hours
- block_time
- unblock_time
- schedule
- add_booking
- confirm_request
- move_booking
- cancel_customer_booking
- mark_booking
- pipeline
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.