Janee MCP Server

What the code does

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

        fs.writeFileSync(path.join(outDir, "app.json"), JSON.stringify(app, null, 2));

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 scripts/postinstall.js

    const proc = spawn(command[0], command.slice(1), {

      ? path.join(this.secretsDir, prefix)

  for (const agent of fs.readdirSync(APP_BASE)) {

    return Object.keys(process.env)

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 janee -- npx -y @true-and-useful/janee

{
  "mcpServers": {
    "janee": {
      "args": [
        "-y",
        "@true-and-useful/janee"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.janee]
command = "npx"
args = ["-y", "@true-and-useful/janee"]

{
  "mcpServers": {
    "janee": {
      "args": [
        "-y",
        "@true-and-useful/janee"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "janee": {
      "args": [
        "-y",
        "@true-and-useful/janee"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: JANEE_CONFIG (Path to secrets configuration file). The author declared them in the registry entry; get the values from the project itself.