Omnifox MCP server tools: full reference
The 72 tools @omnifox/mcp-server exposes, grouped by module, with what each one does.
Watch this step in the video · MCP: let an AI operate Omnifox
This is the full list of tools the Omnifox MCP server makes available to the assistant. The names are the ones you will see in your AI client's registry. In version 0.4.0 there are 72.
Two rules that apply everywhere: all ids are positive integers, never UUIDs; and wherever a contact is expected, a type:value selector is also accepted (email:[email protected], phone:+593987654321, external:abc).
Contacts (11)
| Tool | What it does |
|---|---|
get_contact |
Fetches a contact by id or by selector. |
create_contact |
Creates a contact. display_name is the only required field. |
update_contact |
Updates only the fields you send. |
delete_contact |
Deletes the contact and everything attached to it. Irreversible. |
list_contacts |
Lists contacts, most active first. |
search_contacts |
Free-text search by name, email, and phone (minimum 2 characters). |
add_contact_tags |
Adds tags by name; creates the ones that do not exist. |
remove_contact_tags |
Removes tags by name. |
create_or_update_contact |
Idempotent create: searches by the keys you specify and creates if there is no match. |
merge_contacts |
Merges one contact into another. The primary one survives. |
list_contact_channels |
Lists the contact's channel identities. |
Messaging (5)
| Tool | What it does |
|---|---|
send_message |
Sends to a contact. Reuses its open conversation or opens one. Types: text, attachment, quick_reply, whatsapp_template, email. |
send_conversation_message |
Sends inside a conversation whose id you already know. With type: note it leaves an internal note. |
get_message |
Fetches a message with its delivery status. |
list_messages |
Lists a conversation's messages, oldest to newest. |
retry_message |
Retries delivery of a failed message. |
Attachments travel as a public URL: Omnifox downloads it. The MCP server does not upload files.
Conversations (9)
| Tool | What it does |
|---|---|
list_conversations |
Lists conversations; filters by open, pending, resolved, closed, or snoozed. |
get_conversation |
Fetches a conversation with its contact, channel, status, and assignment. |
get_conversation_sending_window |
Tells you whether free-form text can still be sent or whether a template is required. |
assign_conversation |
Assigns to a user, team, or AI agent, or unassigns. |
assign_contact_conversation |
Assigns the contact's open conversation when you do not have its id. |
update_conversation_status |
Reopens, resolves, or closes, with a resolution label and notes. |
update_contact_conversation_status |
The same, starting from the contact. |
snooze_conversation |
Snoozes the conversation so it comes back later. |
list_conversation_notes |
Lists the thread's internal notes. |
create_comment |
Adds an internal note to a conversation. |
Workspace (13)
list_users, get_user, set_user_status, list_custom_fields, get_custom_field, create_custom_field, list_channels, list_snippets, list_templates, list_tags, create_tag, update_tag, delete_tag.
These are for discovering ids before acting: list_channels and list_users are almost always the first useful call.
Calendar and appointments (13)
list_calendars, list_services, list_resources, list_sites, list_free_slots, book_appointment, list_appointments, reschedule_appointment, cancel_appointment, list_enrollments, enroll_contact, mark_attendance, cancel_enrollment.
Golden rule: always call list_free_slots before offering or booking a time, and pass the starts_at exactly as it was returned.
Catalog and orders (10)
search_products, get_product, create_product, update_product, list_orders, get_order, create_order, set_order_status, record_order_payment, get_catalog_settings.
Amounts are not sent: the server prices each line using the workspace's catalog and taxes.
Workflows, broadcasts, webhooks, and reports (11)
list_workflows, trigger_workflow, set_workflow_active, list_broadcasts, create_broadcast, cancel_broadcast, register_webhook, list_webhooks, list_workspaces, get_report.
get_report accepts four reports: overview, conversations, agents, and heatmap, with ranges today, yesterday, 7d, 30d, 90d, this_month, and last_month (the last 30 days by default).
Tips
- Responses come without the
{success, data}envelope and with listings flattened to{items, page, last_page, per_page, total}: less noise for the model. - On WhatsApp, outside the 24-hour window only an approved template is delivered. Check
list_templatesand send withsend_messageusingtype: whatsapp_template.
Related articles
Related articles
-
How to connect integrations and external apps
Connect Omnifox with your favorite tools from the integrations catalog in just a few steps.
-
Integrations and API complete guide
Integrations and API in depth, in 30 chapters: API keys, real calls, signed webhooks, n8n, MCP and SDKs, all really working.
-
Connecting Omnifox to Azur, Siigo, Alegra, QuickBooks or another accounting system or ERP
Omnifox doesn't have a native connector for accounting systems or ERPs today. Here's how to connect them anyway with workflows, the HTTP node, n8n, Make, Zapier or the API, with examples.
-
Generate and use API keys and webhooks
Create API keys to access Omnifox programmatically and set up webhooks to receive real-time events.
-
Getting started with integrations (webhook / OAuth / API key)
Connect Omnifox with your other tools: what's available today, what's coming soon, and when to use a webhook, an OAuth connection or an API key.