com.boathousecloud/boathouse
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
Boat House
Publisher-provided description
Deploy and share small apps with team login, persistent data, versioned updates and domains.
Summary by lookupd
Deploy and manage small web apps with logs, releases, secrets, domains, team access and prepaid billing.
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http boathouse https://mcp.boathousecloud.com/mcp
Codex, remote (streamable-http)
codex mcp add boathouse --url https://mcp.boathousecloud.com/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"boathouse": {
"url": "https://mcp.boathousecloud.com/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (showing 30 of 41)
Publisher-provided text
whoamiWho 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 worksplist_toolsEvery 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 behindget_toolOne tool in detail: URL, container state, current release, who it is visible to, and the list of people it has been shared with.deployDeploy 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 whopullFetch 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 cologsThe tool container's recent log lines, newest last. Use this to find out why a tool is failing.releasesThe 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.rollbackPut 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.restartRestart the tool's container with its current release and current secrets.shareGive 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 theunshareTake away one person's access to one tool. They keep their workspace account.request_accessAsk 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. Taccess_requestsEveryone 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_requestLet 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_accessSet 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 sharedsecrets_listThe names of a tool's secrets (API keys and the like), when each was last set and by whom. Values are never returned.secrets_setSet 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 bacsecrets_deleteRemove one secret from a tool. It disappears on the tool's next restart or deploy.users_listEveryone in the workspace: role (owner, member or guest), name, and whether they have set a password yet.users_addAdd 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 toolsusers_inviteResend an invitation to someone in the workspace. New accounts confirm their mailbox through the emailed link; established accounts receive a normal sign-in URLusers_removeRemove a person from the workspace. Their sessions, project keys, invites and tool grants stop working immediately. Owners only.domains_listThe addresses this workspace answers on: the free <workspace>.boathousecloud.com address, the primary domain, and every custom domain with its DNS state.domain_checkAsk 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 Boathousedomain_buyBuy 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 (costdomain_renewalsRead domain expiry dates, renewal status, spending limits and billing problems. Owners only.domain_renewal_setSet automatic renewal and a maximum prepaid renewal charge. Quote the change first, then require explicit approval with confirm true. Turning renewal off lets tdomain_attachBring 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 podomain_pointMake a domain (and its www) open one tool instead of the workspace's tool list. An empty tool clears it. Owners only.domain_primaryMake one of the workspace's domains the primary one: the address tool URLs and emails use. Owners only.
Details
- Version: 1.0.0
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 265 ms
- First indexed:
- Last seen in registry:
- Repository: https://github.com/allenzhangyiteng/boathouse-cloud
- Website: https://boathousecloud.com
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/com.boathousecloud/boathouse)
- 62033 servers
- Last crawl: 2026-11-11T15:38:39.561Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp