How to share what Cursor builds — as a real link

If you've used Cursor's Composer or Agent mode, you know the feeling: you describe what you want, the AI builds it, you iterate for a few rounds, and suddenly you have something genuinely good running on localhost:3000. A client dashboard. A proposal with live charts. A calculator that actually works.

And then someone asks you to share it.

The localhost problem

Cursor is a code editor. The things it builds are local projects on your machine. That's the right architecture for development, but it means sharing is entirely your problem. Today, most people handle it one of these ways:

• Screenshots. Fast, but the recipient can't click anything. A screenshot of an interactive dashboard is a picture of an interactive dashboard.
• Screen recordings. Better, but now you're narrating a demo instead of letting them explore. And the file is too big for email.
• Zip the project and send it. The recipient needs Node, needs to install dependencies, needs to run a dev server. You've just assigned homework.
• Deploy to Vercel/Netlify/GitHub Pages. A real solution, but a heavy one. You need a repo, a build config, DNS decisions, and a deploy pipeline for what started as "can you show me what that looks like?"

None of these are wrong, but they all convert a five-minute build into a thirty-minute delivery process. The gap between "I made this" and "here, look at this" is wider than it should be.

The fix: MCP

Cursor supports MCP (Model Context Protocol) — an open standard that lets AI agents use external tools. If you've added a linter, a database explorer, or a documentation tool to Cursor via MCP, you already know how this works.

Bauta is an MCP server. Add it to Cursor once, and the agent gains the ability to publish HTML and React to a live URL. The workflow becomes a single sentence in your Composer chat:

That's a real URL. The recipient opens it in any browser. No Cursor, no dev tools, no Node. Just a page.

Setup: two paths

You can add Bauta to Cursor through the settings UI or by editing the MCP config file directly. Both take about a minute.

Path A: Cursor Settings UI

1. Open Cursor Settings and go to the MCP section.
2. Click "Add new MCP server".
3. Set the URL to:

4. Cursor will open a browser window to authorize. Sign in (or create an account — it's the same step) and you're connected.

Path B: manual mcp.json

If you prefer editing config files, add Bauta to your MCP configuration directly:

Save, restart Cursor, and authorize in the browser window that opens.

What happens when you share

When you ask Cursor to share something, the agent calls Bauta's deploy_artifact tool behind the scenes. Here's what that does:

• Your HTML or React gets published to a live URL — something like share.bauta.app/a7x3k. If the project uses JSX, Bauta compiles it at publish time. No build step on your end.
• The link is private by default. It starts as unlisted — only someone who has the exact URL can open it. Nobody can browse to it, search for it, or stumble on it.
• The URL is permanent. It doesn't expire after 30 days. It doesn't vanish when you close Cursor. Update your project and republish — the same URL updates in place, and previous versions stay in history.
• Content runs in a sandbox. Shared pages are served from an isolated domain with sandbox="allow-scripts" and nothing else. They can't access cookies, can't navigate the parent page, can't phone home. Full security details.

Sharing controls

The default — unlisted, link-only access — is fine for most quick shares. But when the context changes, you can adjust visibility without republishing:

• Unlisted. The default. Only people with the secret link can view it. The bare URL returns a 404 to anyone without the token.
• Public. Anyone can open the URL. Good for portfolio pieces, open-source demos, or anything you're actively promoting.
• Password protected. The recipient needs a password you set. Useful for client deliverables where you want a simple access gate.
• Email invite. Share with specific people by email. They verify with a one-time code — no account required on their end. Available on paid plans.
• Private. Fully locked. Nobody can see it except you. Good for pausing access or archiving something you might need later.

You can change the sharing mode at any time, from Cursor or from any other connected MCP client. The URL stays the same.

What you can share

Anything that renders as HTML in a browser. If Cursor built it and it works on localhost, it can become a shareable link. Some common examples:

• Dashboards and reports. Data visualizations, analytics summaries, weekly client reports with live charts.
• Landing pages. Marketing pages, product announcements, event pages — iterate in Cursor, share the result.
• Internal tools. Calculators, configurators, approval workflows, anything your team uses that doesn't justify a full deploy pipeline.
• Client proposals. Interactive proposals with pricing tables, timelines, and embedded demos beat a PDF every time.
• Prototypes and demos. Show a client or stakeholder what you're building, with real interactivity, before committing to a full implementation.
• Mini-apps. Single-page tools, converters, generators — the kind of thing that lives in a single HTML file and does one job well.

Free vs. Pro

Bauta has a free tier that covers casual sharing, and a Pro plan for professional use. Here's the honest breakdown:

If you're sharing personal projects, experiments, or internal demos, the free tier is genuinely sufficient. If the link is going to a client — or if you want the URL to carry your name instead of a random ID — Pro is $20/month, flat.

Works across your whole toolkit

Bauta isn't Cursor-specific. It's a standard MCP server that works with any MCP-compatible client. Once you have an account, you can share from:

• Cursor — the setup we just covered.
• Claude — add as a connector in Claude's settings.
• Claude Code — one command in the terminal.
• Windsurf — same MCP config as Cursor.
• ChatGPT — add as a connector.
• Codex — add to your MCP config.

Same account, same URLs, same sharing controls. Build in whatever tool fits the task; the sharing layer stays the same.

Frequently asked questions