Oe MCP Server

What the code does

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

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

    const output = execSync(cmd, { encoding: "utf8", timeout: 300000 });

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

      const tmpPath = path.join(tmpDir, safeFilename);

    const mcpProc = spawn(process.execPath, args, {

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 oe-mcp -- npx -y @openenthrium/oe-mcp

{
  "mcpServers": {
    "oe-mcp": {
      "args": [
        "-y",
        "@openenthrium/oe-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.oe-mcp]
command = "npx"
args = ["-y", "@openenthrium/oe-mcp"]

{
  "mcpServers": {
    "oe-mcp": {
      "args": [
        "-y",
        "@openenthrium/oe-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "oe-mcp": {
      "args": [
        "-y",
        "@openenthrium/oe-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: OE_MCP_CONFIG_PATH (Absolute path to your oe-mcp.json config file). The author declared them in the registry entry; get the values from the project itself.