mcpbeat Sign in

Boat House MCP Server

by boathousecloud Your server? Claim it
answering

Boat House is answering right now. Last checked 11 min ago. It exposes 41 tools. Last commit 18 Sep 2026.

Deploy and share small apps with team login, persistent data, versioned updates and domains.

Uptime history 22 hours of history
22 hours agonow
100.0%
Uptime 24h
83 of 83 checks
41
Tools
read from the server
394 ms
Response time
average over 24h
1
Stars
last commit 18 Sep 2026

What the code does

We read the source, 25 min ago · tools taken from the live server · rules 3dff92dd89df

Evidence

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.

Deletes files or strips permissions control/app/restore.py:84
        "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,
Capabilities

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],
Executes code built at runtime control/site/src/build.py:5
here = pathlib.Path(__file__).parent
exec(open(here/'brand_snippets.py').read())
Asks for container control access docker-compose.yml:26
      - /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.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Boat House and you get told the day something new turns up.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add boathouse --transport http https://mcp.boathousecloud.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "boathouse": {
      "url": "https://mcp.boathousecloud.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.boathouse]
url = "https://mcp.boathousecloud.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "boathouse": {
      "url": "https://mcp.boathousecloud.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "boathouse": {
      "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.

domain
domain_attach
Bring a domain the workspace already owns elsewhere: Boathouse starts answering on it and returns the DNS records to make at the current DNS host. Optionally point it at one tool at the same time. Owners only.
domain_buy
Buy a domain through Boathouse's registrar and point it at this box, paid from the workspace's prepaid balance. Without confirm it only returns the quote (cost now, renewal price, your balance) and buys nothing. Owners only.
domain_check
Ask the registrar whether a domain is free and what it costs per year. Buys nothing. total_cents is the price the workspace pays (registrar_cents plus Boathouse's margin_cents); show that one.
domain_detach
Stop serving a domain. The registration itself is untouched and domain_attach brings it back. Owners only.
domain_dns
The DNS records the registrar currently holds for a domain Boathouse bought or manages. Changes nothing.
domain_point
Make a domain (and its www) open one tool instead of the workspace's tool list. An empty tool clears it. Owners only.
domain_primary
Make one of the workspace's domains the primary one: the address tool URLs and emails use. Owners only.
domain_renewal_set
Set automatic renewal and a maximum prepaid renewal charge. Quote the change first, then require explicit approval with confirm true. Turning renewal off lets the domain expire. Owners only.
domain_renewals
Read domain expiry dates, renewal status, spending limits and billing problems. Owners only.
domain_repoint
Rewrite a Boathouse-managed domain's DNS records to point at this Boathouse again (after a move, or if someone changed them). Owners only.
users
users_add
Add a person to the workspace, or change their role. owner = may spend money, buy domains and manage people, and is admin on every tool; member = may see tools open to members and deploy their own; guest = sees only what is explicitly shared with them. Returns a one-time invite link for someone new. Owners only.
users_invite
Resend an invitation to someone in the workspace. New accounts confirm their mailbox through the emailed link; established accounts receive a normal sign-in URL. Password recovery is self-service on that page, and only the account holder's mailbox receives a reset link. Check emailed before offering a fallback.
users_list
Everyone in the workspace: role (owner, member or guest), name, and whether they have set a password yet.
users_remove
Remove a person from the workspace. Their sessions, project keys, invites and tool grants stop working immediately. Owners only.
secrets
secrets_delete
Remove one secret from a tool. It disappears on the tool's next restart or deploy.
secrets_list
The names of a tool's secrets (API keys and the like), when each was last set and by whom. Values are never returned.
secrets_set
Set one secret on a tool. It is injected as an environment variable of that name and the tool is restarted. Names are UPPER_SNAKE_CASE. Never echo the value back to the user.
access
access_requests
Everyone waiting to be let into one of this workspace's tools: request id, email, tier asked for, and their message. Owners and tool admins.
set_access
Set who a tool is open to by default: 'members' means anyone in the workspace (at the given tier), 'listed' means only the people it has been explicitly shared with. Use 'listed' for anything sensitive.
tool
delete_tool
Delete a tool: its container, its releases and its sharing. By default the tool's database and files are kept. purge true also destroys them forever, and then requires purge_confirm true as well.
get_tool
One tool in detail: URL, container state, current release, who it is visible to, and the list of people it has been shared with.
allow
allow_request
Let a waiting person in at the tier they asked for. Their tool grant is made and they get an email saying what to do next. Owners and tool admins.
billing
billing
The workspace's money: prepaid balance, whether it is paused, how fast running tools burn credit, how many days are left, whether a card is on file, and the last ledger lines.
capacity
capacity
Quote additional app storage. Show the maximum extra monthly price and get owner approval before confirming. No automatic upgrade. Owners only.
card
card_link
A one-time link where a workspace owner types a card into Stripe. This is the only part of Boathouse that needs a browser. Owners only.
deploy
deploy
Deploy a folder as a tool and make it live at https://<tool>.<workspace domain>. Send the whole folder in `files`, which MUST include a top-level Dockerfile whose process listens on $PORT (8080). Creates the tool on the first deploy; afterwards it replaces the running container. If you got these files from `pull`, pass the release number you pulled as `base` so a deploy someone else made in the meantime is not silently overwritten.
domains
domains_list
The addresses this workspace answers on: the free <workspace>.boathousecloud.com address, the primary domain, and every custom domain with its DNS state.
logs
logs
The tool container's recent log lines, newest last. Use this to find out why a tool is failing.
prices
prices
What Boathouse charges, in plain words: one organization plan for up to five lightweight tools, shared limits, storage, and the domain margin.
pull
pull
Fetch the exact source folder a release was built from, so you can edit it and deploy it back. Returns the release number and the files as text (binary files come back base64 encoded). Tool admins only.
referral
referral
This person's referral code and link, the deal in words, and what each referred workspace has earned them so far (10% of usage charges, paid monthly in cash).
releases
releases
The last 20 releases of a tool: number, status (live/superseded/failed), when, who and the note. A failed release shows the last line of its build log.
request
request_access
Ask to be let into a tool in someone else's workspace, at viewer, editor or admin. Its owners get an email with one Allow button; nobody there runs a command. The person is emailed when it is allowed.
restart
restart
Restart the tool's container with its current release and current secrets.
rollback
rollback
Put an earlier release back in service. With no `to`, goes back to the release before the live one. This rolls back the software, never the database.
share
share
Give one person access to one tool by email, at a tier: viewer (read only; the gateway blocks their writes), editor (may change the data), admin (may change the software, secrets, sharing). If the person is new, Boat House emails a secure invitation when email is configured. Check emailed in the result; if delivery failed, share the invitation page so the person can request their secure email.
tools
list_tools
Every tool in the workspace with its state (running/absent), current release, public URL and who can see it. A 'tool' is one small web app Boathouse runs behind the workspace login.
topup
topup
Open secure Stripe checkout to add prepaid hosting credit; the owner completes payment there. Without confirm it only quotes and returns operation_id. Confirm the same cents and operation_id after user approval; reuse the ID on retries. Between $5.00 (500) and $1,000.00 (100000). Owners only.
unshare
unshare
Take away one person's access to one tool. They keep their workspace account.
usage
usage
Check storage, memory, CPU and the reason an app is paused. Tool admins only.
whoami
whoami
Who this project key belongs to: the email, the workspace, the domain its tools live on, and the prepaid balance. Call it first if you are not sure which workspace you are acting in.

Endpoints

URLTransportStateLatencyChecked
https://mcp.boathousecloud.com/mcp streamable-http answering 392 ms 11 min ago

Alternatives to Boat House

same job, measured the same way
Layero
by layero

Deploy and operate sites on Layero — hosting with build servers in Russia: domains, env, Data API.

34 tools answering
agenthost
by agenthost

Agent-first web hosting: deploy sites, apps, databases and domains over MCP.

answering
CLI
by settlemesh

Deploy and monetize agent-built apps: login, database, usage billing, and end-user-pays.

278 installs/wk local only
Softkiln Deploy
by softkiln

Host apps built with AI: deploy to a live HTTPS URL, custom domains, secrets and backups.

answering
Croft
by oncroft

Deploy and host the apps your AI assistant builds — a real server, database, and shareable URL.

26 tools answering
Floom
by floomhq

Deploy Python functions as web apps with auto-generated UI, REST API, and shareable links.

26 installs/wk local only
Agentbuilders
by deepfreezechill

Deploy full-stack AI agent apps with database, auth, storage, and Edge AI on one platform.

38 installs/wk local only
Sota
by sota-deploy

Deploy web apps via AI agents with sota.io. 9 tools for deploy, logs, env, and more.

local only

Boat House — questions

Answers built from our own checks of this server.

What can Boat House do?
It exposes 41 tools, read directly from the server on our last check. Among them: access_requests, allow_request, billing, capacity, card_link, delete_tool and 35 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Boat House mostly used for?
Its tools cluster around domain, users and secrets. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Boat House working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 83 of 83 checks got a reply (100.0%), average response time 394 ms. The bar chart above shows every period we have measured.
How do I connect Boat House?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Boat House need an API key?
No. Boat House completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 41 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Boat House?
It answers our handshake in 394 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Boat House open source?
Yes — it is published under the Apache-2.0 licence, written in Python and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.