Birta

How to share a Cursor artifact

Cursor renders interactive artifacts next to the chat, and its own link reaches only your team. Connect Birta once and the same artifact reaches people outside Cursor: a client opens it without a Cursor seat, comments right on it, and you ask Cursor for the next version on the same link.

Connect Cursor to Birta

What Cursor gives you today

Next to the chat: an interactive artifact

Cursor draws it in a canvas beside the conversation and keeps it in the workspace’s canvas list. A Cloud Agent keeps its artifacts in the workspace’s artifacts folder, reachable through the API.

Sharing: inside your team

Publish gives teammates a read-only snapshot on Pro, Teams and Enterprise. Free accounts cannot create shares, and there is no public link or domain of yours.

Connect Cursor to Birta once

Bring what Cursor already made into a project your team can open.

  1. 1

    Add Birta to Cursor in one click

    Add to Cursor

    Open the link and confirm the install Cursor offers; it writes the entry itself. You need Node.js 20 or newer.

  2. 2

    Link did not open Cursor? Add it by hand

    Add a Birta entry with the address https://birta.dev/mcp to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json in one. On Enterprise an admin can limit which servers are allowed.

  3. 3

    Ask it for something, then confirm

    The first request comes back with a link. Open it, sign in with a one-time code from your email or with Google, and confirm access. No key to copy.

Then ask Cursor to publish

Copy this into the conversation where Cursor made your artifact.

Cursor

Publish the artifact that is open in this conversation as a page on Birta. Create a project named "Pricing calculator", put it into index.html with its CSS and JavaScript, publish it, and give me the live link. If anything in it needs Cursor to run, tell me what will change first.

  • published, version 1
  • here is the live link: pricing-calculator.birta.link

Share it. Work on it together.

People comment right on the page. Ask Cursor, or any agent you connect, to work through the remarks: the next version lands on the same address.

Same URL after edits

Each change is a new version on the same address. Every version is kept, rollback is one step.

Comments on the page

Colleagues mark remarks on the page itself, no Cursor account needed. You choose who opens it.

A few good questions

Work on it with your team.

Start in the Birta chat, or connect Cursor and any agent your team uses.

Start free

More ways to share agent output