Knolo MCP Server

What the code does

We read the source, 10 h ago · rules 995398eba69f

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.

    .map((file) => readFileSync(path.join(import.meta.dirname, file), 'utf8'))

  const result = spawnSync(process.execPath, [script], { stdio: 'inherit' });

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 knolo -e 'KNOLO_MCP_CONFIG=<KNOLO_MCP_CONFIG>' -- npx -y @knolo/mcp

{
  "mcpServers": {
    "knolo": {
      "command": "npx",
      "args": [
        "-y",
        "@knolo/mcp"
      ],
      "env": {
        "KNOLO_MCP_CONFIG": "<KNOLO_MCP_CONFIG>"
      }
    }
  }
}

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

{
  "mcpServers": {
    "knolo": {
      "command": "npx",
      "args": [
        "-y",
        "@knolo/mcp"
      ],
      "env": {
        "KNOLO_MCP_CONFIG": "<KNOLO_MCP_CONFIG>"
      }
    }
  }
}

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

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