Codexa MCP Server

What the code does

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

      const child = spawn(command.spawnExecutable, command.spawnArgs, {

  const lockDir = path.isAbsolute(options.lockDir) ? options.lockDir : path.join(repoRoot, options.lockDir);

  await fs.writeFile(path.join(home, ".npmrc"), "", "utf8");

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 codexa -- npx -y @mirnoorata/codexa

{
  "mcpServers": {
    "codexa": {
      "args": [
        "-y",
        "@mirnoorata/codexa"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.codexa]
command = "npx"
args = ["-y", "@mirnoorata/codexa"]

{
  "mcpServers": {
    "codexa": {
      "args": [
        "-y",
        "@mirnoorata/codexa"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "codexa": {
      "args": [
        "-y",
        "@mirnoorata/codexa"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: CODEXA_MCP_STRUCTURED_BUDGET_BYTES (Optional structured-result byte budget override for hosts with small MCP result limits.). The author declared them in the registry entry; get the values from the project itself.