Connect the Omnifox MCP server to Claude Desktop, Cursor, or Continue
Step-by-step setup of the Omnifox MCP server in the most used desktop clients, with the real files and paths for each one.
Watch this step in the video · Test the MCP server with the Inspector
The Omnifox MCP server runs on your machine through npx, so there is nothing to install by hand: you just declare it in your AI client's configuration file and restart it.
Before you start
- A plan with API Access (from Crece up).
- Node.js 18.17 or higher installed (
node -vto check). - An API key created in Settings → Development → API Keys. Copy it the moment you create it: it is shown only once.
Claude Desktop
- Open the
claude_desktop_config.jsonfile:- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
- Add the
omnifoxblock insidemcpServers:
{
"mcpServers": {
"omnifox": {
"command": "npx",
"args": ["-y", "@omnifox/mcp-server"],
"env": {
"OMNIFOX_API_KEY": "tu-token-aqui"
}
}
}
}
- Save the file and quit and reopen Claude Desktop completely.
Cursor
- In your project root, create or edit
.cursor/mcp.json. - Use exactly the same
mcpServersblock from the example above. - Restart Cursor.
Continue
- Edit
~/.continue/config.json. - Add the server under
experimental.modelContextProtocolServers:
{
"experimental": {
"modelContextProtocolServers": [
{
"transport": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@omnifox/mcp-server"],
"env": { "OMNIFOX_API_KEY": "tu-token-aqui" }
}
}
]
}
}
- Restart Continue.
Verify it
Ask your assistant for something simple that forces it to use a tool, for example: "list the connected channels in Omnifox". If it answers with your real channels, the connection works. The first call may take a few seconds because npx downloads the package.
If something does not work
- The client shows no tools: almost always the app needs a full restart, not just closing the window.
OMNIFOX_API_KEY is required: theenvblock is malformed or the token was left empty.- Every call returns 401: the token expired, was revoked, or was copied with leading or trailing spaces.
- Everything returns 402 or
PLAN_API_ACCESS_REQUIRED: your plan does not include API Access. npxnot found: Node.js is missing, or the client starts with a PATH that does not see it; use the absolute path tonpxincommand.
Tips
- Do not keep the token in a file you push to a repository:
.cursor/mcp.jsonoften ends up versioned. - If you work with more than one workspace, declare one server per workspace with different names (
omnifox-ventas,omnifox-soporte) and one key for each.
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.