You asked Claude for a small app, and it works. Now a teammate wants to use it, and someone else wants to change a column or add a filter. This guide shows how to put the app online behind a link only your team can open, and how each teammate can keep improving it from the AI assistant they already use.
On this page: Quick answer · Key takeaways · Why not share the artifact or use GitHub · Step 1: Connect · Step 2: Put it online · Step 3: Choose who can open it · Step 4: Invite · Step 5: Edit · Step 6: History · FAQ
Quick answer
To share an app you built with Claude so your teammates can use it and change it, put it on Server4Agent:
- Connect Server4Agent to Claude as a custom connector and sign in. No API key needed.
- Ask Claude to put the app on Server4Agent. You get a live address at
apps.server4agent.com. - Set who can open it: anyone with the link, only your team, or anyone with a password you set.
- Invite teammates as members from the Team page in the dashboard.
- Each teammate edits from their own assistant, whether that is Claude, ChatGPT or Cursor. Changes land in the same project, and the link stays the same.
Key takeaways
- Sharing inside Claude only reaches teammates who also use Claude. Server4Agent puts the app on a server, so anyone you invite can open it and change it.
- New projects are private. You choose who can open the app: anyone with the link, your team only, or anyone with a password.
- Teammates edit from Claude, ChatGPT, Cursor or another MCP host. Every change lands in the same project behind the same link.
- The app keeps running after the chat ends, and every change is kept in the project's git history.
Key facts
| Server4Agent | |
|---|---|
| Works from | Claude, ChatGPT, Cursor, VS Code, Codex CLI, GitHub Copilot and any MCP host |
| Connect address | https://mcp.server4agent.com (sign in, no API key for Claude or ChatGPT) |
| Who can open the app | Anyone with the link, your team only (or named people), or anyone with a password |
| New projects | Private until you publish them |
| Who can edit | Members and admins you invite. Viewers can only open what is shared with them |
| Keeps running | Yes. The app stays up after the chat ends, backends and scheduled jobs included |
| History | Every project is a git repository with a history of every change |
| Seats | Free 1, Starter 3 ($29 a month), Pro 5 ($99), Business 15 ($299) |
| Spending | One account-wide budget cap that agents cannot raise |
Why not share the artifact or push it to GitHub?
These are the two usual answers, and each leaves someone out.
- Sharing inside Claude works when everyone on the team uses Claude, on a plan that allows shared editing. A teammate who works in ChatGPT or Cursor can't pick it up.
- Pushing the code to GitHub and hosting it on Vercel or Netlify works for developers. Everyone else needs a GitHub account, a copy of the code and a deploy setup before they can change one button.
Server4Agent sits between the two. The app lives on a server with its own address, and anyone you invite changes it by asking their own assistant. Nobody installs anything.
Step 1: Connect Server4Agent to Claude
In Claude, open Settings, then Connectors, then Add custom connector. Paste https://mcp.server4agent.com, click Connect, and sign in to Server4Agent. There is no API key to copy. The integrations page has the same steps with a picture of what it looks like once it is connected.
If your company is on Claude's Team or Enterprise plan, an admin can connect the whole organization at once, so teammates skip this step. See automatic sign-in from Claude.
Step 2: Put the app on Server4Agent
In the chat where Claude built your app, ask:
Put this app on Server4Agent and give me the link.
Claude creates a project, writes the files, starts the app and hands back an address at apps.server4agent.com. The app keeps running after you close the chat, so a dashboard keeps refreshing and a bot keeps answering.
If the code already lives somewhere else, bring it in instead:
- From a Git repository, with the Import from Git template. A private repository works with an access token you store as a secret.
- From a .zip of the code, with the Upload a codebase template.
Server4Agent installs and starts the app for you. If it needs keys, such as an API key for another service, it pauses and asks for them.
Step 3: Choose who can open it
New projects start private, so nothing is on the internet until you say so. When you are ready, publish the project and choose who can open it:
- Anyone with the link: for apps meant for customers or the public.
- My team: only people signed in to your Server4Agent account. You can narrow it to named people.
- Password: anyone who enters a password you set, with no account needed. Useful for a client or a contractor.
You can set this in the project's settings, or just tell Claude: "Make this app team-only." The guide to sharing with your team without going public covers the access options in more detail.
Step 4: Invite your teammates
In the Server4Agent dashboard, open Team, enter a teammate's email and pick a role. Each invite only works for the address it was sent to.
| Role | What they can do |
|---|---|
| Member | Build and change projects, servers and secrets in the account |
| Admin | Everything a member can do, plus invite and remove people |
| Viewer | Open only the app links shared with them. No editing |
To let someone edit the app, invite them as a member. To let someone only use it, invite them as a viewer.
Step 5: Teammates edit from their own assistant
Each teammate connects the assistant they already use, with the steps on the integrations page:
- Claude: the same connector steps as above, signing in with their own Server4Agent login.
- ChatGPT: add Server4Agent as a custom MCP server and sign in. No API key needed.
- Cursor, VS Code, Codex CLI, GitHub Copilot and other MCP hosts: paste the config block with an API key from the account.
Then they ask for the change in plain words: "Add a date filter to the orders table." The change lands in the same project and the same link updates. Nobody has to know which assistant built the first version. How a team builds one tool when everyone uses a different AI assistant walks through a longer example.
All usage counts toward one account budget with a hard cap, so a busy week can't run up a surprise bill.
Step 6: Keep a history and hand off
Every project is a git repository. An engineer can open it in VS Code in the browser, read the history of every change, and take it from there. You can also export a project as one portable file and import it somewhere else.
FAQ
How do I share an app I built with Claude so my team can edit it?
Connect Server4Agent to Claude as a custom connector, ask Claude to put the app on Server4Agent, set the link to team-only, and invite your teammates as members. Each teammate can then change the app from their own AI assistant, and everyone keeps using the same link.
Do my teammates need to use Claude too?
No. They can use Claude, ChatGPT, Cursor or any other assistant that supports MCP. Everyone works on the same project in your Server4Agent account.
Do my teammates need a Claude Team plan?
No. They join your Server4Agent team, not your Claude plan. Automatic sign-in for a whole Claude organization is the one part that needs Claude's Team or Enterprise plan.
Can people outside my company use the app?
Yes. Set the link to anyone with the link, or protect it with a password you share with them. Anyone who has an open link can use the app, so keep internal tools team-only.
What happens when someone leaves the team?
Remove them from the Team page. Their access ends on their next request, and a team-only link they still have stops working within the hour.
Does the app keep running after I close the chat?
Yes. The app runs on a server, not in the chat, so it stays up until you stop it. That includes backends, bots and scheduled jobs.
How much does it cost to share with a team?
The Free plan is for one person. Starter is $29 a month with 3 seats, Pro is $99 with 5 seats, and Business is $299 with 15 seats. Seats include the owner.
Can an engineer take over the code later?
Yes. Every project is a git repository with the history of every change. An engineer can open it in VS Code in the browser, or export the project as one file and import it somewhere else.
Related reading
- Share an internal tool with your team without putting it on the internet: the access options in more detail.
- How a team builds one tool when everyone uses a different AI assistant: a longer example of editing from different assistants.
- Claude auto-connect: give your whole team a server: connect a whole Claude organization at once.
- The non-technical guide to shipping real tools from chat: for teammates who have never built anything.
External references
- Get started with custom connectors using remote MCP, Claude's help center
- Model Context Protocol
About Server4Agent
Server4Agent is a hosted server for AI agents. Your assistant builds a tool, site, API or bot on it from a plain-English request and ships it to a live URL, private by default and under a hard budget cap. See the integrations page to connect the assistant you use.