Oe MCP Server

What the code does

We read the source, 5 d ago · rules 995398eba69f

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 });

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.

postinstall: node postinstall.js

пакет @openenterprise/oe-mcp ссылается на enthrium/open-enthrium-ai-mcp-server

const child = spawn(BIN_PATH, process.argv.slice(2), { stdio: "inherit" });

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);

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 -e 'OE_MCP_CONFIG_PATH=<OE_MCP_CONFIG_PATH>' -- npx -y @openenterprise/oe-mcp

{
  "mcpServers": {
    "oe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@openenterprise/oe-mcp"
      ],
      "env": {
        "OE_MCP_CONFIG_PATH": "<OE_MCP_CONFIG_PATH>"
      }
    }
  }
}

[mcp_servers.oe-mcp]
command = "npx"
args = ["-y", "@openenterprise/oe-mcp"]
env = { OE_MCP_CONFIG_PATH = "<OE_MCP_CONFIG_PATH>" }

{
  "mcpServers": {
    "oe-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@openenterprise/oe-mcp"
      ],
      "env": {
        "OE_MCP_CONFIG_PATH": "<OE_MCP_CONFIG_PATH>"
      }
    }
  }
}

{
  "servers": {
    "oe-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@openenterprise/oe-mcp"
      ],
      "env": {
        "OE_MCP_CONFIG_PATH": "<OE_MCP_CONFIG_PATH>"
      }
    }
  }
}

Put your own value in place of <OE_MCP_CONFIG_PATH> (Absolute path to your oe-mcp.yaml config file). The author’s registry entry marks it as required.