How to Share a Claude Artifact with Your Team

You just built something great in Claude. Maybe it’s a project tracker, a calculator for your team’s commission splits, or an interactive chart that finally makes sense of that messy spreadsheet. Claude’s artifact panel shows it working perfectly — right there in your chat window.

Now you want to share it with someone.

And that’s where it gets weird.

The sharing problem

Claude artifacts are powerful, but they’re stuck. Right now, your options for getting that app in front of someone else look like this:

Share the conversation. Claude lets you publish artifacts, but the person you’re sharing with needs a Claude account to view it. Your manager doesn’t have one. Your client definitely doesn’t.

Copy the code and… then what? You could copy the HTML and JavaScript, but where do you put it? If you’ve never heard of Vercel or GitHub Pages, you’re already lost. And even if you have — do you really want to set up a Git repo, configure a build pipeline, and figure out DNS just to show your boss a calculator?

Screenshot it. We’ve all been there. But a screenshot of an interactive app is like a photo of a bicycle. It doesn’t really capture the experience.

None of these options match what you actually want: a link you can paste into Slack.

The real solution: just tell Claude to share it

Here’s what most people don’t know: you can connect Claude to Brightwing once, and then any time you build something, just say “put this online” — and Claude does it. No copying. No pasting. No leaving the conversation. Claude builds it, publishes it, and hands you a live URL.

The whole thing takes about 30 seconds to set up, and you never have to do it again.

One-time setup (30 seconds)

On claude.ai

1. Go to claude.ai/settings/connectors
2. Click Browse Connectors
3. Search for Brightwing
4. Click the + button to add it

That’s it. You’re done. Claude can now put your apps online.

On Claude Desktop

If you use the Claude desktop app, open your MCP config file:

• Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this to the mcpServers section:

"brightwing": {
  "type": "streamablehttp",
  "url": "https://mcp.brightwing.app/"
}

Restart Claude Desktop and you’re set.

How it works in practice

Once the connector is set up, you just… talk to Claude. Here’s a real example:

You: Build me a habit tracker where I can add daily habits and check them off. Clean, modern design. Put it online.

Claude writes the code, publishes it to Brightwing, and responds with:

• A live URL — click it and your app is working, right there on the internet
• A claim link — click it to add the app to your Brightwing dashboard so you can manage it later

That’s the whole flow. You described what you wanted. Claude built it. Claude put it online. You got a link. Send it to your team.

No GitHub account. No terminal. No “deployment pipeline.” Just a conversation and a URL.

Keep iterating without starting over

Here’s where it gets really good. Stay in the same conversation and ask Claude to make changes:

You: Love it. Can you add a dark mode toggle and a weekly summary view?

Claude updates the code and republishes — to the same URL. Anyone who already has the link sees the new version. No new setup, no second deployment, no version management. Just tell Claude what to change and it happens.

This is what makes the connector approach so powerful. You’re not just publishing once — you’re having a conversation with Claude about your app, and every change goes live instantly.

Share the link

Your app’s URL works everywhere:

• Slack — drop it in a channel and your team can use it immediately
• Email — send it to a client with “here’s that tool I mentioned”
• Text message — share it with a friend who asked for help with something

The person clicking the link doesn’t need a Claude account, a Brightwing account, or any technical knowledge. They just see the app working.

Your app remembers things, too

Most AI-generated apps lose all data when you refresh the page. Apps on Brightwing don’t. Every app automatically gets access to brightwing.db — a built-in storage system that saves data between sessions with zero setup.

Just tell Claude “make sure the data persists between sessions” and it handles the rest. Your habit tracker remembers your habits. Your budget app remembers your expenses. Your to-do list remembers your to-dos.

What about React apps?

If Claude builds your artifact using React (most interactive artifacts use it), don’t worry. Brightwing handles React apps out of the box — no build step, no Node.js, no package.json. Claude publishes the code and it just works.

This is one of the biggest differences between Brightwing and platforms like Vercel or Netlify. Those tools expect a Git repository with a proper project structure. Brightwing expects your code. That’s it.

If you want to dive deeper into how this works, check out How to Put an AI-Generated React App Online for Free.

Keep it or let it go

Apps published without an account live for 14 days. That’s plenty of time for sharing a prototype, demoing an idea, or getting feedback from your team.

Want to keep it longer? Click the claim link Claude gave you to add it to your dashboard. Upgrade to the Personal plan ($3/month) and you get a clean URL like brightwing.app/yourname/your-app instead of the random characters.

But for sharing something with your team right now? You don’t need any of that. Just tell Claude to put it online and send the link.

The paste option (if you prefer)

If you’d rather not set up the connector, you can always go to brightwing.app/launch, paste your code manually, and publish from there. It works great — but once you’ve tried the connector approach, you probably won’t go back. There’s something magical about telling Claude “put this online” and getting a URL back without ever leaving the conversation.

Go try it

You’ve got something in Claude worth sharing. Go share it.

Add the Brightwing connector in your Claude settings, then tell Claude to build something and put it online. You’ll have a live URL in under a minute. No account needed. No GitHub. No terminal. No “deployment pipeline.”

Your AI builds it. Brightwing puts it online. That’s the whole idea.