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_create_ui_skill ~286

Give the agent one more rich WhatsApp component to send, and the instruction that says when to send it. Returns the created UI skill with its id. 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 is FIXED AT CREATION and cannot be changed afterwards. flow_id is required when component_type is `flow`, and is refused for every other type; a flow UI skill also cannot be enabled until the flow itself is published.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
component_typestringyesThe kind of rich message this UI skill sends. Cannot be changed after creation.
flow_idinteger–The flow to send. Required when component_type is `flow`, refused otherwise.
instructionstringyesTells the agent when to send this component, e.g. 'Send this when the customer asks to browse the catalog'.
statusstringyesWhether the agent may send this component. Only an enabled UI skill is available to the agent.
titlestringyesHuman-readable name for the UI skill.

No output schema declared.

No examples provided.

mba_create_website ~93

Add a website URL for the agent to crawl into its knowledge base. Returns the entry with its id and crawl status. Crawling is asynchronous - the knowledge is not available immediately; poll mba_get_website for crawl_status.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
urlstringyesWebsite URL to crawl.

No output schema declared.

No examples provided.

mba_delete_agent ~104

Remove the Meta Business Agent from this channel's WhatsApp number. Deletes the agent configuration and, when the last agent on the account is removed, disconnects the integration entirely. Returns {deleted_agent_id}. This is irreversible: knowledge, skills and connectors configured on the agent go with it, and restoring the setup means onboarding again from scratch.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

No output schema declared.

No examples provided.

mba_delete_agent_skill ~69

Delete one agent skill by its id, so the agent stops following it. Returns no content on success.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
skill_idstringyesAgent skill id.

No output schema declared.

No examples provided.

mba_delete_connector ~68

Delete one connector by its id. Its tools and stored credentials go with it. Returns no content on success.

NameTypeReqDescription
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_delete_connector_tool ~83

Delete one connector tool definition by its id, so the agent can no longer perform that action. Returns no content on success.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
connector_idstringyesConnector id.
tool_idstringyesConnector tool id.

No output schema declared.

No examples provided.

mba_delete_faq ~62

Delete one FAQ entry by its id. Returns no content on success.

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

No output schema declared.

No examples provided.

mba_delete_file ~66

Delete one file from the agent's knowledge base by its id. Returns no content on success.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
file_idstringyesKnowledge file id.

No output schema declared.

No examples provided.

mba_delete_ui_skill ~89

Delete one UI skill by its id, so the agent stops sending that component. Returns no content on success. To stop the component temporarily, set status to `disabled` with mba_update_ui_skill instead.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
instruction_idstringyesUI skill id.

No output schema declared.

No examples provided.

mba_delete_website ~71

Remove one website crawl entry by its id, dropping the knowledge crawled from it. Returns no content on success.

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

No output schema declared.

No examples provided.

mba_get_agent_budgets ~279

Read the usage caps in force for the agent, each with its budget_id. Returns {budgets}; an empty array means no cap is set and usage is unlimited. Known limitations: budgets are ONLY SERVED for the business that owns this number's WABA; any other business_id is refused with an error that says so. For a number whose business is not known to 360dialog yet, budgets are not available and this tool returns an error that says so. When several caps are set, whichever is reached first stops the agent until its window resets, and the agent then hands conversations to the business. Token caps apply across the WHOLE BUSINESS MANAGER, so every agent in that portfolio shares them; AI-turn caps apply per conversation. These tools set and read caps and do not report usage against them: mba_get_agent_usage_insights reports billed usage, keyed on the billable account ID and not on business_id.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
business_idstringyesThe Meta Business Manager ID of the business that owns this number's WABA. No other tool returns it: it is the WABA's owner business in Meta Business Suite, and the 360dialog hub shows it on the chan…

No output schema declared.

No examples provided.

mba_get_agent_event ~111

Read the processing status of an event submitted with mba_send_agent_event. Status is one of request_received, processing, sent, failed, skipped or success; failed and skipped carry error_message and skipped_reason. This is the only way to find out whether an accepted event actually reached the consumer.

NameTypeReqDescription
agent_event_idstringyesEvent id returned by send_agent_event.
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

No output schema declared.

No examples provided.

mba_get_agent_event_insights ~223

Read what happened to the events sent to the agent (mba_send_agent_event) over a date range, one row per event type, busiest first: how many were received, how many the agent successfully processed, and the mean end-to-end latency. Successfully processed means the agent sent its message, not that the message was delivered. Figures are rolled up once a day, so the most recent day may still be incomplete. Known limitation: the dates are in PACIFIC TIME, not the business time zone, and the range may span at most 30 days, counting both ends.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
end_datestringyesLast day to include, YYYY-MM-DD in Pacific Time. Inclusive.
event_typestring–Return only this event type, named as it was sent. Omit for every event type.
start_datestringyesFirst day to include, YYYY-MM-DD in Pacific Time. Inclusive.

No output schema declared.

No examples provided.

mba_get_agent_settings ~115

Read the agent's current settings: rollout, handoff, followup and ai_audience. Known limitation: this returns an ARRAY with one entry per channel, not a single object. Read the entry whose `channel` you care about (usually "whatsapp") rather than treating the response as an object.

NameTypeReqDescription
agent_idstring–Optional - restrict the read to one agent.
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

No output schema declared.

No examples provided.

mba_get_agent_skill ~70

Read one agent skill by its id, as returned by mba_list_agent_skills or mba_create_agent_skill.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
skill_idstringyesAgent skill id.

No output schema declared.

No examples provided.

mba_get_agent_state ~128

Read whether this channel has ever been onboarded and whether its agent has ever been activated, as {onboarded, activated_once}. Known limitation: this is NOT a Meta call - it reads this service's own tracking record, written when onboarding or a settings read/write goes through here. It answers 'did onboarding ever succeed' and 'was rollout ever enabled', and nothing about the agent's current configuration. For live state call mba_get_agent_settings.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

No output schema declared.

No examples provided.

mba_get_agent_usage_insights ~437

Read the billed usage of a Meta Business Agent account over a billing date range, one entry per HOUR, DAY or MONTH bucket: billable messages, billable tokens, and cost in the account's currency. Returns {usage}; an empty array means no usage in the range. Each entry carries its bucket start and end (Unix seconds, end exclusive), plus channel and sender_id when they are in dimensions. Metrics left out of metric_types are omitted from every entry, not returned as null. Tokens are BILLED tokens, the figure on the invoice, which can be fewer than the tokens the agent consumed. Known limitations: usage insights are ONLY AVAILABLE for numbers whose stack uses its own WABA access token; for any other number this tool returns an error that says so. The range is start INCLUSIVE, end EXCLUSIVE, and dates are evaluated in the billable account's timezone, so a day bucket can be 23 or 25 hours long. MONTH needs a range of whole months: start on the 1st, end on the last day of a month.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
billable_account_idstringyesThe billable account ID of the Meta Business Agent account. No other tool returns it: Meta Billing Hub shows it under Accounts > Meta Business Agent accounts. It is not the Business Manager ID the bu…
channelsarray–Only usage on these messaging surfaces.
dimensionsarray–Split each bucket by these axes. Omit to total the whole agent per bucket.
endintegeryesEnd of the range, Unix seconds. Exclusive: buckets that start before it.
granularitystringyesSize of each bucket.
metric_typesarray–Which metrics to return. Omit for all of them.
sender_idsarray–Only usage attributed to these sending entities.
startintegeryesStart of the range, Unix seconds. Inclusive: buckets that start at or after it.

No output schema declared.

No examples provided.

mba_get_business_info ~148

Read the business information the agent uses to answer customers. Returns empty or default values when none has been configured. 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.

No output schema declared.

No examples provided.

mba_get_commerce_settings ~84

Read this channel's WhatsApp commerce settings: whether the cart is enabled and whether the catalog is visible in the chat and on the business profile. Returns {data: [one entry]} with is_cart_enabled and is_catalog_visible.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

No output schema declared.

No examples provided.

mba_get_connector ~76

Read one connector by its id, including its connection_status and mTLS metadata. Credentials are never returned - the private key and secrets stay at Meta.

NameTypeReqDescription
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_get_connector_logs ~255

Read the connector's third-party error logs, or aggregated failure patterns when summary_only is true. Only errors from the third-party system are included, so an empty result means no failures, not no traffic. Known limitation: the time range must not exceed 7 DAYS, and only the last 7 days are retained - start_time defaults to 24 hours ago and end_time to now. Unlike the other list tools this one does return an object: {data: [...], stats: {...}}, with stats present only when include_stats is true.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
connector_idstringyesConnector id.
end_timeinteger–End of the range, Unix seconds.
include_statsboolean–Add aggregate statistics.
limitinteger–Default 100.
start_timeinteger–Start of the range, Unix seconds. Must be within the last 7 days.
summary_onlyboolean–Return failure patterns instead of entries.
tool_idstring–Restrict to one connector tool.
top_ninteger–Default 10.

No output schema declared.

No examples provided.

mba_get_connector_tool ~67

Read one connector tool definition by its id.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
connector_idstringyesConnector id.
tool_idstringyesConnector tool id.

No output schema declared.

No examples provided.

mba_get_conversation_insights ~235

Read how many conversations the agent replied in over a date range (ai_threads), and how many are currently handed from the agent to the business and still awaiting a business reply (ai_handoffs). Counts are per conversation, not per message, and match the business's own agent summaries. Returns {data: [one row]}, each metric as {count}, present only when requested. Known limitation: ai_handoffs is a SNAPSHOT of the present moment - it ignores start_date and end_date. The range may span at most 90 days, counting both ends, and each requested metric costs a separate scan, so ask only for what you need.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
end_datestringyesLast day to include, YYYY-MM-DD in the business time zone. Inclusive.
metricsarray–Which metrics to return. Omit for all of them.
start_datestringyesFirst day to include, YYYY-MM-DD in the business time zone. Inclusive.

No output schema declared.

No examples provided.

mba_get_conversation_turns ~362

Read the ordered turns of the most recent conversation between the agent and one customer. Each turn carries its turn_id, conversation_id and the observed steps - LLM calls with a preview of the model output, and tool calls with the tool name, input and output - plus latency and status where available. Use it to see why the agent answered the way it did. Malformed records, and tool responses that cannot be matched to a tool call, may be missing. This list is CURSOR-PAGINATED: it returns {data, paging} - page with the `after` cursor from paging.cursors, and stop when paging carries no `next` link, because a page can be empty and still have more after it.

NameTypeReqDescription
afterstring–Cursor - return the page immediately after it.
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
beforestring–Cursor - return the page immediately before it.
end_timestamp_msinteger–Only turns that started at or before this Unix time in milliseconds.
limitinteger–Maximum entries per page. A page can be shorter.
start_timestamp_msinteger–Only turns that started at or after this Unix time in milliseconds.
user_phone_numberstringyesThe customer: a phone number in digits only with the country code (15551234567, no + or separators), a Business-Scoped User ID such as US.2788620304833812, or the conversation_id returned by test_age…

No output schema declared.

No examples provided.

mba_get_eval_details ~128

Read per-conversation evaluation results - scores, per-turn labels, reasons and the transcript. Takes eval_ids, which is a different kind of id from the job_id that mba_get_eval_results takes. Read them from the eval_ids_by_score field of a completed job. mba_get_eval_results already adds these details when it can read that field, so call this tool when it could not.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
eval_idsstringyesComma-separated evaluation ids.

No output schema declared.

No examples provided.

mba_get_eval_results ~179

Read an evaluation job by its job_id. While the job runs this gives the status (QUEUED or RUNNING) and the progress. When the job fails it gives the error. When the job completes it gives the aggregated report: the summary text, the average conversation and turn scores, the highlights and the top failure categories. There is no separate summary call: a completed job already carries that report. For the per-conversation transcripts and per-turn labels, take the ids from `eval_ids_by_score` and call mba_get_eval_details. This tool adds a `details` key when it can read those ids for you.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
job_idstringyesJob id returned by start_eval_run.

No output schema declared.

No examples provided.

mba_get_faq ~70

Read one FAQ entry by its id, as returned by mba_list_faqs or mba_create_faq.

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

No output schema declared.

No examples provided.

mba_get_file ~76

Read one knowledge file's metadata by its id. Returns {id, file_name} - this returns metadata only, not the file's contents.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
file_idstringyesKnowledge file id.

No output schema declared.

No examples provided.

mba_get_tool_call_insights ~229

Read how each of the business's own tools performed over a date range, one row per tool, busiest first: how many conversations called it, its mean latency, and its success, error and timeout rates (0 to 1; timeouts count as errors too). Only tools the business supplied are reported. thread_count counts a conversation once per day, so one that called the tool on three days counts three times. Figures are rolled up once a day, so the most recent day may still be incomplete. Known limitation: the range may span at most 30 days, counting both ends.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
end_datestringyesLast day to include, YYYY-MM-DD in the business time zone. Inclusive.
start_datestringyesFirst day to include, YYYY-MM-DD in the business time zone. Inclusive.
tool_namestring–Return only this tool, named as it was registered. Omit for every tool called.

No output schema declared.

No examples provided.

mba_get_ui_skill ~121

Read one UI skill by its id, as returned by mba_list_ui_skills or mba_create_ui_skill. 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.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
instruction_idstringyesUI skill id.

No output schema declared.

No examples provided.

mba_get_website ~92

Read one website crawl entry by its id, including crawl_status, pages_crawled and last_crawled_at. This is how you check whether a site added with mba_create_website has been ingested yet.

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

No output schema declared.

No examples provided.

mba_list_agent_skills ~89

List the agent's skills - the instruction texts that shape how it behaves. Known limitation: this returns a BARE ARRAY, not an object with a `data` key.

NameTypeReqDescription
agent_idstring–Optional - restrict the list to one agent.
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

No output schema declared.

No examples provided.

mba_list_allowlist_entries ~86

List the consumer phone numbers allowed to reach the agent while ai_audience is ALLOWLISTED_ONLY. Known limitation: this returns a BARE ARRAY of {id, consumer_phone_number}, not an object with a `data` key.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

No output schema declared.

No examples provided.

mba_list_catalog_products ~283

List the products of one catalog connected to this channel's WhatsApp Business Account. A product's retailer_id is the product_retailer_id that product messages take. Known limitation: a catalog that is NOT CONNECTED to this WABA, or that does not exist, returns 403 Catalog not accessible - get valid ids from mba_list_product_catalogs. This list is CURSOR-PAGINATED: it returns {data, paging} - page with the `after` cursor from paging.cursors, and stop when paging carries no `next` link, because a page can be empty and still have more after it.

NameTypeReqDescription
afterstring–Cursor - return the page immediately after it.
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
beforestring–Cursor - return the page immediately before it.
catalog_idstringyesThe catalog ID, as list_product_catalogs returns it.
fieldsstring–Comma-separated fields to return, e.g. id,retailer_id,name,price,image_url,availability.
filterstring–Meta product filter as a JSON string, e.g. {"availability":{"eq":"in stock"}}.
limitinteger–Maximum entries per page. A page can be shorter.

No output schema declared.

No examples provided.

mba_list_connector_tools ~75

List the actions defined on one connector. Known limitation: this returns a BARE ARRAY, not an object with a `data` key.

NameTypeReqDescription
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_list_connectors ~97

List the agent's connectors - the third-party systems it can call. Each carries a connection_status (PENDING_OAUTH, ACTIVE, EXPIRED or ERROR) worth checking before relying on its tools. Known limitation: this returns a BARE ARRAY, not an object with a `data` key.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

No output schema declared.

No examples provided.

mba_list_eval_cases ~71

List the evaluation scenarios configured for this agent, each with its scenario text, categories, max_turns and success criteria. Their ids are what mba_start_eval_run takes.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

No output schema declared.

No examples provided.

mba_list_faqs ~65

List the agent's FAQ entries. Known limitation: this returns a BARE ARRAY, not an object with a `data` key.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

No output schema declared.

No examples provided.

mba_list_files ~73

List the files in the agent's knowledge base, as {id, file_name}. Known limitation: this returns a BARE ARRAY, not an object with a `data` key.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

No output schema declared.

No examples provided.

mba_list_product_catalogs ~207

List the Meta product catalogs connected to this channel's WhatsApp Business Account. Only id and name are returned unless `fields` asks for more. Use the catalog id with mba_list_catalog_products. This list is CURSOR-PAGINATED: it returns {data, paging} - page with the `after` cursor from paging.cursors, and stop when paging carries no `next` link, because a page can be empty and still have more after it.

NameTypeReqDescription
afterstring–Cursor - return the page immediately after it.
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
beforestring–Cursor - return the page immediately before it.
fieldsstring–Comma-separated fields to return, e.g. id,name,product_count,vertical. Default: id,name.
limitinteger–Maximum entries per page. A page can be shorter.

No output schema declared.

No examples provided.

mba_list_ui_skills ~237

List the agent's UI skills - the rich WhatsApp components (carousels, CTA URLs, flows, images, interactive lists and buttons, location) the agent may send, each with the instruction that says when to send 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. This list is CURSOR-PAGINATED: it returns {data, paging} - page with the `after` cursor from paging.cursors, and stop when paging carries no `next` link, because a page can be empty and still have more after it.

NameTypeReqDescription
afterstring–Cursor - return the page immediately after it.
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
beforestring–Cursor - return the page immediately before it.
limitinteger–Maximum entries per page. A page can be shorter.

No output schema declared.

No examples provided.

mba_list_websites ~72

List the websites the agent crawls for knowledge, with their crawl status. Known limitation: this returns a BARE ARRAY, not an object with a `data` key.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.

No output schema declared.

No examples provided.

mba_onboard_agent ~109

Create the Meta Business Agent for this channel on the given messaging channel. Creates the underlying entities and schedules asynchronous data-preparation jobs, so the agent is not immediately ready to answer. Returns {agent_id}. Onboarding does not switch the agent on: rollout stays disabled until mba_update_agent_settings enables it.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
channelstringyesMessaging channel to onboard.

No output schema declared.

No examples provided.

mba_release_thread_control ~93

Hand a consumer conversation back to the Meta Business Agent as the automatic responder, after a human agent has taken it over. Only releasing is supported here - taking control is restricted to configured escalation partners.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
tostringyesConsumer's WhatsApp number in E.164 format.

No output schema declared.

No examples provided.

mba_remove_allowlist_entry ~113

Remove one entry from the allowlist by its entry id, which comes from mba_list_allowlist_entries (it is not the phone number). Returns no content on success. While ai_audience is ALLOWLISTED_ONLY, removing the entry stops the agent answering that consumer.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
entry_idstringyesAllowlist entry id, as returned by list_allowlist_entries.

No output schema declared.

No examples provided.

mba_replace_agent_budgets ~363

Set the usage caps for the agent. Returns the caps in force after the write. This is a FULL REPLACEMENT of the set: send again every cap to keep, because any cap left out is removed, and an empty array clears all caps and returns the agent to unlimited. To edit an existing cap, pass back its budget_id from mba_get_agent_budgets; omit budget_id to add a new cap. Two caps with the same unit_type and time_window pair are rejected. Known limitations: budgets are ONLY SERVED for the business that owns this number's WABA; any other business_id is refused with an error that says so. For a number whose business is not known to 360dialog yet, budgets are not available and this tool returns an error that says so. When several caps are set, whichever is reached first stops the agent until its window resets, and the agent then hands conversations to the business. Token caps apply across the WHOLE BUSINESS MANAGER, so every agent in that portfolio shares them; AI-turn caps apply per conversation. These tools set and read caps and do not report usage against them: mba_get_agent_usage_insights reports billed usage, keyed on the billable account ID and not on business_id.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
budgetsarrayyesThe complete set of caps. An empty array removes every cap.
business_idstringyesThe Meta Business Manager ID of the business that owns this number's WABA. No other tool returns it: it is the WABA's owner business in Meta Business Suite, and the 360dialog hub shows it on the chan…

No output schema declared.

No examples provided.

mba_reset_business_info ~162

Reset the agent's business information to empty defaults and return the emptied object. Unlike most deletes this does not 404 afterwards - mba_get_business_info keeps working and returns the defaults. 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.

No output schema declared.

No examples provided.

mba_run_connector_tool ~213

Execute one connector tool once, as the agent would, and return what the third-party system answered. Use it to check a definition works before relying on it. `input` is a JSON-ENCODED STRING of the arguments, not an object. Known limitation: the result is DOUBLY STRINGIFIED - the response is {output, status} where `output` is a JSON string; parse `output`, then parse its `.body` to reach the third-party system's actual response. What this call does depends entirely on the tool being run: it can create, change or delete data in the connected system.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
connector_idstringyesConnector id.
inputstring–Arguments as a JSON-encoded string, e.g. '{"order_id":"123"}'. Defaults to an empty object.
tool_idstringyesConnector tool id.

No output schema declared.

No examples provided.

mba_send_agent_event ~163

Trigger the agent to act on a consumer conversation asynchronously - the event is queued and the call returns immediately with status "accepted" and an agent_event_id. Poll mba_get_agent_event with that id to find out what happened; a 202-style acknowledgement here does not mean the consumer was messaged. Known limitation: event.payload must be a JSON-ESCAPED STRING, not an object - pass "{\"order_id\":\"123\"}", not {"order_id": "123"}. Maximum 4096 characters.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
eventobjectyes–
tostringyesConsumer's WhatsApp number in E.164 format.

No output schema declared.

No examples provided.

mba_send_message ~200

Send a WhatsApp message to a consumer and release thread control back to the agent. The body is the WhatsApp Cloud API message object - set `type` and the matching payload key (text, template, interactive, image, ...). This messages a real person: it is subject to the platform's send eligibility rules, and outside a 24-hour customer service window only an approved template will be delivered.

NameTypeReqDescription
app_idstringyesThe 360dialog channel's app_id. Identifies which WhatsApp number the agent belongs to.
recipient_typestring–Defaults to individual.
templateobject–Used when type is template.
textobject–Used when type is text, e.g. {"body": "Hello"}.
tostringyesConsumer's WhatsApp number in E.164 format.
typestringyesMessage type, e.g. text, template, interactive, image.

No output schema declared.

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.