# 360dialog Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## 360dialog

Manage your WhatsApp Business number, message templates and shared inbox from chat

- Record: https://musedirectory.ai/connector/360dialog
- Category: Marketing & Ads
- Developer: 360dialog (https://www.360dialog.com)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 84ms, checked 2026-11-08T16:46:17Z
- Endpoint: https://mcp.360dialog.com/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-08T16:46:17Z)
- Source: Found in the official MCP Registry (com.360dialog/mcp) https://registry.modelcontextprotocol.io/v0/servers?search=com.360dialog%2Fmcp

Connects to your 360dialog WhatsApp Business account. Muse can list channels, create and preview message templates, check number onboarding status, set webhooks, review balance and invoices, and reply in the shared team inbox.

Example request: "Check whether my new WhatsApp number is live and show me my approved message templates."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use 360dialog to help me. It is a free service with an MCP server at https://mcp.360dialog.com/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- list_skills: List the 360Dialog skills available to you. A skill is a curated, up-to-date how-to guide for a 360Dialog process (e.g. drafting a compliant WhatsApp template, diagnosing a channel that stopped sending). Call this tool BEFORE answering any "how do I..." question about 360Dialog p
- get_skill: Get the full guide for one skill returned by 'list_skills', as markdown.
- start_signup: Returns the URL where a user can create a 360Dialog account. Only relevant if the user has not created a 360Dialog account yet.
- search_client_documentation: Search the 360Dialog client documentation at https://docs.360dialog.com/docs. Search across the documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Client Documentation, find specific documen
- get_client_documentation_page: Get a documentation page from the 360Dialog client documentation at https://docs.360dialog.com/docs. Fetch the full markdown content of a specific documentation page from Client Documentation. Use this when you have a page URL and want to read its content. Accepts full URLs (e.g.
- get_balance: Get balance for an account.
- list_channels: Find a channel by passing in an identifier. A channel is a phone number. By calling this tool you retrieve information about the phone number/channel in 360Dialog. Results are paginated; use the 'page' and 'size' arguments to page through results if there are more than fit in a s
- set_display_name: Submit a new display name for this channel (a.k.a. phone number.) Calling this tool will submit a display name request to Meta. Meta takes up to 48 hours to review the submitted display name. The display name may be rejected if it does not comply with display name guidelines. The
- get_channel_profile: Get a channel's (a.k.a. phone number) WhatsApp profile.
- update_channel_profile: Update the WhatsApp profile for this channel (a.k.a. phone number.) The user may be prompted by 360Dialog for an OTP code delivered to their email address. Make them aware of the OTP requirement.
- get_invoices: Get invoices for an account.
- wait_for_onboarding_step: Wait for a server-side onboarding step to finish, then report back. Embedded Signup and payment setup finish in the person's browser. This tool polls the hub every 5 seconds for up to 45 seconds and returns one of: - "done": The step finished. - "pending": Still not finished. Cal
- get_company_details: Get the user's company's details from 360Dialog.
- update_company_details: Set the user's company's details on 360Dialog. This change does not affect Meta; only records on 360Dialog are affected by the update. Before calling this tool, make sure to: 1. Check if the `get_company_details` tool returns the correct company information already. 2. Check with
- check_number_eligibility: Check whether a phone number can be onboarded for this client before handing over the onboarding link. This tool only checks 360Dialog's own database and this client's channel quota. It does not ask WhatsApp/Meta anything, so a number already active on WhatsApp elsewhere (includi
- start_number_onboarding: Get the link that lets the user connect a WhatsApp phone number in 360Dialog, plus what to tell them beforehand. This hands over 360Dialog's own onboarding page. The user clicks through Embedded Signup themselves; this tool cannot do it for them. The user must be signed in to 360
- start_payment_setup: Get the link that lets the user add their credit card to their account. If this client was created through assistant-led onboarding and still has no company name or country on file, the payment page is kept behind a company details form instead. In that case this tool does not re
- get_onboarding_status: Get a phone number's status on whether a number is live, what type of messages it can send today, and suggestions for what's next. A live number can send free-form replies inside the 24-hour customer service window immediately (meaning if someone messages the number, the user can
- request_otp: Request an OTP code. Sometimes OTP is needed to complete invoking a tool. When tool invocation fails due to OTP reasons, you will be notified in the tool response, and be asked to rqeuest an OTP code. Only call after a tool call fails due to OTP.
- verify_otp: Verify the 6-digit OTP code from the user. Doing so will automatically replay the blocked tool call that required verification.
- list_templates: List templates for a WABA (WhatsApp Business Account). If you do not have a waba_account_id ending in 'WA' (case-insensitive), run the 'list_channels' tool first.
- show_template_preview: Show a preview of a given template to the user.
- get_template_json_example: Sending messaging templates in WhatsApp API / 360Dialog API requires a JSON body in the API request. The API request can be hard to form, as the body must declare in JSON what each parameter in the JSON should be filled as. This tool creates a valid example JSON body that the use
- create_template: Use this tool to create a WhatsApp message template. For this tool's 'template_json' property, pass a JSON matching this shape: { "name": string, "language": string, "category": "MARKETING" | "AUTHENTICATION" | "UTILITY", "components": Component[], } General rules: - name must be
- delete_template: Delete a WhatsApp message template by its internal template ID.
- get_webhook: Get a channel's (a.k.a. phone number's) webhook URL, and check if the optional webhook headers are set. Webhook headers are optional. They can be set using the 'set_webhook' tool, which also sets the webhook URL. When webhook headers are set, 360Dialog will send webhooks to the c
- set_webhook: Set a channel's (a.k.a. phone number's) webhook URL and optionally webhook headers.
- test_webhook: Test if a channel's (a.k.a. phone number's) webhook URL is functional. A total of 32 test cases will be run by sending sample POST requests to the user's webhook URL. During this test, the user may see 32 requests being made to their webhook server. Returns the test's results, sh
- get_self: Get currently logged in user's information in 360Dialog. You will get: - user's name, - user's email address, - partner name, - user's permissions in 360Dialog Hub, - user's roles
- list_users: List users for the selected account, including their roles and creation timestamps.
- sandbox_register_number: Register the user's phone number on the 360Dialog sandbox. Upon registration, the user can send messages to this phone number from the 360Dialog sandbox account on WhatsApp. The user will be given a link to complete registration. When this link is used, they will send a verificat
- sandbox_complete_registration: Complete a phone number's registration. This will get you the API key to use when sending messages from the 360Dialog sandbox phone number to the user's registered phone number.
- sandbox_send_message: Send a message on the 360Dialog sandbox. Messages can only be sent to the user's phone number that was used during sandbox registration. The payload must be a JSON string matching the WhatsApp messages endpoint body. Interactive message example: use this only when there is an act
- sandbox_configure_webhook: Set webhook for the channel on 360Dialog sandbox. Optional.
- sandbox_get_webhook_configuration: Get configured webhook for the channel on 360Dialog sandbox.
- sandbox_list_events: List webhook events received. This will show received messages from the user, and status of messages sent from the sandbox account.
- getchat_send_message: Send a message into an existing conversation, as the business. This is inbox-scoped sending: it posts into an existing conversation with correct threading. Outside the 24-hour customer-care window, WhatsApp only permits template messages — other types are rejected with an explana
- getchat_assign_conversation: Assign or reassign one conversation to an agent and/or a group. Both fields are always set to exactly what you pass: calling with only `user_id` clears any group assignment and vice versa; calling with neither unassigns the conversation entirely.
- getchat_tag_conversation: Add or remove one tag on one conversation.
- getchat_mark_conversation_as_read: Mark one conversation's messages as read by the calling user. Pass `up_to_timestamp` after reviewing a conversation so that messages arriving in the meantime stay unread. The read mark only moves forward: a timestamp older than the caller's current mark changes nothing. Read stat

Screening checks:
- MCP handshake: pass (Answered in 84ms)
- Domain against threat feeds (Cloudflare security DNS): pass (mcp.360dialog.com, www.360dialog.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: warn (create_template: Unusually long tool description; getchat_send_message: Tool text tells the model to take extra steps; getchat_apply_saved_response: Tool text tells the model to take extra steps; mba_send_agent_event: Tool text tells the model to take extra steps)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 5372 days ago)
- AI review of purpose and tool behavior: pass (tool descriptions include workflow instructions aimed at the model; OTP and payment steps handled through user-facing links)