360dialog
REMOTE · MCP.360DIALOG.COM
Manage WhatsApp Business accounts on 360Dialog: channels, templates, sandbox, inbox, and more.
Available components
Last scanned (21 hours ago)
Scores higher than 71% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Communication
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
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 →
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.
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 |
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 →
block_users Block users ~162
Block WhatsApp users from messaging a channel. Identify each user by phone number or by BSUID; pass at least one of 'phone_numbers' and 'user_ids'. Only a business can block users who recently messaged it, so some users can fail. The result lists which succeeded and which failed with the reason.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Needs to end with 'CH'. |
| phone_numbers | – | – | Phone numbers of the WhatsApp users to block, in international format without '+' or spaces, for example ['49100100200']. |
| user_ids | – | – | Business-scoped user IDs (BSUIDs) of the WhatsApp users to block, for users whose phone number isn't known. 'list_blocked_users' shows each blocked user's BSUID. |
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| failed | array | yes | – |
| succeeded | array | yes | – |
No examples provided.
change_user_role Change user role ~126
Change the role of an existing user of the account. Users cannot change their own role. Client users change users of their own client account, partner users users of the partner account. The user may be prompted by 360Dialog for an OTP code delivered to their email address.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | yes | New role. 'partner-owner' or 'partner-member' on a partner account, 'client-owner' or 'client-member' on a client account. |
| user_id | string | yes | Needs to end with 'U'. Use 'list_users' to find a user's ID. |
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | – |
| changed | boolean | yes | – |
| message | string | yes | – |
| role | string | yes | – |
| user_id | string | yes | – |
No examples provided.
check_number_eligibility Check number eligibility ~154
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 (including the personal app) can still come back eligible here.
| Name | Type | Req | Description |
|---|---|---|---|
| check_coex | boolean | – | Set to true if the phone number to check is currently on the WhatsApp Business app (not to be confused with the normal, personal, WhatsApp app.) WhatsApp Business app numbers can be onboarded to the… |
| phone_number | string | yes | The phone number to check |
| Name | Type | Req | Description |
|---|---|---|---|
| checked | boolean | yes | – |
| checks | – | – | – |
| cta_action | – | – | – |
| eligibility_status | – | – | – |
| eligible | boolean | – | – |
| message | – | – | – |
No examples provided.
create_partner_change_request Create partner change request ~260
Request that the client's numbers move to a new partner. The new partner has to approve the request; then the numbers are moved, which changes who manages them and who is billed. ALWAYS call 'preview_partner_change_request' first with the same arguments, show its result to the user and get their confirmation before calling this tool. This tool also runs the preview itself and does NOT create the request when the preview finds issues; it then returns the issues instead. The user may be prompted by 360Dialog for an OTP code delivered to their email address.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_bundles | – | – | Optional. Which payment plan of the new partner each number moves onto. Only needed when the new partner bills its clients. |
| channel_ids | array | yes | IDs 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_id | string | yes | ID of the partner the numbers should move to. Needs to end with 'PA'. |
| Name | Type | Req | Description |
|---|---|---|---|
| actions_required | array | yes | – |
| created | boolean | yes | – |
| message | string | yes | – |
| preview_ready | boolean | yes | – |
| request | – | – | – |
No examples provided.
create_template Create template ~1,683
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 lowercase snake_case. - category must be uppercase. - language must be a WhatsApp locale code such as "en_US", "tr", "es", "pt_BR". - Only include fields supported by the component variant. - Do not include null fields. - Components should normally be ordered as: 1. header, if any 2. body 3. footer, if any 4. buttons, if any - A template can have at most one header, one body, one footer, and one buttons component. - BODY is required unless the user is clearly creating a special authentication template handled elsewhere. - HEADER and FOOTER are optional. - BUTTONS are optional. Component variants: 1. Text header without variables { "type": "HEADER", "format": "text", "text": "Your order update" } Use this when the header is plain text. 2. Text header with variables { "type": "HEADER", "format": "TEXT", "text": "Hi {{1}}", "example": { "header_text": ["Alice"] } } Rules: - Text header supports template variables. - If text contains variables, include example.header_text. - The example array must contain sample values in the same order as the variables appear. - For named parameters, the placeholder names appear in text, but the examples are still values. 3. Image header { "type": "HEADER", "format": "IMAGE", "example": { "header_handle": ["https://example.com/sample-image.jpg"] } } Use this when the template header should contain an image. The example should be a sample image handle or URL when available. 4. Video header { "type": "HEADER", "format": "VIDEO", "example": { "header_handle": ["https://example.com/sample-video.mp4"] } } Use this when the template header should contain a video. The example should be a sam…
| Name | Type | Req | Description |
|---|---|---|---|
| template_json | object | yes | The template's JSON. |
| waba_account_id | string | yes | Needs to end with 'WA'. |
| Name | Type | Req | Description |
|---|---|---|---|
| created | boolean | yes | – |
| example | – | – | – |
| message | – | – | – |
| template | – | – | – |
No examples provided.
delete_template Delete template ~62
Delete a WhatsApp message template by its internal template ID.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | Needs to end with 'WT'. Use 'list_templates' to find a template's ID. |
| waba_account_id | string | yes | Needs to end with 'WA'. |
| Name | Type | Req | Description |
|---|---|---|---|
| deleted | boolean | yes | – |
| message | string | yes | – |
| template_id | string | yes | – |
No examples provided.
enable_local_storage Enable local storage ~79
Store a channel's message data in a chosen region. The channel is re-registered in Cloud API after calling this tool. Contact our support team if this tool fails.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Needs to end with 'CH'. |
| data_localization_region | string | yes | Region code where this number's message data is at rest. |
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| data_localization_region | string | yes | – |
No examples provided.
get_business_username_suggestions Get business username suggestions ~53
Suggest available WhatsApp business usernames for a channel. Meta reserves these usernames for the number's business. Use this before 'set_business_username'.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Needs to end with 'CH'. |
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| suggestions | array | yes | – |
No examples provided.
get_channel_details Get channel details ~139
Show the full details of one channel: status, availability, quality rating, messaging limit, registration code status, and its WABA, project, client and app IDs. Also shows the channel's WhatsApp Business Account (WABA): its status, Meta business verification status, message-on-behalf status, phone number and conversation limits, Meta ban state, and any policy violations affecting this number. Use it to troubleshoot restricted or unverified accounts. Useful for when the user asks more details for a specific number. Use 'list_channels' to find channels first.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Needs to end with 'CH'. |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | object | yes | – |
No examples provided.
get_channel_profile Get channel profile ~63
Get a channel's (a.k.a. phone number) WhatsApp profile, and the profile's 360Dialog Hub page.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Needs to end with 'CH'. |
| project_id | string | yes | Needs to end with 'PR'. |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| hub_url | – | – | – |
| message | – | – | – |
| profile | – | – | – |
No examples provided.
get_client_details Get client details ~50
Show one client's account details and status: name, status, number limit, contact information and Meta business ID. Client users see their own account. Partner users pass the ID of one of their clients.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| client | – | – | – |
| found | boolean | yes | – |
| message | – | – | – |
No examples provided.
get_client_documentation_page Get client documentation page ~134
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. https://docs.360dialog.com/docs/getting-started). Since `searchDocumentation` returns partial content, use `getPage` to retrieve the complete page when you need more details. The content includes links you can follow to navigate to related pages.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL of the page to fetch |
No output schema declared.
No examples provided.
get_commerce_settings Get commerce settings ~42
Show whether the WhatsApp Business catalog is visible and the cart is enabled on a channel.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Needs to end with 'CH'. |
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
| settings | object | yes | – |
No examples provided.
get_company_details Get company details ~19
Get the user's company's details from 360Dialog.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| client | object | yes | – |
No examples provided.
get_currency_migration_status Get currency migration status ~51
Show the progress of a WABA's billing currency change. Returns the most recent migration, or says there is none.
| Name | Type | Req | Description |
|---|---|---|---|
| waba_account_id | string | yes | Needs to end with 'WA'. |
| Name | Type | Req | Description |
|---|---|---|---|
| destination_waba_id | – | – | – |
| found | boolean | yes | – |
| meta_status | – | – | – |
| status | – | – | – |
| target_currency | – | – | – |
| waba_account_id | string | yes | – |
No examples provided.
get_messaging_analytics Get messaging analytics ~202
Show messages sent, delivered and billed for a phone number (channel) over a date range, and their cost. Without dates it covers the last 7 days; ranges over 90 days are summarised by month. Days follow the WhatsApp Business Account's timezone, and today (or this month) appears only once it's over. Rate limited, so prefer one call covering the whole range.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Needs to end with 'CH'. |
| end_date | – | – | Last day to include, as an ISO date like 2026-05-07. Defaults to today. |
| granularity | – | – | Report by day or by calendar month. Defaults to daily; ranges over 90 days are always monthly. |
| start_date | – | – | First day to include, as an ISO date like 2026-05-01. Defaults to 6 days before the end date, so the last 7 days when no dates are given. |
| Name | Type | Req | Description |
|---|---|---|---|
| by_category | array | – | – |
| by_day | array | – | – |
| channel_id | string | yes | – |
| cost_unavailable | boolean | – | – |
| currency | – | – | – |
| current_period_missing | boolean | – | – |
| display_name | – | – | – |
| end_date | string | yes | – |
| found | boolean | yes | – |
| granularity | string | yes | – |
| message | – | – | – |
| phone_number | – | – | – |
| start_date | string | yes | – |
| timezone | – | – | – |
| totals | – | – | – |
No examples provided.
get_onboarding_status Get onboarding status ~152
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 respond to the message using the API). Template messages are separately blocked until Meta reviews a submitted template (template reviews take up to 24 hours.) Lack of business verification is not a blocker. Unverified businesses can only send 250 templates to unique users per 24 hours.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | – | yes | Needs to end with 'CH'. |
| phone_number | – | – | The phone number of the number being onboarded |
| Name | Type | Req | Description |
|---|---|---|---|
| availability_status | – | – | – |
| can_send_templates | – | – | – |
| channel_status | – | – | – |
| found | boolean | yes | – |
| live | boolean | – | – |
| message | string | yes | – |
| messaging_limit | – | – | – |
| next_step | – | – | – |
| phone_number | – | – | – |
| quality_rating | – | – | – |
No examples provided.
get_platform_status Get platform status ~46
Check whether 360Dialog or WhatsApp currently has an outage or degraded service. Use this first when messages fail, webhooks stop, or the user asks whether the platform is down.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| all_operational | boolean | yes | – |
| components_with_issues | array | – | – |
| message | – | – | – |
| pages_with_issues | array | – | – |
| unavailable_sources | array | – | – |
| whatsapp_outages | array | – | – |
No examples provided.
get_self Get current user ~49
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
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | yes | – |
| message | – | – | – |
| ok | boolean | yes | – |
| profile | – | – | – |
No examples provided.
get_skill Get skill ~46
Get the full guide for one skill returned by 'list_skills', as markdown.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A skill's 'name' field, as returned by list_skills. |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| skill | – | – | – |
No examples provided.
get_template_json_example Get template JSON example ~156
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 user can later modify before sending the template to WhatsApp users. It is recommended that you use this tool after creating a template, or after the user asks how to send a template. Display the JSON result of this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | Needs to end with 'WT'. Use 'list_templates' to find a template's ID. |
| waba_account_id | string | yes | Needs to end with 'WA'. |
| Name | Type | Req | Description |
|---|---|---|---|
| example | – | – | – |
| message | – | – | – |
| template_id | string | yes | – |
| template_name | string | yes | – |
No examples provided.
get_voice_analytics Get voice analytics ~173
Show the number, duration and cost of calls for a phone number (channel) over a date range. Without dates it covers the last 7 days; ranges over 90 days are summarised by month. Days follow the WhatsApp Business Account's timezone, and today (or this month) appears only once it's over. Rate limited, so prefer one call covering the whole range.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Needs to end with 'CH'. |
| end_date | – | – | Last day to include, as an ISO date like 2026-05-07. Defaults to today. |
| start_date | – | – | First day to include, as an ISO date like 2026-05-01. Defaults to 6 days before the end date, so the last 7 days when no dates are given. |
| Name | Type | Req | Description |
|---|---|---|---|
| by_direction | array | – | – |
| channel_id | string | yes | – |
| cost_unavailable | boolean | – | – |
| currency | – | – | – |
| current_period_missing | boolean | – | – |
| display_name | – | – | – |
| end_date | string | yes | – |
| found | boolean | yes | – |
| granularity | string | yes | – |
| message | – | – | – |
| phone_number | – | – | – |
| start_date | string | yes | – |
| timezone | – | – | – |
| totals | – | – | – |
No examples provided.
get_webhook Get webhook ~185
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 channel's webhook URL and add the specified headers. This helps only authenticated requests pass through app firewalls, if the user has any. Example: If webhook URL is `https://foo.com/webhook`, and webhook headers are set to {"x-360dialog-webhook-security": "RANDOM-STRING"}, the webhook URL will receive POST requests like this: POST https://foo.com/webhook HEADERS x-360dialog-webhook-security: RANDOM-STRING
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Needs to end with 'CH'. |
| Name | Type | Req | Description |
|---|---|---|---|
| configured | boolean | yes | – |
| masked_headers | object | – | – |
| message | – | – | – |
| webhook | – | – | – |
No examples provided.
inbox_apply_saved_response Apply saved response ~124
Send a saved (canned) response into a conversation as a text message. Subject to the same 24-hour window rule as inbox_send_message.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | The 360dialog channel ID of the inbox to operate on. |
| conversation_id | string | yes | The conversation's contact WhatsApp ID (phone-style like '4915112345678', or business-scoped). Take it from list_conversations or search_conversations results; do not guess it. |
| saved_response_id | integer | yes | Saved response ID from list_saved_responses. |
Structured output declared, but exposes no named fields.
No examples provided.
inbox_assign_conversation Assign conversation ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | The 360dialog channel ID of the inbox to operate on. |
| conversation_id | string | yes | The conversation's contact WhatsApp ID (phone-style like '4915112345678', or business-scoped). Take it from list_conversations or search_conversations results; do not guess it. |
| group_id | – | – | Group ID from list_groups to assign; omit/null to leave unassigned. |
| user_id | – | – | Agent (user) ID from list_agents to assign; omit/null to leave unassigned. |
Structured output declared, but exposes no named fields.
No examples provided.
inbox_get_conversation Get conversation ~169
Read one conversation: contact/assignment/tag details plus its message history. Messages are returned newest first. To page further back, call again with `before_time` set to the oldest returned message's timestamp.
| Name | Type | Req | Description |
|---|---|---|---|
| before_time | – | – | Only messages strictly older than this POSIX timestamp — use for paging back through history. |
| channel_id | string | yes | The 360dialog channel ID of the inbox to operate on. |
| conversation_id | string | yes | The conversation's contact WhatsApp ID (phone-style like '4915112345678', or business-scoped). Take it from list_conversations or search_conversations results; do not guess it. |
| limit | integer | – | Maximum number of messages to return. |
| since_time | – | – | Only messages at or after this POSIX timestamp. |
Structured output declared, but exposes no named fields.
No examples provided.
inbox_list_agents List agents ~61
List the inbox's agents (users) — for assignment via inbox_assign_conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | The 360dialog channel ID of the inbox to operate on. |
| is_available | – | – | Filter by availability; omit to list all agents. |
Structured output declared, but exposes no named fields.
No examples provided.
inbox_list_conversations List conversations ~126
List conversations of the inbox, newest activity first. Returns one entry per conversation with contact info, unread count, last message, current assignee (user and/or group), and tags.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to_me | boolean | – | Only conversations assigned to the calling user. |
| channel_id | string | yes | The 360dialog channel ID of the inbox to operate on. |
| limit | integer | – | – |
| offset | integer | – | – |
| tag_id | – | – | Only conversations carrying this tag (see list_tags). |
| unread | boolean | – | Only conversations with unread incoming messages. |
Structured output declared, but exposes no named fields.
No examples provided.
inbox_list_groups List agent groups ~45
List the inbox's agent groups — for group assignment via inbox_assign_conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | The 360dialog channel ID of the inbox to operate on. |
Structured output declared, but exposes no named fields.
No examples provided.
inbox_list_inboxes List inboxes ~156
List the WhatsApp inboxes the calling 360dialog user can access. Call this first when you don't know which `channel_id` to pass to the other tools: each entry pairs a `channel_id` with its inbox URL and WhatsApp number (`wa_id`). Entries without a `channel_id` cannot be driven through these tools. The listing covers the caller's own client accounts, plus every inbox under a partner the caller administers. It never reaches another tenant: a client user is not shown other clients' inboxes, including ones managed by the same partner. An empty list does not mean no inbox exists; pass a known `channel_id` to the other tools directly.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
inbox_list_saved_responses List saved responses ~63
List the inbox's saved (canned) responses — for use with inbox_apply_saved_response.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | The 360dialog channel ID of the inbox to operate on. |
| search | – | – | Only saved responses whose text contains this substring. |
Structured output declared, but exposes no named fields.
No examples provided.
inbox_list_tags List tags ~50
List the inbox's tags — for tagging via inbox_tag_conversation and filtering via inbox_list_conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | The 360dialog channel ID of the inbox to operate on. |
Structured output declared, but exposes no named fields.
No examples provided.
inbox_mark_conversation_as_read Mark conversation as read ~234
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 state is per inbox user: this clears the unread count for the caller only, not for other agents. The inbox also marks the messages as read on WhatsApp, so the contact sees read receipts. Only conversations whose messages you can read can be marked.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | The 360dialog channel ID of the inbox to operate on. |
| conversation_id | string | yes | The conversation's contact WhatsApp ID (phone-style like '4915112345678', or business-scoped). Take it from list_conversations or search_conversations results; do not guess it. |
| up_to_timestamp | – | – | Timestamp of the last message you reviewed, taken from get_conversation results; messages up to and including it are marked read, newer ones stay unread. Omit to mark everything currently in the conv… |
Structured output declared, but exposes no named fields.
No examples provided.
inbox_search_conversations Search conversations ~108
Find conversations by contact name, phone number, tag name, or message content. Searches contact profiles and tags first, then message text and media captions; results from both are merged and deduplicated by conversation. Each match notes why it matched (`contact` or `message_content`).
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | The 360dialog channel ID of the inbox to operate on. |
| limit | integer | – | – |
| query | string | yes | Text to search for. |
Structured output declared, but exposes no named fields.
No examples provided.
inbox_send_message Send message ~248
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 explanation.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | The 360dialog channel ID of the inbox to operate on. |
| content | – | – | The type-specific message object, following the WhatsApp Business API shape. For type=text: {"body": "..."}. For image/video: {"link": "https://...", "caption"?}. For document: {"link": "https://..."… |
| conversation_id | string | yes | The conversation's contact WhatsApp ID (phone-style like '4915112345678', or business-scoped). Take it from list_conversations or search_conversations results; do not guess it. |
| type | string | – | WhatsApp message type of `content`. |
Structured output declared, but exposes no named fields.
No examples provided.
inbox_tag_conversation Tag conversation ~116
Add or remove one tag on one conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Add the tag to or remove it from the conversation. |
| channel_id | string | yes | The 360dialog channel ID of the inbox to operate on. |
| conversation_id | string | yes | The conversation's contact WhatsApp ID (phone-style like '4915112345678', or business-scoped). Take it from list_conversations or search_conversations results; do not guess it. |
| tag_id | integer | yes | Tag ID from list_tags. |
Structured output declared, but exposes no named fields.
No examples provided.
invite_user Invite user ~177
Invite a new user to the account, with a role. The invitee gets an email with a link to set their password. Client users invite to their own client account, partner users to the partner account. To create a new client together with its first user, use 'create_client_and_invite'. The user may be prompted by 360Dialog for an OTP code delivered to their email address.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address of the person to invite. | |
| name | string | yes | Full name of the person to invite. |
| role | string | yes | Role to give the new user. 'partner-owner' or 'partner-member' on a partner account, 'client-owner' or 'client-member' on a client account. Owners can invite users and manage the account; members can… |
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | – |
| string | yes | – | |
| invited | boolean | yes | – |
| message | string | yes | – |
| role | string | yes | – |
No examples provided.
list_blocked_users List blocked users ~81
Show which WhatsApp users are blocked from messaging a channel. Meta always returns the BSUID; phone number is only returned when it has been shared with the business. To unblock a user without a phone number, pass their BSUID to 'unblock_users' in 'user_ids'.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | Needs to end with 'CH'. |
| Name | Type | Req | Description |
|---|---|---|---|
| blocked_users | array | yes | – |
| channel_id | string | yes | – |
No examples provided.
list_channels List channels ~202
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 single page. Returns: If no channel matches, returns "No channels found." If found, returns information of channels, like WABA ID, client ID, channel ID, app ID and the number's 360Dialog Hub page, along with the current page, total pages, and total count.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | – | – | Optional filter. You can pass a phone number, client ID, or channel ID here. Defaults to None; call without this argument if you want to get all channels. |
| page | integer | – | Page number to retrieve, starting at 1. |
| size | integer | – | Number of channels to return per page, at most 100. |
| Name | Type | Req | Description |
|---|---|---|---|
| channels | – | – | – |
| found | boolean | yes | – |
| message | – | – | – |
| page | – | – | – |
| total_count | – | – | – |
| total_pages | – | – | – |
No examples provided.
list_partner_change_requests List partner change requests ~153
List requests to move numbers between partners, with their status. Client users see the requests their client made. Partner users see the requests addressed to their partner, which they can approve or reject; a partner can pass 'client_id' to only see the requests of one client. Pass 'request_id' to follow the status of one request.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number to retrieve, starting at 1. |
| request_id | – | – | Optional. Only show the request with this ID. |
| size | integer | – | Number of requests to return per page, at most 100. |
| status | – | – | Optional. Only list requests in this status. 'created' means waiting for the new partner's approval. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| message | string | yes | – |
| requests | array | yes | – |
| total | – | – | – |
No examples provided.
list_platform_status_subscriptions List platform status subscriptions ~26
List the user's 360Dialog status update subscriptions (delivered via email).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| – | – | – | |
| message | – | – | – |
| subscriptions | array | – | – |
No examples provided.
list_skills List skills ~114
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 products or processes - it tells you which skills exist and when to use them. Once you find a match, call 'get_skill' with its 'name' to read the full guide.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| skills | array | yes | – |
No examples provided.
list_templates List templates ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name_filter | – | – | Template name to search for. If one is not provided, leave blank. |
| status_filter | – | – | Filter templates by status. Allowed values are 'approved', 'pending', 'paused', 'rejected'. Leave blank if not needed. |
| waba_account_id | string | yes | Needs to end with 'WA'. |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| message | – | – | – |
| templates | – | – | – |
No examples provided.
list_users List users ~42
List users of the selected account, including their roles and creation timestamps. Client users get the users of their own client account, partner users the users of the partner account.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| message | – | – | – |
| ok | boolean | yes | – |
| users | – | – | – |
No examples provided.
mba_add_allowlist_entry Add an allowlisted number ~116
Add one consumer phone number to the allowlist. Returns the created {id, consumer_phone_number}. The allowlist only takes effect while ai_audience is ALLOWLISTED_ONLY; under EVERYONE the agent answers all consumers regardless of this list.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to. |
| consumer_phone_number | string | yes | Consumer's WhatsApp number in E.164 format, e.g. +15551234567. |
No output schema declared.
No examples provided.
mba_check_agent_eligibility Check agent eligibility ~108
Check whether this channel's WhatsApp number is eligible for a Meta Business Agent. Returns {is_eligible: boolean}. Known limitation: a 403 from this call can mean the number is simply not eligible, rather than that the business has not accepted Meta's terms - do not report an unaccepted-terms problem on a 403 alone.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to. |
No output schema declared.
No examples provided.
mba_create_agent_skill Create an agent skill ~154
Add a skill to the agent - an instruction text that changes how it answers. Returns the created skill with its id. Skills are the right home for behavioural instructions; facts the agent should know belong in FAQs, websites or files instead.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Optional - attach the skill to one agent. |
| app_id | string | yes | The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to. |
| description | string | – | What the skill is for (max 1024 characters). |
| skill | string | – | The instruction text the agent follows (max 20000 characters). |
| title | string | – | Short name for the skill (max 64 characters). |
No output schema declared.
No examples provided.
mba_create_connector Create a connector ~241
Create a connector so the agent can call a third-party system. Returns the connector with its id and connection_status. A connector on its own does nothing - add connector tools with mba_create_connector_tool to expose individual operations to the agent.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to. |
| auth_config | object | – | 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_type | string | yes | How the connected system authenticates. |
| base_url | string | yes | Base URL every tool on this connector calls. |
| description | string | yes | What the connected system does. |
| name | string | yes | Name of the connector. |
| requires_certificate | boolean | – | True when the system needs mTLS; upload the certificate with upsert_connector_certificate. |
| user_auth_injection_config | object | – | Optional configuration for injecting a per-user token into tool requests. |
No output schema declared.
No examples provided.
mba_create_connector_tool Create a connector tool ~254
Define one action the agent can perform through a connector - an outbound HTTP request against the connector's base_url. Returns the created tool with its id. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to. |
| connector_id | string | yes | Connector id. |
| description | string | yes | What the action does - the agent uses this to decide when to call it. |
| name | string | yes | Name the agent sees for this action. |
| request_definition | object | yes | The outbound HTTP request this tool makes, relative to the connector's base_url. |
| user_auth_action_config | object | – | Optional login/refresh response extraction config, for user-auth actions. |
| user_auth_required | boolean | yes | True when the call needs a per-user token rather than the connector's own credentials. |
No output schema declared.
No examples provided.
mba_create_faq Create an FAQ ~108
Add one question-and-answer entry to the agent's knowledge. Returns the created entry with its id. FAQs are the right home for knowledge that does not fit business info's six fields.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The answer the agent should give. |
| app_id | string | yes | The 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to. |
| metadata | object | – | Optional free-form metadata. |
| question | string | yes | The customer's question. |
No output schema declared.
No examples provided.
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
claude mcp add --transport http com-360dialog-mcp 'https://mcp.360dialog.com/mcp'
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.