Vexor MCP Server

What the code does

We read the source, 9 h ago · rules 3dff92dd89df

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.

            completed = subprocess.run(list(command), check=False, timeout=timeout)

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 vexor -- uvx vexor

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

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

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

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

This one needs environment variables set before it will start: VEXOR_API_KEY (Embedding provider API key (optional; overrides a stored key; providers can also be configured via `vexor init`)), VEXOR_REMOTE_RERANK_API_KEY (Remote reranker API key (optional; overrides a stored key; only needed when rerank is set to remote)), VEXOR_CONFIG_JSON (Non-secret Vexor config as a JSON object, e.g. {"provider": "gemini", "rerank": "bm25"} (optional; merged over ~/.vexor/config.json; credential fields are rejected, use the dedicated variables)). The author declared them in the registry entry; get the values from the project itself.