List your agent

Boat House

MCP server● Hosted · onlinev1.0.0

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

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: automate CI/CD pipelines.
All AI agents to automate CI/CD pipelines, ranked →

Similar tools

Listed for the same task: automate CI/CD pipelines

Reviews

No review yet. Used Boat House? Be the first to help others choose.

What it does

Boat House is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: devops automation. That makes it a candidate for tasks such as automate CI/CD pipelines or monitor production incidents.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.0
PriceNot in the registry
First seen26 Sept 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://mcp.boathousecloud.com/mcp streamable-http

Required: Authorization (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "boat-house": {
      "url": "https://mcp.boathousecloud.com/mcp",
      "headers": {
        "Authorization": "<your Authorization>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE Boat House answered an MCP connection on 15 Nov 2026 and introduced itself as boathouse 0.3 (MCP protocol 2025-03-26).

41 tools offered to AI assistants

  • 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 first deploy; afterw
  • 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 House emails a secure i
  • 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.
Show 29 more
  • 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 what is explicitly share
  • 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 the account holder's
  • 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 only.
  • 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 the ID on retries. Bet
  • 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 "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://mcp.boathousecloud.com/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Websitehttps://boathousecloud.comDECLAREDSRC-001 Official MCP Registry1d ago
Repositoryhttps://github.com/allenzhangyiteng/boathouse-cloudDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
Version1.0.0DECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Boat House? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor Boat HouseLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Boat House?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/boat-house?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/boat-house/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Boat House

How do I connect Boat House?

Use the hosted endpoint https://mcp.boathousecloud.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does Boat House need an API key or token?

Yes. The registry entry lists a required value: Authorization. Get it from the publisher.

What tools does Boat House offer?

When Electra Index connected on 15 Nov 2026, it listed 41 tools: whoami, list_tools, get_tool, deploy, pull, logs, releases, rollback and more. The full list is in "Live check" above.

Is Boat House online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.

What can I use Boat House for?

Based on its description, it is most relevant to: automate CI/CD pipelines, monitor production incidents.