Oss Autopilot MCP Server

What the code does

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

  execFile(openCmd, args, (error) => {

    const candidate = path.join(dir, claudePath);

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 oss-autopilot -- npx -y @oss-autopilot/mcp

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

[mcp_servers.oss-autopilot]
command = "npx"
args = ["-y", "@oss-autopilot/mcp"]

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

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

This one needs environment variables set before it will start: GITHUB_TOKEN (GitHub personal access token or token from `gh auth token`). The author declared them in the registry entry; get the values from the project itself.