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.

Aug 19, 2026

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 -v to check).
  • An API key created in Settings → Development → API Keys. Copy it the moment you create it: it is shown only once.

Claude Desktop

  1. Open the claude_desktop_config.json file:
    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json
  2. Add the omnifox block inside mcpServers:
{
  "mcpServers": {
    "omnifox": {
      "command": "npx",
      "args": ["-y", "@omnifox/mcp-server"],
      "env": {
        "OMNIFOX_API_KEY": "tu-token-aqui"
      }
    }
  }
}
  1. Save the file and quit and reopen Claude Desktop completely.

Cursor

  1. In your project root, create or edit .cursor/mcp.json.
  2. Use exactly the same mcpServers block from the example above.
  3. Restart Cursor.

Continue

  1. Edit ~/.continue/config.json.
  2. 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" }
        }
      }
    ]
  }
}
  1. 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: the env block 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.
  • npx not found: Node.js is missing, or the client starts with a PATH that does not see it; use the absolute path to npx in command.

Tips

  • Do not keep the token in a file you push to a repository: .cursor/mcp.json often 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

Was this helpful?

Related articles

Message us on WhatsApp