Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

360dialog

REMOTE · MCP.360DIALOG.COM

Manage WhatsApp Business accounts on 360Dialog: channels, templates, sandbox, inbox, and more.

+1 this week 78 Trust /100

Last scanned (22 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Communication

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security97
Transport & Reachability100
Schema Quality & AI Usability44
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 20649 tokens (~141/item across 146 items; 138 tools + 8 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management29
  • Stability check failed: schema churn in the 13 days we've observed: 17 tool removals, 0 breaking changes, 0 auth/transport breaks, 39 additions. See how to fix → Fail
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 97% of tool parameters carry a description.Partial
  • Structured output schemas are declared (48% of tools); any adoption earns full credit.Pass
Tool Safety96
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 18 of 21 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "mba_list_eval_cases" implies "eval" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 140 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Server version: 2.2.2 → 2.4.0 functional
  • 20 Nov 26 +1
    • Server version: 2.2.1 → 2.2.2 functional
  • 19 Nov 26 0
    • Server version: 2.0.4 → 2.2.1 functional
    • New tool “mba_get_commerce_settings” functional
    • New tool “mba_list_catalog_products” functional
    • New tool “mba_list_product_catalogs” functional
  • 18 Nov 26 0
    • Server version: 2.0.3 → 2.0.4 functional
  • 17 Nov 26 +1
    • Server version: 2.0.1 → 2.0.3 functional
  • 16 Nov 26 −1
    • Stability: 0.23 → fail ▼ security
    • Tool “get_balance” was removed ▼ security
    • Tool “get_invoices” was removed ▼ security
    • Tool “getchat_apply_saved_response” was removed ▼ security
    • Tool “getchat_assign_conversation” was removed ▼ security
    • Tool “getchat_get_conversation” was removed ▼ security
    • Tool “getchat_list_agents” was removed ▼ security
    • Tool “getchat_list_conversations” was removed ▼ security
    • Tool “getchat_list_groups” was removed ▼ security
    • Tool “getchat_list_inboxes” was removed ▼ security
    • Tool “getchat_list_saved_responses” was removed ▼ security
    • Tool “getchat_list_tags” was removed ▼ security
    • Tool “getchat_mark_conversation_as_read” was removed ▼ security
    • Tool “getchat_search_conversations” was removed ▼ security
    • Tool “getchat_send_message” was removed ▼ security
    • Tool “getchat_tag_conversation” was removed ▼ security
    • Tool “start_payment_setup” was removed ▼ security
    • Tool “test_webhook” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “block_users”, which the server declares destructive security
    • New tool “change_user_role”, which the server declares destructive security
    • New tool “create_partner_change_request”, which the server declares destructive security
    • New tool “enable_local_storage”, which the server declares destructive security
    • New tool “inbox_apply_saved_response”, which the server declares destructive security
    • New tool “inbox_assign_conversation”, which the server declares destructive security
    • New tool “inbox_mark_conversation_as_read”, which the server declares destructive security
    • New tool “inbox_send_message”, which the server declares destructive security
    • New tool “inbox_tag_conversation”, which the server declares destructive security
    • New tool “invite_user”, which the server declares destructive security
    • New tool “send_test_webhook_event”, which the server declares destructive security
    • New tool “set_business_username”, which the server declares destructive security
    • New tool “subscribe_platform_status_updates”, which the server declares destructive security
    • New tool “unblock_users”, which the server declares destructive security
    • New tool “unsubscribe_platform_status_updates”, which the server declares destructive security
    • New tool “update_commerce_settings”, which the server declares destructive security
    • Tool “get_channel_profile” rewrote its description, which is the text the model reads security
    • Tool “get_onboarding_status” rewrote its description, which is the text the model reads security
    • Tool “list_channels” rewrote its description, which is the text the model reads security
    • Tool “list_users” rewrote its description, which is the text the model reads security
    • Tool “request_otp” rewrote its description, which is the text the model reads security
    • Tool “verify_otp” rewrote its description, which is the text the model reads security
    • Schema quality: 17564 → 20075 ▼ functional
    • Tool coverage: 41% → 49% ▲ functional
    • New resource “show_channel_list” functional
    • New resource “show_channel_profile” functional
    • New resource “show_confirm_action” functional
    • New resource “show_messaging_analytics” functional
    • New resource “show_otp_entry” functional
    • New resource “show_secret_reveal” functional
    • Server version: 3.4.11 → 2.0.1 functional
    • New tool “get_business_username_suggestions” functional
    • New tool “get_channel_details” functional
    • New tool “get_client_details” functional
    • New tool “get_commerce_settings” functional
    • New tool “get_currency_migration_status” functional
    • New tool “get_messaging_analytics” functional
    • New tool “get_platform_status” functional
    • New tool “get_voice_analytics” functional
    • New tool “inbox_get_conversation” functional
    • New tool “inbox_list_agents” functional
    • New tool “inbox_list_conversations” functional
    • New tool “inbox_list_groups” functional
    • New tool “inbox_list_inboxes” functional
    • New tool “inbox_list_saved_responses” functional
    • New tool “inbox_list_tags” functional
    • New tool “inbox_search_conversations” functional
    • New tool “list_blocked_users” functional
    • New tool “list_partner_change_requests” functional
    • New tool “list_platform_status_subscriptions” functional
    • New tool “preview_partner_change_request” functional
    • “list_channels” reworded the description of “size” cosmetic
  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.360dialog.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.360dialog.com CN=YR1,O=Let's Encrypt,C=US 30 Oct 2026 28 Jan 2027 RSA 2048 SHA256-RSA 625dfd90aff22b3a8fdd03001d7f7d47d3f
SANs: *.360dialog.com, 360dialog.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.360dialog.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
360dialog.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer error="invalid_token", resource_metadata="https://mcp.360dialog.com/.well-known/oauth-protected-resource/mcp"

Bearer error="invalid_token", resource_metadata="https://mcp.360dialog.com/.well-known/oauth-protected-resource/mcp"
Header Value
strict-transport-security max-age=31536000; includeSubDomains

Protected resource metadata

Document https://mcp.360dialog.com/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://mcp.360dialog.com/mcp
Authorisation server https://mcp.360dialog.com/

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.360dialog.com/mcp Verified 200
http (plaintext) http://mcp.360dialog.com/mcp HTTPS enforced 308 https://mcp.360dialog.com/mcp
MCP tools · 138 exposed · ~20,275 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
mba_start_eval_run ~153

Submit an evaluation job that simulates the listed cases against the agent, evaluates the conversations and optionally produces insights. Returns {job_id, status: QUEUED} - the work is asynchronous, so poll mba_get_eval_results with the job_id. Known limitation: eval_case_ids is read from the QUERY STRING, not the request body - pass it as the comma-separated argument here and this service puts it in the right place; the body is a separate object that accepts nothing else.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
eval_case_idsstringyesComma-separated eval case ids from list_eval_cases.

No output schema declared.

No examples provided.

mba_test_agent ~152

Send a test message through the full agent pipeline and read its reply, without needing a real consumer number. Pass conversation_id from a previous reply to continue the same test conversation. Known limitation: while ai_audience is ALLOWLISTED_ONLY this returns agent_response: "" with no_response_reason: "ELIGIBILITY_CHECK_FAILED", no matter which consumer number is involved - check mba_get_agent_settings before concluding the agent is broken.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
conversation_idstring–Optional - continue an existing test conversation.
user_msgstringyesThe message to send to the agent.

No output schema declared.

No examples provided.

mba_update_agent_settings ~222

Replace the agent's settings and return the updated entry. Known limitation: this is a FULL REPLACEMENT, not a patch - every field you omit is reset, so read the current settings with mba_get_agent_settings first and send them back with your change applied. Note also that setting rollout.enabled to false stops the AI responding on all threads; re-enabling it makes the AI respond to new threads only, not to threads that were already open.

NameTypeReqDescription
agent_idstring–Optional - restrict the update to one agent.
ai_audiencestring–ALLOWLISTED_ONLY restricts the agent to the numbers on the allowlist.
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
followupobject–Following up with an inactive user.
handoffobject–Handing the conversation to a human agent.
rolloutobject–Whether the agent responds at all. Disabling it stops the AI answering on every thread.

No output schema declared.

No examples provided.

mba_update_agent_skill ~137

Replace one agent skill by its id. This replaces the skill rather than patching it, so send the title, description and skill text you want it to end up with.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
descriptionstring–What the skill is for (max 1024 characters).
skillstring–The instruction text the agent follows (max 20000 characters).
skill_idstringyesAgent skill id.
titlestring–Short name for the skill (max 64 characters).

No output schema declared.

No examples provided.

mba_update_business_info ~243

Replace the agent's business information and return the stored object. Known limitation: this is a FULL REPLACEMENT - fields you omit are cleared, so read mba_get_business_info first and send the existing values back with your change applied. Known limitation: business info is a CLOSED six-field schema - business_description, contact_info, delivery_and_shipping, payment_method, purchase_info, return_policy. Any other key is rejected. Knowledge that does not fit one of these six fields belongs in an FAQ (mba_create_faq), an agent skill (mba_create_agent_skill), a crawled website (mba_create_website) or an uploaded file (mba_upload_file) - not here.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
business_descriptionstring–What the business does.
contact_infoobject–Contact and location details.
delivery_and_shippingstring–Delivery and shipping terms.
payment_methodstring–Accepted payment methods.
purchase_infostring–How customers buy.
return_policystring–Returns and refunds.

No output schema declared.

No examples provided.

mba_update_connector ~240

Replace one connector by its id. This replaces the connector rather than patching it, so send the full definition you want it to end up with - read mba_get_connector first.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
auth_configobject–Credentials matching auth_type: `api_key` when auth_type is API_KEY, `oauth2_client_credentials` when it is OAUTH2_CLIENT_CREDENTIALS. Credentials can also be set later with upsert_connector_api_key…
auth_typestringyesHow the connected system authenticates.
base_urlstringyesBase URL every tool on this connector calls.
connector_idstringyesConnector id.
descriptionstringyesWhat the connected system does.
namestringyesName of the connector.
requires_certificateboolean–True when the system needs mTLS; upload the certificate with upsert_connector_certificate.
user_auth_injection_configobject–Optional configuration for injecting a per-user token into tool requests.

No output schema declared.

No examples provided.

mba_update_connector_tool ~275

Replace one connector tool definition by its id. This replaces the definition rather than patching it, so send the whole request_definition you want it to end up with - read mba_get_connector_tool first. Known limitation: path_parameters, query_parameters and headers are NAME-TO-SCHEMA OBJECTS, not arrays - write {"order_id": {"type": "string"}}, never [{"name": "order_id", ...}]. And every {brace} token in `path` must have a matching key in path_parameters, or the definition is rejected.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
connector_idstringyesConnector id.
descriptionstringyesWhat the action does - the agent uses this to decide when to call it.
namestringyesName the agent sees for this action.
request_definitionobjectyesThe outbound HTTP request this tool makes, relative to the connector's base_url.
tool_idstringyesConnector tool id.
user_auth_action_configobject–Optional login/refresh response extraction config, for user-auth actions.
user_auth_requiredbooleanyesTrue when the call needs a per-user token rather than the connector's own credentials.

No output schema declared.

No examples provided.

mba_update_faq ~111

Replace one FAQ entry by its id. Both question and answer are required: this replaces the entry rather than patching it, so send the fields you want the entry to end up with.

NameTypeReqDescription
answerstringyes–
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
faq_idstringyesFAQ entry id.
metadataobject–Optional free-form metadata.
questionstringyes–

No output schema declared.

No examples provided.

mba_update_ui_skill ~249

Change the title, the status or the instruction of one UI skill by its id. This is a partial update: a field you omit keeps its stored value. Use it to enable or disable a component without deleting it. A UI skill is NOT an agent skill (mba_list_agent_skills): an agent skill is instruction text that shapes what the agent says, a UI skill lets the agent send one kind of rich WhatsApp component and tells it when to send that component. Known limitation: component_type and flow_id cannot be changed - delete the UI skill and create a new one instead. A flow UI skill cannot be enabled until its flow is published.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
instructionstring–Tells the agent when to send this component, e.g. 'Send this when the customer asks to browse the catalog'.
instruction_idstringyesUI skill id.
statusstring–Whether the agent may send this component. Only an enabled UI skill is available to the agent.
titlestring–Human-readable name for the UI skill.

No output schema declared.

No examples provided.

mba_update_website ~71

Replace the URL of one website crawl entry. Changing the URL restarts crawling.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
urlstringyes–
website_idstringyesWebsite entry id.

No output schema declared.

No examples provided.

mba_upload_file ~281

Upload a file into the agent's knowledge base. Multipart uploads cannot travel over MCP, so pass the file EITHER as `url` (a publicly reachable https URL this service downloads) OR as `content_base64` (the file's bytes, base64-encoded) - exactly one of the two, always with `file_name`. This service performs the multipart upload to Meta for you and returns the created {id, file_name}. Known limitations: Meta caps a file at 100 MB and accepts PDF, DOC, DOCX, PNG, JPG and JPEG (CSV and XLSX where enabled). Base64 content is additionally capped by this endpoint's request size limit, so prefer `url` for anything larger than a few megabytes. A `url` must be https and must resolve to a public address - private, loopback and link-local addresses are refused.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
content_base64string–The file's bytes, base64-encoded. Use `url` instead for large files.
file_namestringyesName to store the file under, including its extension, e.g. 'returns-policy.pdf'.
urlstring–Publicly reachable https URL to download the file from.

No output schema declared.

No examples provided.

mba_upsert_connector_api_key ~123

Set or rotate the API key credentials for a connector. This is an upsert: if credentials already exist they are REPLACED and the connection is re-established. It cannot be used to remove credentials - the payload is required.

NameTypeReqDescription
api_key_configobjectyesWhere the API key is injected. Supply at least one of headers, query_params, body_params.
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
connector_idstringyesConnector id.

No output schema declared.

No examples provided.

mba_upsert_connector_certificate ~162

Upload or rotate the mTLS client certificate for a connector. This is an upsert: if credentials already exist they are REPLACED and the connection is re-established. It cannot be used to remove credentials - the payload is required. Certificates and keys are PEM-encoded; the private key is never returned by any read tool.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
ca_certificatestring–Optional PEM-encoded CA certificate.
client_certificatestringyesPEM-encoded client certificate.
client_keystringyesPEM-encoded private key (PKCS8, RSA or EC).
connector_idstringyesConnector id.

No output schema declared.

No examples provided.

mba_upsert_connector_oauth ~114

Set or rotate the OAuth 2.0 client credentials for a connector. This is an upsert: if credentials already exist they are REPLACED and the connection is re-established. It cannot be used to remove credentials - the payload is required.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
connector_idstringyesConnector id.
oauth_configobjectyesOAuth 2.0 client credentials.

No output schema declared.

No examples provided.

preview_partner_change_request ~241

Check whether numbers can move to a new partner, without creating a request. Runs the same pre-flight checks as 'create_partner_change_request' and reports every issue that would block the move (for example a number that cannot move, a missing company detail, or a request that is already in progress). Nothing is created or changed. Show the result to the user, then, if it is clear, call 'create_partner_change_request' with the same arguments.

NameTypeReqDescription
channel_bundles––Optional. Which payment plan of the new partner each number moves onto. Only needed when the new partner bills its clients.
channel_idsarrayyesIDs of the numbers (channels) to move. Use 'list_channels' to find them. All numbers of a WABA have to move together.
target_client_id––Optional. ID of an existing client at the new partner to move the numbers into. Only for a partial move (not all numbers of the client). Needs to end with 'CL'.
target_partner_idstringyesID of the partner the numbers should move to. Needs to end with 'PA'.
NameTypeReqDescription
actions_requiredarrayyes–
messagestringyes–
readybooleanyes–

No examples provided.

request_otp ~92

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. In clients that show apps, the user enters the code in a card shown with the result, and the result says so.

Input schema present but exposes no named parameters.

NameTypeReqDescription
expires_at–––
messagestringyes–
pending_tool–––
pending_tool_title–––
requestedbooleanyes–

No examples provided.

sandbox_complete_registration ~43

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
api_keystringyes–
mdnstringyes–
messages_leftintegeryes–

No examples provided.

sandbox_configure_webhook ~51

Set webhook for the channel on 360Dialog sandbox. Optional.

NameTypeReqDescription
api_keystringyesSandbox API key
urlobjectyesWebhook to set for this channel on sandbox
NameTypeReqDescription
headers–––
url–––

No examples provided.

sandbox_get_webhook_configuration ~34

Get configured webhook for the channel on 360Dialog sandbox.

NameTypeReqDescription
api_keystringyesSandbox API key
NameTypeReqDescription
headers–––
url–––

No examples provided.

sandbox_list_events ~53

List webhook events received. This will show received messages from the user, and status of messages sent from the sandbox account.

NameTypeReqDescription
pageinteger–Page number. Starts from 1, defaults to 1.
NameTypeReqDescription
itemsarrayyes–
pageintegeryes–
pagesintegeryes–
sizeintegeryes–
totalintegeryes–

No examples provided.

sandbox_register_number ~99

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 verification code to 360Dialog sandbox phone number on WhatsApp. They can click the link, or alternatively scan the QR code.

NameTypeReqDescription
phone_numberstringyes–
NameTypeReqDescription
message_to_sendstringyes–
quick_linkstringyes–
sandbox_numberstringyes–

No examples provided.

sandbox_send_message ~348

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 active conversation window, which lasts 24 hours since the customer's last message. { "messaging_product": "whatsapp", "to": "{{recipient_phone_number}}", "type": "text", "text": { "body": "{{message_body}}" } } Template message example: use this when there is no active conversation window, or when sending an approved template message. You can only send the 'marketing_message' template. { "messaging_product": "whatsapp", "to": "{{recipient_phone_number}}", "type": "template", "template": { "name": "marketing_message", "language": { "policy": "deterministic", "code": "en" }, "components": [ { "type": "header", "parameters": [ { "type": "image", "image": { "link": "https://placehold.co/600x315/34D399/FFFFFF/png?text=Summer+Sale!" } } ] } ] } }

NameTypeReqDescription
api_keystringyesSandbox API key
payloadstringyesJSON body of the WhatsApp message to send. Use a text payload only inside an active 24-hour customer service window; use a template payload to start or continue conversations outside that window.
NameTypeReqDescription
contactsarray––
messagesarray––
messaging_productstring––

No examples provided.

search_client_documentation ~94

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 documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

send_test_webhook_event ~151

Send sample events to a channel's (a.k.a. phone number's) or a WABA's webhook, so the user can check that the webhook receives them and answers with a 2xx code. Pass exactly one of 'channel_id' or 'waba_account_id'. The user may see several sample requests arrive at their webhook server. Returns which sample events passed and which failed.

NameTypeReqDescription
channel_id––Channel ID, ending in 'CH', to test that channel's webhook. Leave blank when testing a WABA.
waba_account_id––WABA ID, ending in 'WA', to test the WABA's webhook. Leave blank when testing a channel.
NameTypeReqDescription
failed_countinteger––
messagestringyes–
passed_countinteger––
resultsarray––
sentbooleanyes–
targetstringyes–
target_idstringyes–

No examples provided.

set_business_username ~136

Claim or change the WhatsApp business username of a channel. This changes what WhatsApp users see for the business, because the username can be shown instead of the phone number. Meta may reject the username, in which case an error is returned.

NameTypeReqDescription
channel_idstringyesNeeds to end with 'CH'.
force_transferboolean–Set to true only if the username is currently on another number of the same business portfolio and should move to this one. Defaults to false.
usernamestringyesThe username to claim for this number. Use 'get_business_username_suggestions' to see usernames reserved for it.
NameTypeReqDescription
channel_idstringyes–
status–––
usernamestringyes–

No examples provided.

set_display_name ~137

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 user will receive an email when their display name review is complete. When this tool is called, the user may be prompted by 360Dialog for an OTP code delivered to their email address.

NameTypeReqDescription
channel_idstringyesNeeds to end with 'CH'.
new_display_namestringyesNew requested display name for this phone number.
NameTypeReqDescription
channel_idstringyes–
new_display_namestringyes–
submittedbooleanyes–

No examples provided.

set_webhook ~51

Set a channel's (a.k.a. phone number's) webhook URL and optionally webhook headers.

NameTypeReqDescription
channel_idstringyesNeeds to end with 'CH'.
webhook_settingobjectyes–
NameTypeReqDescription
configuredbooleanyes–
message–––
webhook–––

No examples provided.

show_template_preview ~62

Show a preview of a given template to the user.

NameTypeReqDescription
template_idstringyesNeeds to end with 'WT'. Use 'list_templates' to find a template's ID.
waba_account_idstringyesNeeds to end with 'WA'.
NameTypeReqDescription
templatestringyes–

No examples provided.

start_number_onboarding ~150

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 360Dialog Hub already, or the link sends them to login first and loses the destination. Tell them to make sure they're signed in first. The link given by this tool may not work if the user's 360Dialog client account is under a partner-paid channel. Make them aware of this. Returns the client's current channel IDs for future reference on recognizing which phone number was newly added.

Input schema present but exposes no named parameters.

NameTypeReqDescription
current_channel_idsarray––
onboarding_urlstringyes–
what_meta_will_askarrayyes–

No examples provided.

start_signup ~38

Returns the URL where a user can create a 360Dialog account. Only relevant if the user has not created a 360Dialog account yet.

Input schema present but exposes no named parameters.

NameTypeReqDescription
next_stepstringyes–
signup_urlstringyes–

No examples provided.

subscribe_platform_status_updates ~21

Subscribe the user to 360Dialog status update emails.

Input schema present but exposes no named parameters.

NameTypeReqDescription
email–––
message–––
subscribedbooleanyes–
subscriber_id–––

No examples provided.

unblock_users ~176

Unblock WhatsApp users so they can message a channel again. Identify each user by phone number or by BSUID; pass at least one of 'phone_numbers' and 'user_ids'. For a user that 'list_blocked_users' shows without a phone number, pass the BSUID in 'user_ids'. The result lists which users were unblocked and which failed with the reason.

NameTypeReqDescription
channel_idstringyesNeeds to end with 'CH'.
phone_numbers––Phone numbers of the WhatsApp users to unblock, in international format without '+' or spaces, for example ['49100100200'].
user_ids––Business-scoped user IDs (BSUIDs) of the WhatsApp users to unblock, for users whose phone number isn't known. 'list_blocked_users' shows each blocked user's BSUID.
NameTypeReqDescription
channel_idstringyes–
failedarrayyes–
succeededarrayyes–

No examples provided.

unsubscribe_platform_status_updates ~43

Stop 360Dialog status update emails for the user.

NameTypeReqDescription
subscriber_idstringyesUse 'list_platform_status_subscriptions' to find a subscription's ID.
NameTypeReqDescription
message–––
subscriber_idstringyes–
unsubscribedbooleanyes–

No examples provided.

update_channel_profile ~169

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.

NameTypeReqDescription
channel_idstringyesNeeds to end with 'CH'.
new_profileobjectyesChanges to the business profile. This is a PATCH request, so only pass fields the user wants changed. If you want to clear a field, set it to null. If you don't want to change a field, omit it from t…
project_idstringyesNeeds to end with 'PR'.
NameTypeReqDescription
channel_idstringyes–
messagestringyes–
updatedbooleanyes–

No examples provided.

update_commerce_settings ~120

Turn the catalog visibility and the cart on or off for a channel. This changes what WhatsApp users see in the chat with the business. Pass at least one of 'catalog_visible' and 'cart_enabled'; a value that is left out keeps its current setting.

NameTypeReqDescription
cart_enabled––Whether the cart is enabled for WhatsApp users. Omit to leave unchanged.
catalog_visible––Whether the catalog is visible to WhatsApp users. Omit to leave unchanged.
channel_idstringyesNeeds to end with 'CH'.
NameTypeReqDescription
channel_idstringyes–
settingsobjectyes–

No examples provided.

update_company_details ~132

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 the user if they want to change their company details in 360Dialog. 3. Get the user's approval/confirmation.

NameTypeReqDescription
billing_countrystringyesISO country code, for example 'DE'
company_namestringyesThe company's name
tax_id–yesOptional - the company's tax ID
NameTypeReqDescription
clientobjectyes–

No examples provided.

verify_otp ~81

Verify the 6-digit OTP code from the user. Doing so will automatically replay the blocked tool call that required verification, except for tools whose result is shown to the user in an app: for those, the result says to call the tool again.

NameTypeReqDescription
codestringyes6-digit OTP code. You must receive this from the user.
NameTypeReqDescription
call_again_tool–––
messagestringyes–
replayedbooleanyes–
replayed_structured_content–––
replayed_tool–––
verifiedbooleanyes–

No examples provided.

wait_for_onboarding_step ~322

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. Call this tool again to keep waiting. - "failed": There was an error. 'channel_id' and 'phone_number' are returned back once a channel is found so you can pass 'phone_number' into the next call once you have it. When 'phone_number' is omitted, 'candidates' lists the client's most recently created channels - check it if you're unsure the right number was picked (e.g. two users connecting numbers on the same 360Dialog client account). Only use this for the short waits during onboarding. This tool is NOT suitable for display name approval, WABA approval, or business verification scenarios, as they take days, not seconds.

NameTypeReqDescription
phone_number––The phone number to wait for - optional. If absent for 'number_connected' and 'channel_live', reports back with top 3 recently connected/went live phone numbers. If present, it checks the status for…
stepstringyesWhich step to wait for: 'number_connected' (a new phone number was added), 'payment_connected' (the client has a payment method), or 'channel_live' (the number is ready to send messages).
NameTypeReqDescription
candidates–––
channel_id–––
detailstringyes–
observed–––
phone_number–––
statestringyes–

No examples provided.

Install

How do I install the 360dialog MCP server?

360dialog is a hosted endpoint at https://mcp.360dialog.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.360dialog.com

# add to Claude Code
claude mcp add --transport http com-360dialog-mcp 'https://mcp.360dialog.com/mcp'
Common questions

What is the 360dialog MCP server?

360dialog is an MCP server listed in the public MCP registry as com.360dialog/mcp. Manage WhatsApp Business accounts on 360Dialog: channels, templates, sandbox, inbox, and more. This page covers its hosted endpoint (https://mcp.360dialog.com/mcp).

Is the 360dialog MCP server safe to use?

360dialog scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the 360dialog MCP server expose?

360dialog exposes 138 tools: list_skills, get_skill, start_signup, search_client_documentation, get_client_documentation_page, and 133 more. Their descriptions and schemas cost roughly 20,275 tokens of context every time the server is loaded.

Does the 360dialog MCP server require authentication?

Yes. 360dialog asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the 360dialog MCP server still maintained?

360dialog is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the 360dialog MCP server?

VerifyMCP ran 14 checks on 360dialog, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.