Index / MCP servers / Boat House

Boat House MCP server

Connect Boat House and your agent gets 41 tools, among them access_requests, allow_request, billing. It answers at https://mcp.boathousecloud.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 3 of 3 times since 20 September 2026; the last check, on 12 October 2026, succeeded.

Status
Answering
Tools
41
Official
yes, served from boathousecloud.com
Reliability
3 of 3 checks
Response time
349 ms
Transport
streamable HTTP
Last checked
12 October 2026

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

Description as the publisher wrote it.

The 41 tools Boat House offers

ToolWhat it does
access_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.
Inputs: workspace
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.
Inputs: workspace, id
billingThe 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.
Inputs: workspace
capacityQuote additional app storage. Show the maximum extra monthly price and get owner approval before confirming. No automatic upgrade. Owners only.
Inputs: workspace, tool, storage_gb, confirm, quote_id, max_extra_monthly_cents
card_linkA 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.
Inputs: workspace
delete_toolDelete 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.
Inputs: workspace, tool, purge, purge_confirm
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 whose process listens on $PORT (8080). Creates the tool on the first deploy; afterw
Inputs: workspace, tool, files, base64, name, note
domain_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 point it at one tool at the same time. Owners only.
Inputs: workspace, domain, tool
domain_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 (cost now, renewal price, your balance) and buys nothing. Owners only.
Inputs: workspace, domain, confirm, quote_id, max_cost_cents
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 Boathouse's margin_cents); show that one.
Inputs: workspace, domain
domain_detachStop serving a domain. The registration itself is untouched and domain_attach brings it back. Owners only.
Inputs: workspace, domain
domain_dnsThe DNS records the registrar currently holds for a domain Boathouse bought or manages. Changes nothing.
Inputs: workspace, domain
domain_pointMake a domain (and its www) open one tool instead of the workspace's tool list. An empty tool clears it. Owners only.
Inputs: workspace, domain, tool
domain_primaryMake one of the workspace's domains the primary one: the address tool URLs and emails use. Owners only.
Inputs: workspace, domain
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 the domain expire. Owners only.
Inputs: workspace, domain, enabled, max_cost_cents, confirm
domain_renewalsRead domain expiry dates, renewal status, spending limits and billing problems. Owners only.
Inputs: workspace
domain_repointRewrite a Boathouse-managed domain's DNS records to point at this Boathouse again (after a move, or if someone changed them). Owners only.
Inputs: workspace, domain
domains_listThe addresses this workspace answers on: the free <workspace>.boathousecloud.com address, the primary domain, and every custom domain with its DNS state.
Inputs: workspace
get_toolOne tool in detail: URL, container state, current release, who it is visible to, and the list of people it has been shared with.
Inputs: workspace, tool
list_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 behind the workspace login.
Inputs: workspace
logsThe tool container's recent log lines, newest last. Use this to find out why a tool is failing.
Inputs: workspace, tool, tail, since
pricesWhat Boathouse charges, in plain words: one organization plan for up to five lightweight tools, shared limits, storage, and the domain margin.
Inputs: workspace
pullFetch 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.
Inputs: workspace, tool, release
referralThis 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).
Inputs: workspace
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.
Inputs: workspace, tool
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. The person is emailed when it is allowed.
Inputs: workspace, target, tier, message
restartRestart the tool's container with its current release and current secrets.
Inputs: workspace, tool
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.
Inputs: workspace, tool, to
secrets_deleteRemove one secret from a tool. It disappears on the tool's next restart or deploy.
Inputs: workspace, tool, name
secrets_listThe names of a tool's secrets (API keys and the like), when each was last set and by whom. Values are never returned.
Inputs: workspace, tool
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 back to the user.
Inputs: workspace, tool, name, value
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 shared with. Use 'listed' for anything sensitive.
Inputs: workspace, tool, mode, tier
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 the software, secrets, sharing). If the person is new, Boat House emails a secure i
Inputs: workspace, tool, email, tier, labels
topupOpen 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. Bet
Inputs: workspace, cents, confirm, operation_id
unshareTake away one person's access to one tool. They keep their workspace account.
Inputs: workspace, tool, email
usageCheck storage, memory, CPU and the reason an app is paused. Tool admins only.
Inputs: workspace, tool
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 tools open to members and deploy their own; guest = sees only what is explicitly share
Inputs: workspace, email, role
users_inviteResend 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
Inputs: workspace, email
users_listEveryone in the workspace: role (owner, member or guest), name, and whether they have set a password yet.
Inputs: workspace
users_removeRemove a person from the workspace. Their sessions, project keys, invites and tool grants stop working immediately. Owners only.
Inputs: workspace, email
1 more tools

whoami

Add Boat House to your AI client

Every block below points at https://mcp.boathousecloud.com/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http boat-house https://mcp.boathousecloud.com/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "boat-house": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.boathousecloud.com/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "boat-house": {
      "url": "https://mcp.boathousecloud.com/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "boat-house": {
      "type": "http",
      "url": "https://mcp.boathousecloud.com/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "boat-house": {
      "url": "https://mcp.boathousecloud.com/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "boat-house": {
      "serverUrl": "https://mcp.boathousecloud.com/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "boat-house": {
      "url": "https://mcp.boathousecloud.com/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Boat House
version: 0.0.1
schema: v1
mcpServers:
  - name: Boat House
    type: streamable-http
    url: https://mcp.boathousecloud.com/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "boat-house": {
      "httpUrl": "https://mcp.boathousecloud.com/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "boat-house": {
      "type": "http",
      "url": "https://mcp.boathousecloud.com/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "boat-house": {
      "url": "https://mcp.boathousecloud.com/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fmcp.boathousecloud.com%2Fmcp&type=streamable_http&id=boat-house&name=Boat%20House

Is Boat House up right now?

It answered our last check on 12 October 2026 in 349 ms. Over 3 checks since 20 September 2026 it answered 3. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Boat House

Questions about Boat House

Is there an official Boat House MCP server?

Yes. It is published by boathousecloud.com and served from mcp.boathousecloud.com, the vendor's own domain: https://mcp.boathousecloud.com/mcp.

How many tools does Boat House have?

41, as returned by the server's own tools/list on 20 October 2026: access_requests, allow_request, billing, capacity, card_link, delete_tool, deploy, domain_attach, and 33 more.

Is Boat House down?

It answered our last check on 12 October 2026 in 349 ms. Over 3 checks since 20 September 2026 it answered 3.

How do I add Boat House to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.boathousecloud.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Boat House need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: com.boathousecloud. Endpoint host: mcp.boathousecloud.com. ARD identifier: urn:air:com.boathousecloud:mcp:boathouse. First indexed 17 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.