mcpField
B
Bauta

Bauta

Remote
bauta.appCloud & Infra0Updated 16w ago

About Bauta

Bauta is a hosted remote MCP server for publishing HTML and React artifacts from AI clients to share-controlled URLs. It offers tools for deployment and artifact management, with OAuth sign-in and a stdio bridge for clients that need it.

Key features

  1. 01Publish HTML and React artifacts
  2. 02Control sharing and access modes
  3. 03Update or roll back at the same URL
  4. 04Sandbox artifacts in isolated iframes
  5. 05Connect through OAuth 2.1
  6. 06Use a stdio bridge for compatible clients

Use cases

  1. 01Publish an artifact created in an AI client
  2. 02Share a deployment with selected access controls
  3. 03Revise or roll back a published artifact
  4. 04Connect a stdio-only client through `mcp-remote`

MCP support

Bauta exposes deployment and artifact-management tools through a remote MCP server at `https://bauta.app/mcp`, using Streamable HTTP and OAuth 2.1. A stdio bridge is available for clients that do not support remote MCP servers.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://bauta.app/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Bauta connector

Connect your AI client to Bauta — a remote MCP server that deploys HTML/React artifacts from your AI client to hosted, share-gated URLs.

Bauta runs as a hosted remote MCP server. There is nothing to install to use it: point any MCP client at the endpoint below and sign in. This repo is a connect reference and a small stdio bridge for clients that only speak stdio.

Endpoint

https://bauta.app/mcp
  • Transport: Streamable HTTP
  • Auth: OAuth 2.1 — supports both Dynamic Client Registration (DCR) and Client ID Metadata Documents (CIMD)
  • Docs: https://bauta.app/docs

What Bauta does

  • Deploy HTML or React/JSX artifacts to a hosted URL in seconds (JSX is compiled at publish time).
  • Private by default — a new deploy is unlisted (secret-link only); the bare URL is a 404 until you choose to share it.
  • Sharing modes: public, unlisted, password, email verification, or fully private — changed at any time with the set_sharing tool.
  • Updates and rollbacks keep the same URL.
  • Artifacts run in a sandboxed iframe on a separate origin (no cookies, no cross-artifact access).
  • EU data residency (content and metadata in EU-jurisdiction storage).
  • Free tier, no credit card.

Connect

Clients that support remote MCP servers (recommended)

Add the endpoint as a custom connector and complete the OAuth sign-in:

https://bauta.app/mcp
Clients that speak stdio only

Use the mcp-remote bridge:

{
  "mcpServers": {
    "bauta": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://bauta.app/mcp"]
    }
  }
}

The bridge opens a browser once to complete OAuth, then proxies stdio to the hosted server.

Docker

A Dockerfile is included that runs the stdio bridge:

docker build -t bauta-connector .
docker run -it bauta-connector

Tools

Bauta exposes read and write tools kept strictly separate (deploy, update, rollback, rename, set sharing, share via email, bind data source, analytics, export, delete, and more). See https://bauta.app/docs for the full list.

License

MIT — see LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.