What the Omnifox MCP server is and what it does
The Omnifox MCP server connects Claude, Cursor, and other AI assistants to your workspace so they can read and write in your inbox, contacts, CRM, and calendar.
Watch this step in the video · MCP: let an AI operate Omnifox
The Model Context Protocol (MCP) is an open standard that lets an AI assistant use external tools. The Omnifox MCP server is the official package that turns the Omnifox REST API into those tools: once connected, your assistant can read conversations, reply to messages, create contacts, move CRM deals, book appointments, or take catalog orders, without you writing a single line of code.
The package is called @omnifox/mcp-server and it is published on npm. Version 0.4.0 exposes 72 tools across contacts, messaging, conversations, internal notes, workspace, calendar, catalog and orders, workflows, broadcasts, webhooks, and reports.
What you use it for
- Work your inbox from your assistant. "Find Maria's conversation, summarize it, and tell her that her order ships tomorrow."
- Check data without opening Omnifox. "How many new conversations came in this week, by channel?"
- Automate repetitive tasks. Tag, assign to a team, snooze conversations, or close threads with a resolution.
- Build your own agents. Any MCP client (Claude Desktop, Cursor, Continue, Composio, agent SDKs) can be built on top of these tools.
What you need
- A plan with API Access: available from Crece up (Crece, Escala, and Exclusivo). The Lite, Impulsa, and Conecta plans do not include it.
- An API key (personal token) created in Settings → Development → API Keys.
- Node.js 18.17 or higher on the computer or server where the assistant runs.
- An MCP-compatible client.
How it connects, in short
The server is not installed inside Omnifox: it runs on the AI client side. In your client's configuration you declare the command npx -y @omnifox/mcp-server and pass your token in the OMNIFOX_API_KEY variable. The client starts the server, discovers the 72 tools, and from then on the model uses them when needed.
What it does NOT do
- It does not upload files: the messaging tools send attachments by public URL, not by direct upload.
- It does not expose the Team module or Co-browse.
- It does not replace Omnifox AI agents, which live inside the platform and answer your customers on their own. The MCP server is so your assistant can work on Omnifox.
Tips
- Create an API key dedicated to the MCP server, with the minimum permissions. If you ever want to cut off access, you revoke it without touching your other integrations.
- The token is tied to a single workspace. If you work with several, you need one key per workspace.
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.