Hybrid Recursive Ladder MCP Server

What the code does

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

        subprocess.run(

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 hybrid-recursive-ladder -- uvx hybrid-recursive-ladder-mcp

{
  "mcpServers": {
    "hybrid-recursive-ladder": {
      "command": "uvx",
      "args": [
        "hybrid-recursive-ladder-mcp"
      ]
    }
  }
}

[mcp_servers.hybrid-recursive-ladder]
command = "uvx"
args = ["hybrid-recursive-ladder-mcp"]

{
  "mcpServers": {
    "hybrid-recursive-ladder": {
      "command": "uvx",
      "args": [
        "hybrid-recursive-ladder-mcp"
      ]
    }
  }
}

{
  "servers": {
    "hybrid-recursive-ladder": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "hybrid-recursive-ladder-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: HL_SOURCE (Source backend: demo (default), thingsboard, or postgres), HL_TB_URL (ThingsBoard base URL, for example http://localhost:9090), HL_TB_USERNAME (ThingsBoard username; pair with HL_TB_PASSWORD), HL_TB_PASSWORD (ThingsBoard password), HL_TB_TOKEN (ThingsBoard access token, used instead of username and password), HL_PG_DSN (PostgreSQL DSN for the local materialized store), HL_TIMEZONE (IANA timezone for calendar boundaries; default Asia/Shanghai), HL_FINEST (Finest ladder level: minute, hour, day, or month).