Boat House MCP Server

What the code does

We read the source, 6 d ago · tools taken from the live server · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

        "alpine", ["sh", "-c", "rm -rf /v/* /v/.[!.]* 2>/dev/null; tar xzf /b.tgz -C /v"], remove=True, mem_limit="128m", memswap_limit="128m", nano_cpus=500000000, pids_limit=64,

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.

    out = subprocess.run(["pg_dump", "-h", config.PG_HOST, "-U", "postgres", "--no-owner", "--no-privileges", "--no-tablespaces", name],

here = pathlib.Path(__file__).parent
exec(open(here/'brand_snippets.py').read())

      - /var/run/docker.sock:/var/run/docker.sock

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

claude mcp add boathouse --transport http https://mcp.boathousecloud.com/mcp

https://mcp.boathousecloud.com/mcp

[mcp_servers.boathouse]
url = "https://mcp.boathousecloud.com/mcp"

{
  "mcpServers": {
    "boathouse": {
      "url": "https://mcp.boathousecloud.com/mcp"
    }
  }
}

{
  "servers": {
    "boathouse": {
      "type": "http",
      "url": "https://mcp.boathousecloud.com/mcp"
    }
  }
}

Available tools 41

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Endpoints