fxray MCP Server

What the code does

We have not read this server's code yet, 31 d ago · rules ccca72095570

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

fxray похож на fray

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

этот файл ставится пользователю, но в репозитории его нет

                    st = yaml.load(text, Loader=_Loader) or {}

        return subprocess.Popen([self.pac_path, *args], stdin=subprocess.DEVNULL, stdout=subprocess.PIPE,

        env = dict(os.environ)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add fxray -- uvx fxray

{
  "mcpServers": {
    "fxray": {
      "command": "uvx",
      "args": [
        "fxray"
      ]
    }
  }
}

[mcp_servers.fxray]
command = "uvx"
args = ["fxray"]

{
  "mcpServers": {
    "fxray": {
      "command": "uvx",
      "args": [
        "fxray"
      ]
    }
  }
}

{
  "servers": {
    "fxray": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "fxray"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: FXRAY_CONFIG (Path to fxray.toml (environment allowlist, write gate, pac path). Optional if the file is in the working folder or the per-user folder), FXRAY_WORKSPACE (Folder whose fxray.toml to use when FXRAY_CONFIG is not set), FXRAY_HOME (Per-user folder (default %LOCALAPPDATA%\fxray on Windows, ~/.config/fxray elsewhere)).