MCP.Market

Boat House MCP server

online · 100% uptime
by boathousecloud.com·com.boathousecloud/boathouse·v1.0.0·1 stars
No reviews yet

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

A88/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

1 stars

Reviews

Write one

Nobody has reviewed Boat House yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Boat House tools (41, 6 write)

write = sends, deletes, buys or posts
  • access_requestsFree

    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_requestFree

    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.

  • billingFree

    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.

  • capacityFree

    Quote additional app storage. Show the maximum extra monthly price and get owner approval before confirming. No automatic upgrade. Owners only.

  • card_linkFree

    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_toolwrite actionFree

    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.

  • deploywrite actionFree

    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.

  • domain_attachFree

    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_buywrite actionFree

    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_checkFree

    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_detachFree

    Stop serving a domain. The registration itself is untouched and domain_attach brings it back. Owners only.

  • domain_dnsFree

    The DNS records the registrar currently holds for a domain Boathouse bought or manages. Changes nothing.

  • domain_pointFree

    Make a domain (and its www) open one tool instead of the workspace's tool list. An empty tool clears it. Owners only.

  • domain_primaryFree

    Make one of the workspace's domains the primary one: the address tool URLs and emails use. Owners only.

  • domain_renewal_setFree

    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_renewalsFree

    Read domain expiry dates, renewal status, spending limits and billing problems. Owners only.

  • domain_repointFree

    Rewrite a Boathouse-managed domain's DNS records to point at this Boathouse again (after a move, or if someone changed them). Owners only.

  • domains_listFree

    The addresses this workspace answers on: the free <workspace>.boathousecloud.com address, the primary domain, and every custom domain with its DNS state.

  • get_toolFree

    One tool in detail: URL, container state, current release, who it is visible to, and the list of people it has been shared with.

  • list_toolsFree

    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.

  • logsFree

    The tool container's recent log lines, newest last. Use this to find out why a tool is failing.

  • pricesFree

    What Boathouse charges, in plain words: one organization plan for up to five lightweight tools, shared limits, storage, and the domain margin.

  • pullFree

    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.

  • referralFree

    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).

  • releasesFree

    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_accessFree

    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.

  • restartFree

    Restart the tool's container with its current release and current secrets.

  • rollbackwrite actionFree

    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.

  • secrets_deletewrite actionFree

    Remove one secret from a tool. It disappears on the tool's next restart or deploy.

  • secrets_listFree

    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_setFree

    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.

  • set_accessFree

    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.

  • shareFree

    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.

  • topupFree

    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.

  • unshareFree

    Take away one person's access to one tool. They keep their workspace account.

  • usageFree

    Check storage, memory, CPU and the reason an app is paused. Tool admins only.

  • users_addFree

    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_inviteFree

    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_listFree

    Everyone in the workspace: role (owner, member or guest), name, and whether they have set a password yet.

  • users_removewrite actionFree

    Remove a person from the workspace. Their sessions, project keys, invites and tool grants stop working immediately. Owners only.

  • whoamiFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 154ms20/20
  • Tool poisoning41 tool descriptions checked15/15
  • Auth qualityAPI key sent as a header8/15
  • Maintenancelast push 8 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Boat House compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 1,119 Developer tools servers
Tools
41
the typical Developer tools server has 7
Tools that change things
15%
typical: 5%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote Developer tools server answers 100%
Response time
329 ms
faster than 37% of 443 Developer tools servers
GitHub stars
1
more than 50% of 855 Developer tools servers

What its tools let an agent do: 32 read · 5 change · 1 delete · 1 send or post · 2 run or deploy

Install Boat House in Claude Code, Cursor or VS Code

claude mcp add --transport http boathouse https://mcp.boathousecloud.com/mcp
Add to Cursor

What the publisher says

From the Boat House repository's README, as published. We do not edit it. Read it on GitHub

Boat House

Open-source infrastructure for small software built with AI agents.

Boat House gives a tool a live HTTPS address, sign-in, a database, persistent files, and sharing by email. Editors use the app in a browser. Developers with Admin access can use their own agents to fetch its source and publish versioned updates to the same address.

The software is licensed under Apache 2.0. You can run it on your own infrastructure or use Boat House managed hosting.

What is included

  • A FastAPI control plane and Caddy HTTPS gateway.
  • Account sign-in, email invitations, per-tool Viewer / Editor / Admin access, and signed identity passed to apps.
  • Per-tool PostgreSQL databases, persistent file volumes, container resource limits, and saved source releases.
  • Deployment, source checkout, updates, rollback, export, and backup/restore commands.
  • The bh CLI, an MCP endpoint, and an agent skill for Claude Code, Codex and other compatible agents.
  • Optional email, domain registration, and prepaid billing integrations. Self-hosters configure their own providers; metering can be disabled.

Admin is full control of a tool, including its source, secrets, sharing and deletion. Software collaboration uses source checkout and versioned publication. App code enforces its own record-level access rules.

Start with managed hosting

Create an account at boathousecloud.com, confirm your email, then choose Copy connection and paste the message into your coding agent. Ask it to put a tool online or share it by email. Add credit before deploying. No separate hosting, database or sign-in project is needed.

Install the agent skill in Cursor, Codex or Windsurf:

npx skills add allenzhangyiteng/boathouse-skills

For Claude Code, add /plugin marketplace add allenzhangyiteng/boathouse-skills, then /plugin install boathouse@boathouse. See the skill and plugin repository and installation guide.

The CLI can create a working app before you connect an account:

bh init my-app --template team
cd my-app
python3 app.py --local

Use --template static for an HTML website. boathouse is an alias installed alongside bh when available. The starter format is ordinary source plus boathouse.json; no proprietary runtime is needed. See the runnable guides, llms.txt and complete agent docs.

Run your own installation

See the self-hosting guide for a Linux host with Docker, DNS and HTTPS. The public release contains no accounts, credentials, database snapshots, hosted customer tools or production configuration. All examples use placeholders; generate your own secrets.

This is infrastructure for trusted teams and trusted app builders. The control plane manages the host Docker daemon. Resource limits and container networks do not make it a secure sandbox for hostile code. Read the security model before exposing an installation.

Development

Python 3.12 is used by the container image. In a virtual environment:

python -m pip install -r control/requirements.txt -r requirements-dev.txt
python -m pytest -q
python scripts/check_public_tree.py

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Boat House: common questions

Is Boat House MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Boat House safety report
How do I install Boat House?
It runs remotely at mcp.boathousecloud.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Boat House need an API key?
Yes. The registry entry asks for Authorization.
Is Boat House maintained?
The last commit was 40 days ago (2026-09-24). The latest release is v1.0.0.
Is Boat House up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Boat House?
Servers from other publishers that do the same job: Aiven MCP server, Dockhold MCP server and walkerOS Flow MCP server.
How does Boat House compare with other Developer tools MCP servers?
safety score 88/100 (higher than 75% of 1,119 Developer tools servers); tools 41 (the typical Developer tools server has 7); tools that change things 15% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Boat House

Same job from other publishers: the closest match first, then the best rated.

  • Aiven MCP
    Provision PostgreSQL, manage Apache Kafka, and deploy apps with Aiven - all from your AI assistant.
    A
  • Dockhold
    Deploy your project to a live HTTPS URL from your AI tool; read logs, set variables, resize apps.
    A
  • walkerOS Flow
    Build, validate, simulate, and deploy walkerOS event pipelines
    B
  • Omnara
    Deploy durable AI agents with Omnara, an open-source managed-agent platform.
    A
  • Porkbun (official)
    Official Porkbun MCP server: domains, DNS, SSL, hosting and Cloudflare via the Porkbun API.
    A