General Tools
boathousecloud.com
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://mcp.boathousecloud.com/mcp
MCP server metadata
- Name
- boathouse
- Version
- 0.3
Boathouse is a small cloud: a workspace deploys folder-with-a-Dockerfile tools that become login-protected URLs (https://<tool>.<workspace domain>), shares them by email at three tiers (viewer, editor, admin), keeps their source, secrets, logs and releases, and buys domains. Every tool below acts as the workspace whose project key you send: set the header Authorization: Bearer <project key> on this MCP connection (minted on the workspace's account page, or with `bh keys create`). The server is stateless: no session id, no server-to-client stream. Anything that spends money (domain_buy, topup) quotes first and only acts with confirm true.
Known tools 41
whoamiWho this project key belongs to: the email, the workspace, the domain its tools live on, and the prepaid balance.
Potential side effectslist_toolsEvery tool in the workspace with its state (running/absent), current release, public URL and who can see it.
Inferred read-onlyget_toolOne tool in detail: URL, container state, current release, who it is visible to, and the list of people it has been shared with.
Inferred read-onlypullFetch the exact source folder a release was built from, so you can edit it and deploy it back.
Potential side effectsreleasesThe last 20 releases of a tool: number, status (live/superseded/failed), when, who and the note.
Inferred read-onlyshareGive 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).
Potential side effectsrequest_accessAsk to be let into a tool in someone else's workspace, at viewer, editor or admin.
Inferred read-onlyaccess_requestsEveryone waiting to be let into one of this workspace's tools: request id, email, tier asked for, and their message.
Potential side effectsset_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 shared with.
Inferred read-onlysecrets_listThe names of a tool's secrets (API keys and the like), when each was last set and by whom.
Inferred read-onlyusers_listEveryone in the workspace: role (owner, member or guest), name, and whether they have set a password yet.
Inferred read-onlydomain_checkAsk the registrar whether a domain is free and what it costs per year.
Inferred read-onlydomain_buyBuy a domain through Boathouse's registrar and point it at this box, paid from the workspace's prepaid balance.
Inferred read-onlydomain_renewalsRead domain expiry dates, renewal status, spending limits and billing problems.
Inferred read-onlydomain_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.
Inferred read-onlydomain_pointMake a domain (and its www) open one tool instead of the workspace's tool list.
Inferred read-onlydomain_primaryMake one of the workspace's domains the primary one: the address tool URLs and emails use.
Inferred read-onlydomain_dnsThe DNS records the registrar currently holds for a domain Boathouse bought or manages.
Inferred read-onlydomain_repointRewrite a Boathouse-managed domain's DNS records to point at this Boathouse again (after a move, or if someone changed them).
Inferred read-onlybillingThe 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.
Inferred read-onlypricesWhat Boathouse charges, in plain words: one organization plan for up to five lightweight tools, shared limits, storage, and the domain margin.
Inferred read-onlyreferralThis 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).
Inferred read-onlytopupOpen secure Stripe checkout to add prepaid hosting credit; the owner completes payment there.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.boathouse]
url = "https://mcp.boathousecloud.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"boathouse": {
"type": "http",
"url": "https://mcp.boathousecloud.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: boathouse
Remote MCP URL: https://mcp.boathousecloud.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"boathouse": {
"url": "https://mcp.boathousecloud.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"boathouse": {
"type": "http",
"url": "https://mcp.boathousecloud.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "boathouse",
"transport": "streamable-http",
"url": "https://mcp.boathousecloud.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.