Brod

Guide

Share a Claude Code app with your team

The app runs on localhost:3000 and your team wants to use it. This guide takes it from your laptop to a private HTTPS address your colleagues sign in to, with you deciding exactly who gets in.

Deploy your first app Claude Code deploy guide 
claude mcp add --transport http brod https://brod.sh/mcp

From localhost to your team

Screen sharing, a tunnel from your laptop or a shared server login all stop working the moment you close the lid or someone leaves.

  • An address that stays up. Not one that depends on your laptop.
  • A sign-in your team already has. Nobody gets a new password.
  • A way to add and remove people. You decide exactly who gets in.

Here is that path with Claude Code and Brod.

1. Deploy it

The Claude Code deploy guide covers this step in more detail, including frameworks and server code.

  1. Connect Brod once

    Run claude mcp add --transport http brod https://brod.sh/mcp.

  2. Sign in

    Run /mcp in Claude Code, pick brod, and sign in in the browser.

  3. Ask Claude to deploy

    Ask Claude to deploy the app and give it a name. The first version goes live straight away at its own HTTPS address.

  4. Open it yourself

    It is private: only you and the workspace admins can open it. Open it yourself before you share it.

Check the app is ready for other people. If Claude wrote a login page or a users table, ask it to remove them and read the signed-in person from Brod instead. See authentication for AI-generated apps.

2. Get your colleagues into the workspace

A Brod workspace is your team: the people who can sign in and be given apps. Each person has a workspace role.

Use member for colleagues who just use the app and builder for those who will change it with their own agent. Use guest for a contractor or client who should see one app and nothing else.

Claude can send invitations with the invite tool. Invitations last 7 days. People sign in with an emailed link, or Google where it is set up, so nobody gets a new password.

RoleWhat they can do
adminManage people, groups and branding, invite people into the workspace, change roles.
builderDeploy and manage apps and connect agents. Can invite a guest to one app.
memberUse the apps they can open.
guestOnly the apps they were given.

3. Choose who can open the app

Pick one access mode for the app. You can change the mode any time without a redeploy.

  • people

    Only the people, groups and email domains you grant a role. The usual choice for a team tool.

  • workspace

    Everyone in the workspace. Guests only if granted.

  • password

    Anyone with the address and the app's password, without an account.

  • signed_in and public

    Much wider. On brod.sh, signed_in means anyone with a brod.sh account. Rarely right for internal data.

Access is checked before every request. Someone the app is not shared with gets the same "App not found" page as an address with no app, so the app's existence is not revealed.

4. Grant groups and domains, not just names

In people mode, a grant gives a role to:

  • A person

    By email.

  • A group

    Such as finance. Groups are set up by workspace admins, so when someone joins finance, they get every app finance can open.

  • An email domain

    Such as everyone at your company's domain.

  • App roles. Each app has roles, by default owner, editor and viewer. Grant viewers widely and editors narrowly.
  • The app enforces them. The app reads the role from the x-brod-role header and must enforce it itself: Brod tells the app who is an editor, and the app's code decides what editors can do.
  • Spaces. If several apps go to the same people, an admin can put them in a space, a named set of apps and the people who use them. Adding someone to a space gives them every app in it.

5. Confirm the links

When Claude asks to widen access or invite someone, nothing changes yet. Brod returns a short summary and a confirmation link, and Claude passes it to you.

Open the link, read the summary, and confirm. You must be signed in to the same workspace, with a role that could make the change yourself.

This is deliberate: an agent can ship code, but opening an app up stays a person's decision. Narrowing access, such as removing a grant, applies at once with no link.

Share rota with the support group as viewers, and make Priya an editor.

set_access

That widens access, so it needs your confirmation. Open this link to approve it. It expires in 24 hours.

On a new free workspace on brod.sh, the password, signed_in and public modes are held for the first 24 hours. Sharing inside the workspace works from the start.

6. Keep changing it together

  • Staging first

    When Claude updates the live app, the new version goes to a staging address. Your team keeps using the live one until you publish. Staging uses the live data, so test carefully.

  • Several builders

    If a colleague's agent changed the app since your files were fetched, your deploy is refused with 409 stale_base and told who deployed what. It is refused, not merged, so nobody's change is lost silently.

  • Someone leaves

    Remove them from the workspace and they lose access to every app on their next request.

Questions

Do my colleagues need Claude Code?

No. They open the address in a browser and sign in. Only people who change the app need an agent connected to Brod.

Can I share with someone outside the company?

Yes. Invite them as a guest to that one app, or use password mode. Both widen access, so an agent's request waits for your confirmation.

Can Claude share the app with everyone by itself?

No. It can ask, and you get a link to confirm. Until a person confirms, access stays as it was.

Your AI already built the app. Put it in your team's hands.

Deploy your first app Read the docs