Llmxray MCP Server

What the code does

We read the source, 13 h 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.

function exec(cmd: string): string {

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.

function exec(cmd: string): string {

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 llmxray -- npx -y llmxray

{
  "mcpServers": {
    "llmxray": {
      "args": [
        "-y",
        "llmxray"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.llmxray]
command = "npx"
args = ["-y", "llmxray"]

{
  "mcpServers": {
    "llmxray": {
      "args": [
        "-y",
        "llmxray"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "llmxray": {
      "args": [
        "-y",
        "llmxray"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: LLMXRAY_URL (The running LLMxRay server the tools read from (start it with `npx llmxray`).), OLLAMA_URL (The Ollama daemon, for the list_local_models tool.). The author declared them in the registry entry; get the values from the project itself.