Boat House by boathousecloud.com
MCP server · Cloud & infrastructure · indexed, not reviewed
Hostedvendor's own
Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
Deploy and share small apps with team login, persistent data, versioned updates and domains.
Facts
- MCP registry
com.boathousecloud/boathouse· 1.0.0- Endpoint
https://mcp.boathousecloud.com/mcp- Website
- boathousecloud.com
- GitHub stars
- 1
- Registry entry
- updated 17 Sep 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under boathousecloud.com, a namespace the registry only gives to whoever proves they control that domain.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 41 · about 6,136 tokens of context · checked 3 hours ago
| Tool | What it does | Hint |
|---|---|---|
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. | |
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. | |
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. | |
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… | |
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. | |
logs | The tool container's recent log lines, newest last. Use this to find out why a tool is failing. | |
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. | |
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. | |
restart | Restart the tool's container with its current release and current secrets. | |
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… | |
unshare | Take away one person's access to one tool. They keep their workspace account. | |
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. | |
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. | |
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. | |
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. | |
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. | |
secrets_delete | Remove one secret from a tool. It disappears on the tool's next restart or deploy. | |
users_list | Everyone in the workspace: role (owner, member or guest), name, and whether they have set a password yet. | |
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… | |
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… | |
users_remove | Remove a person from the workspace. Their sessions, project keys, invites and tool grants stop working immediately. Owners only. | |
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. | |
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_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… | |
domain_renewals | Read domain expiry dates, renewal status, spending limits and billing problems. 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_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_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_dns | The DNS records the registrar currently holds for a domain Boathouse bought or manages. Changes nothing. | |
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. | |
domain_detach | Stop serving a domain. The registration itself is untouched and domain_attach brings it back. Owners only. | |
usage | Check storage, memory, CPU and the reason an app is paused. Tool admins only. | |
capacity | Quote additional app storage. Show the maximum extra monthly price and get owner approval before confirming. No automatic upgrade. Owners only. | |
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. | |
prices | What Boathouse charges, in plain words: one organization plan for up to five lightweight tools, shared limits, storage, and the domain margin. | |
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). | |
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… | |
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. | |
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. |
What https://mcp.boathousecloud.com/mcp answered to tools/list, asked without credentials. answered without the initialize handshake. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 42 warnings · 1 note
- warnTC16access_requestsno readOnlyHint or destructiveHint
- warnTC16allow_requestno readOnlyHint or destructiveHint
- warnTC16billingno readOnlyHint or destructiveHint
- warnTC16capacityno readOnlyHint or destructiveHint
- warnTC16card_linkno readOnlyHint or destructiveHint
- warnTC16delete_toolno readOnlyHint or destructiveHint
- warnTC16deployno readOnlyHint or destructiveHint
- warnTC16domain_attachno readOnlyHint or destructiveHint
- warnTC16domain_buyno readOnlyHint or destructiveHint
- warnTC16domain_checkno readOnlyHint or destructiveHint
- warnTC16domain_detachno readOnlyHint or destructiveHint
- warnTC16domain_dnsno readOnlyHint or destructiveHint
- warnTC16domain_pointno readOnlyHint or destructiveHint
- warnTC16domain_primaryno readOnlyHint or destructiveHint
- warnTC16domain_renewal_setno readOnlyHint or destructiveHint
- warnTC16domain_renewalsno readOnlyHint or destructiveHint
- warnTC16domain_repointno readOnlyHint or destructiveHint
- warnTC16domains_listno readOnlyHint or destructiveHint
- warnTC16get_toolno readOnlyHint or destructiveHint
- warnTC16list_toolsno readOnlyHint or destructiveHint
- warnTC16logsno readOnlyHint or destructiveHint
- warnTC16pricesno readOnlyHint or destructiveHint
- warnTC16pullno readOnlyHint or destructiveHint
- warnTC16referralno readOnlyHint or destructiveHint
The first 24 of 43; every finding is in the listing's JSON under mcpTools.check.
The checks from /check and anchor check, run each day on the list above: about 6,136 tokens of definitions. Not part of the score yet. Check your own server.