draft_bot_flow — LetsBot MCP Tool
draft_bot_flow
(draft bot flow) is one of 95 tools on the
LetsBot
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call draft_bot_flow from your client
- Claude Code LetsBot draft_bot_flow run in your project directory
- Claude Desktop LetsBot draft_bot_flow ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor LetsBot draft_bot_flow ~/.cursor/mcp.json
- VS Code LetsBot draft_bot_flow .vscode/mcp.json
- Zed LetsBot draft_bot_flow ~/.config/zed/settings.json
- Windsurf LetsBot draft_bot_flow ~/.codeium/windsurf/mcp_config.json
- Cline LetsBot draft_bot_flow ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI LetsBot draft_bot_flow ~/.gemini/settings.json
- Grok LetsBot draft_bot_flow .mcp.json (in your project root)
- ChatGPT LetsBot draft_bot_flow Settings → Connectors → Advanced → Developer mode
- Claude.ai LetsBot draft_bot_flow Settings → Connectors → Add custom connector
- LangChain LetsBot draft_bot_flow pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://letsbot.net/mcpOther tools on this server
- send_text_message
- send_image
- send_video
- send_audio
- send_file
- send_location
- send_contact_card
- send_template
- send_buttons
- send_list
- send_carousel
- reply_to_message
- send_reaction
- forward_message
- upload_file
- get_contacts
- get_contact
- create_contact
- update_contact
- get_my_chats
- get_conversations_awaiting_reply
- pin_contact
- archive_contact
- block_contact
- delete_contact
- assign_label
- assign_moderator
- reassign_conversations
- get_assignment_rules
- update_assignment_rules
- add_note
- get_account_overview
- get_owner_briefing
- get_report
- list_whatsapp_templates
- create_whatsapp_template
- list_scheduled_activity
- cancel_scheduled_activity
- get_messages
- get_message_status
- search_messages
- mark_as_read
- get_groups
- get_group_messages
- send_group_message
- send_group_file
- get_labels
- create_label
- get_label_contacts
- get_moderators
- get_quick_replies
- create_quick_reply
- update_quick_reply
- delete_quick_reply
- update_label
- delete_label
- ai_suggest_reply
- ai_summarize_conversation
- ai_analyze_contact
- ai_improve_message
- ai_translate_message
- ai_sentiment_analysis
- ai_dashboard_summary
- get_order_status
- search_products
- get_abandoned_carts
- list_store_automations
- set_store_automation_active
- create_campaign
- get_campaigns
- get_campaign_status
- cancel_campaign
- resume_campaign
- resend_campaign
- get_bot_status
- toggle_bot
- get_bot_conversations
- create_simple_conversation
- create_interactive_conversation
- update_bot_conversation
- get_bot_settings
- update_bot_settings
- set_bot_conversation_active
- duplicate_bot_conversation
- delete_bot_conversation
- get_ad_lead_settings
- update_ad_lead_settings
- get_notification_template
- update_notification_template
- save_cart_reminder
- get_ai_assistant_settings
- update_ai_assistant_settings
- diagnose_messaging
- get_store_setup_checklist
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.