Skip to content

MCP server - quick start

Resilio MCP server enables AI tools to query and manage your Resilio Active Everywhere deployment.

Quick Start

  1. Download and install the MCP server binary for your operating system.

    Windows

    To install MCP Server on Windows, download and run the .msi installer specific to your hardware architecture.

    Binary path for AI tool configuration

    If you used the installer, point your AI tool at this path:
    C:\Users\<YOUR-USERNAME>\AppData\Local\Programs\Resilio MCP Server\resilio-mcp-server.exe

    Replace <YOUR-USERNAME> with your actual Windows username. Use whoami in Command Prompt or PowerShell to confirm it if you're not sure.

    macOS

    To install MCP Server on macOS:

    1. Download and open an image file specific to your hardware architecture (resilio-mcp-osx-arm64.dmg for Apple Silicon, or resilio-mcp-osx-x64.dmg for Intel).

    2. Create a new folder and copy the binary file and the sample configuration file into it:

      • Finder
        In Finder, create a resilio-mcp folder in your home folder, then drag resilio-mcp-server and env.example.txt into it from the open disk image window.

      • Terminal
        In Terminal, run the following commands: 

        mkdir -p ~/resilio-mcp
cp /Volumes/resilio-mcp-osx-arm64/resilio-mcp-server /Volumes/resilio-mcp-osx-arm64/env.example.txt ~/resilio-mcp/

        Note

        On an Intel Mac, change osx-arm64 to osx-x64 in the second line before running it.

    3. In Terminal, run the following command to remove the quarantine attribute from the binary to allow it to run:

      xattr -d com.apple.quarantine ~/resilio-mcp/resilio-mcp-server

    Binary path for AI tool configuration

    If you've set up MCP Server using the suggested binary file location, point your AI tool at this path:
    /Users/<YOUR-USERNAME>/resilio-mcp/resilio-mcp-server

    Replace <YOUR-USERNAME> with your actual macOS username. Use whoami in Terminal to confirm it if you're not sure.

    Linux

    To install MCP Server on Linux:

    1. Download the linux-x64.tar.gz.

    2. Extract the archive: 

      tar xzf resilio-mcp-linux-x64*.tar.gz

    3. Enter the extracted folder: 

      cd resilio-mcp-server

    4. Create a folder for the MCP Server binary: 

      mkdir -p ~/resilio-mcp

    5. Copy the binary and example .env file into the new folder:

      cp resilio-mcp-server env.example.txt ~/resilio-mcp/

    6. Make the binary executable:

      chmod +x ~/resilio-mcp/resilio-mcp-server

    Binary path for AI tool configuration

    If you've set up MCP Server using the suggested binary file location, point your AI tool at this path:
    /home/<YOUR-USERNAME>/resilio-mcp/resilio-mcp-server

    Replace <YOUR-USERNAME> with your actual username. Use whoami in Terminal to confirm it if you're not sure.

  2. Create your API token:

    Important: Use a scoped API token

    Create a dedicated API token in the Management Console with only the permissions you want the AI to have. Don't reuse an admin token.

    1. In the Management Console, go to Settings > API.
    2. Click + Create new token.
    3. Enter description, select admin account that will be tied to this token, and determine permissions, then click Save.
    4. Copy the token value and use it in the next step.

  3. Create the .env credentials file.
    Use the env.example.txt file included with the binary, edit your RESILIO_BASE_URL and RESILIO_API_TOKEN, then rename the file to .env.

    .env file on Windows

    • On Windows, when installed using MSI installer, the env.example.txt file is located in C:\Users\<YOUR-USERNAME>\AppData\Local\Programs\Resilio MCP Server.

    • Rename the file using command line to ensure it's processed correctly by the file system:

      cd /d "%LocalAppData%\Programs\Resilio MCP Server"
ren env.example.txt .env

    .env file on macOS and Linux

    macOS and Linux hide files starting with a dot. To see them:

    • On macOS, in Finder, press Command + Shift + . or use the ls -a command to list them in Terminal.
    • On Linux, in your file manager, enable Show Hidden Files option or use the ls -a command in Terminal.

    Authorization scheme

    By default the token is sent as Authorization: Token <value>. If you use a JWT token with your Management Console, change RESILIO_AUTH_TYPE from Token to Bearer. For details, see Configuration Reference.

    .env file parameters

    The .env file contains other modifiable parameters that are explained in the Configuration Reference section. Make sure that you save the .env file and restart your AI client after making any changes.

  4. Set up your AI tool to connect to the MCP server.
    Resilio's MCP server uses stdio transport, meaning that it runs locally as a subprocess of your AI tool. Each tool reads its MCP configuration from a JSON file. Add the resilio entry shown below.

    Note

    In all examples, replace the path with the absolute path to your binary. Refer to installation instructions for details on where the binary is located based on your operating system and installation method.

    Claude Desktop

    In Claude Desktop, select Settings > Developer > Edit Config to open configuration file location.

    Configuration file location:

    • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows:
      • %LOCALAPPDATA%\Packages\Claude_<id>\LocalCache\Roaming\Claude\claude_desktop_config.json (newer builds)
      • %APPDATA%\Claude\claude_desktop_config.json (older builds)
    • Linux: ~/.config/Claude/claude_desktop_config.json
    {
  "mcpServers": {
    "resilio-active-everywhere": {
      "command": "/path/to/resilio-mcp-server"
    }
  }
}

    On Windows, make sure to use the full MSI install path:

    {
  "mcpServers": {
    "resilio-active-everywhere": {
      "command": "C:\\Users\\<YOUR-USERNAME>\\AppData\\Local\\Programs\\Resilio MCP Server\\resilio-mcp-server.exe"
    }
  }
}
    Claude Code (CLI)

    Run the following command to register a new MCP server to Claude Code's configuration:

    claude mcp add resilio /path/to/resilio-mcp-server --scope user

    Or manually add the following to ~/.claude.json file:

    {
  "mcpServers": {
    "resilio-active-everywhere": {
      "command": "/path/to/resilio-mcp-server"
    }
  }
}

    On Windows, Claude Code runs under WSL, so point it at the .exe through the /mnt/c mount:

    claude mcp add resilio-active-everywhere "/mnt/c/Users/<YOUR-USERNAME>/AppData/Local/Programs/Resilio MCP Server/resilio-mcp-server.exe" --scope user

    Or manually, with type: stdio and the WSL path:

    {
  "mcpServers": {
    "resilio-active-everywhere": {
      "type": "stdio",
      "command": "/mnt/c/Users/<YOUR-USERNAME>/AppData/Local/Programs/Resilio MCP Server/resilio-mcp-server.exe",
      "args": [],
      "env": {}
    }
  }
}
    Cursor

    Configuration file location:

    • Global: ~/.cursor/mcp.json
    • Per-project: .cursor/mcp.json in your project directory
    {
  "mcpServers": {
    "resilio-active-everywhere": {
      "command": "/path/to/resilio-mcp-server"
    }
  }
}
    OpenAI Codex (CLI and IDE extension)

    Configuration file location:

    • Global: ~/.codex/config.toml
    • Per-project: .codex/config.toml in your project directory
    [mcp_servers.resilio-active-everywhere]
command = "/path/to/resilio-mcp-server"

    See the OpenAI Codex MCP docs for the full field reference.

    OpenAI Agents SDK (Python)

    Supported via stdio. Embed the server in your Agent code with MCPServerStdio, pointing command at the binary. See the OpenAI Agents SDK MCP docs.

    Windsurf

    Note

    While Windsurf is now a Cognition/Devin product, the configuration file is still located under the legacy .codeium directory.

    Configuration file location:

    • Mac/Linux: ~/.codeium/windsurf/mcp_config.json
    • Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
    {
  "mcpServers": {
    "resilio-active-everywhere": {
      "command": "/path/to/resilio-mcp-server"
    }
  }
}
    VS Code (Continue extension)

    Install the Continue extension from the VS Code Marketplace and configure the server through it:

    1. Install Continue from the VS Code Marketplace (search Continue in the Extensions panel) and open the Continue sidebar.
    2. In Continue's settings, search for MCP, and choose Add MCP server.
    3. Create .continue/mcpServers/resilio-active-everywhere.yaml in your workspace (or ~/.continue/mcpServers/resilio-active-everywhere.yaml for all workspaces).
    4. Paste the configuration below, replacing /path/to/resilio-mcp-server with your binary path:
    name: Resilio Active Everywhere MCP
version: 0.0.1
schema: v1
mcpServers:
  - name: resilio-active-everywhere
    command: /path/to/resilio-mcp-server

    Note

    MCP tools are available in Agent mode only - they are not exposed in Chat or Plan mode. Switch Continue to Agent mode before using them.

    JetBrains IDEs (IntelliJ, PyCharm, WebStorm, etc.)

    Configure the server through your JetBrains AI client's settings. For the bundled AI Assistant:

    1. Select Settings > Tools > AI Assistant > Model Context Protocol (MCP).
    2. Click Add server (use the "As Command" / manual entry option).
    3. Set the command to your binary path — the one your OS section gave you above.

    Other JetBrains AI plugins expose an equivalent MCP setting inside their own settings panel — configure it the same way.

    Note

    MCP tools require Codebase mode in the AI Assistant chat.

    Google Gemini (CLI only)

    The Gemini desktop and web apps do not support MCP — they can't launch a local stdio server, so they can't connect to this binary. Use the Gemini CLI instead.

    Config file location:

    • Global: ~/.gemini/settings.json
    • Per-project: .gemini/settings.json in your project directory
    {
  "mcpServers": {
    "resilio-active-everywhere": {
      "command": "/path/to/resilio-mcp-server"
    }
  }
}

    Restart the Gemini CLI after saving, then run /mcp inside the CLI to confirm the resilio-active-everywhere server connected and to list its tools.

    ChatGPT Desktop

    Not supported. ChatGPT Desktop requires HTTP endpoints with OAuth authentication — it does not support local stdio MCP servers.

  5. Restart your AI tool.

Configuration Reference

Restart after changes

If you make any changes in the .env file, make sure to restart your AI client after saving the modified configuration for the changes to take effect.

Variable Required Description
RESILIO_BASE_URL Yes Management Console API URL (e.g. https://host:8446).
RESILIO_API_TOKEN Yes API token from the Management Console (Settings > API).
RESILIO_AUTH_TYPE No Authorization scheme for RESILIO_API_TOKEN. Token (default) or Bearer. For details, see Authentication scheme.
RESILIO_TLS_VERIFY No Enable HTTPS certificate validation for the Management Console connection. Defaults to false (accepts the Management Console's self-signed cert).
RESILIO_WRITE_ENABLED No Enable write/mutation tools. Defaults to false.
RESILIO_ANALYTICS_ENABLED No Enable the analytics SQL tools (QueryAnalyticsData, GetAnalyticsSchema), which query the Management Console's public /api/v2/analytics API with your RESILIO_API_TOKEN.
Default:
  • true in Active Everywhere 6.0 and newer.
  • false in Active Everywhere 5.1 and older.
RESILIO_HTTP_ALLOWED_ORIGINS No Comma-separated allowlist of Origin headers for --http mode. For details, see HTTP transport - Origin allowlist.
RESILIO_HTTP_TOKEN_HASH --http only SHA-256 hash of the bearer token required by --http mode. Written by --generate-token; never set by hand. --http refuses to start without it. For more information, see HTTP transport - Setup.
RESILIO_HTTP_IDLE_TIMEOUT No --http session idle timeout in minutes. Default 1440 (24 h). For details, see HTTP transport - Session idle timeout.

Authentication scheme (RESILIO_AUTH_TYPE)

The MCP server authenticates to the Management Console by sending RESILIO_API_TOKEN in the Authorization header. RESILIO_AUTH_TYPE controls the scheme prefix:

Value Header sent When to use
Token (default) Authorization: Token <value> Standard Resilio Management Console API tokens (Settings > API). This is the historical behavior — leave the variable unset and it works.
Bearer Authorization: Bearer <value> Management Console instances that use a JWT token instead of the Token scheme.

Note

The value is case-insensitive (bearer, BEARER, etc. all work). Any value other than Token or Bearer is rejected at startup with an error.