Skip to content

MCP server - troubleshooting

Troubleshooting

  • Tools appear in your AI client, but every tool call fails
    The server connected fine (listing tools needs no Management Console), but the calls can't reach the Management Console — almost always because your .env isn't being loaded, so RESILIO_BASE_URL / RESILIO_API_TOKEN are unset and the call throws before any request goes out. Check tool-calls.log — usually %LOCALAPPDATA%\Resilio MCP\ on Windows, ~/Library/Application Support/Resilio MCP/ on macOS, ~/.local/share/Resilio MCP/ on Linux. (On Windows, if your client is a sandboxed/MSIX app like Claude Desktop, the server's writes are redirected into that app's container instead — e.g. …\AppData\Local\Packages\Claude_<id>\LocalCache\Local\Resilio MCP\tool-calls.log; if it's not in the usual spot, find it with Get-ChildItem $env:LOCALAPPDATA -Recurse -Filter tool-calls.log.) If the log shows only startup banners and no GET/POST lines, the .env never loaded. The usual cause is a misnamed file: confirm it's named exactly .env — not .env.txt or still env.example.txt — and sits next to the binary (or in your per-user data folder). On Windows this is exactly why the install steps create it with the ren command instead of File Explorer.

  • Tool calls failing unexpectedly — especially ones with numeric or boolean filters (limit, online, active, etc.)
    Some AI clients send an empty string ("") or whitespace for optional parameters the model didn't fill in, instead of leaving them out. The server can't convert "" into a number or boolean, so the call fails before it runs. If you see unexplained tool-call failures, tell your AI to omit optional parameters it doesn't need, or pass null — never an empty string or whitespace. The server's built-in instructions already ask for this, but repeating it in your own prompt/system message helps.

Known issues and limitations

The self-contained binaries bundle their own .NET runtime. This bundled runtime has a known issue reaching hosts on Parallels Desktop virtual network adapters (e.g. 10.211.55.x addresses). If your Management Console runs inside a Parallels VM on the same machine, use dotnet run (which uses the system .NET runtime) instead of the pre-built binary. This does not affect normal network configurations — customers connecting to an Management Console on a standard network address will not encounter this issue.