Skip to main content

Cursor Setup

Early Access

Try our newest feature! Only available through reach out. Contact us to join the early access program and get priority support.

Prerequisites​

  • Cursor IDE
  • Unizo API key and Communications integration ID
  • Node.js v20 or higher

Setup Instructions​

  1. Install @mcp-remote if not already installed:

    npm i mcp-remote

  2. Open Cursor Settings (Cmd/Ctrl + ,)

  3. Add MCP configuration:

Navigate to Cursor's settings.json and add:

{
  "mcpServers": {
    "unizo-comms": {
      "command": "/Users/{user_name}/.nvm/versions/node/v18.x.x/bin/node",
      "args": [
        "/Users/{user_name}/.nvm/versions/node/v18.x.x/bin/mcp-remote",
        "http://api.unizo.ai/mcp/comms",
        "--allow-http",
        "--header",
        "apikey:${UNIZO_API_KEY}"
      ],
      "env": {
        "UNIZO_API_KEY": "your_api_key"
      }
    }
  }
}
  1. Restart Cursor to load the MCP server

Flags: If npx is producing errors, consider adding -y as the first argument to auto-accept the installation of the mcp-remote package.

{
  "mcpServers": {
    "unizo-comms": {
      "command": "/Users/{user_name}/.nvm/versions/node/v18.x.x/bin/node",
      "args": [
        "-y",
        "/Users/{user_name}/.nvm/versions/node/v18.x.x/bin/mcp-remote",
        "http://api.unizo.ai/mcp/comms",
        "--allow-http",
        "--header",
        "apikey:${UNIZO_API_KEY}"
      ],
      "env": {
        "UNIZO_API_KEY": "your_api_key"
      }
    }
  }
}

Available Tools​

Once configured, you'll have access to:

  • list_channels - Browse and search channels across communication platforms
  • send_message - Send messages to channels or direct messages
  • create_channel - Create new channels or conversation spaces
  • list_messages - Retrieve and search message history
  • manage_members - Add or remove members from channels
  • schedule_message - Schedule messages for future delivery

Environment Variables​

You can also set environment variables in your shell profile:

export UNIZO_API_KEY="your_api_key"

Then reference them in settings.json:

{
  "env": {
    "UNIZO_API_KEY": "${env:UNIZO_API_KEY}",
  }
}

Multiple Integrations​

Configure multiple communication platforms:

{
  "mcpServers": {
    "unizo-comms": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://api.unizo.ai/mcp/comms",
        "--allow-http",
        "--header",
        "apikey:${UNIZO_API_KEY}"
      ],
      "env": {
        "UNIZO_API_KEY": "your_api_key"
      }
    },
    "unizo-ticketing": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://api.unizo.ai/mcp/ticketing",
        "--allow-http",
        "--header",
        "apikey:${UNIZO_API_KEY}"
      ],
      "env": {
        "UNIZO_API_KEY": "your_api_key"
      }
    }
  }
}

Troubleshooting​

MCP not detected​

  • Check Cursor's output panel: View → Output → MCP
  • Ensure Node.js v20+ is installed

Authentication errors​

  • Verify your API key in Unizo dashboard
  • Check that the integration ID is correct
  • Ensure the integration is active

Debug mode​

Enable debug logging in settings.json:

{
  "args": [
  "--debug"
]
}