Getting started

spawnpoint puts the small apps your agent builds online and gives you a public link. To set it up, you ask your coding agent to install it: Claude Code, Codex, Cursor, Antigravity, opencode, GitHub Copilot, and more. After that, you ask your agent to deploy.

The idea

Agents are good at building small apps for one job: a dashboard, a tracker, a quick internal tool. Putting the app online and sharing it is usually harder. With spawnpoint, you ask your agent to do both.

Three steps

1. Ask your agent to install spawnpoint. Send it this message:
   Install spawnpoint for yourself: https://getspawnpoint.com/installCopy
   The agent runs the installer. It finds every supported agent on your machine and sets up each one (Claude Code also gets the plugin and its skills), so there is nothing else to configure. If you prefer to run it yourself, paste this into a terminal:
   curl -fsSL https://getspawnpoint.com/install | bashCopy
   On Windows, paste this into PowerShell instead:
   irm https://getspawnpoint.com/install.ps1 | iexCopy
2. Sign in. Sign in once in the browser for each agent. Your agent tells you the step when the install finishes. There is never a key to copy: sign-in uses OAuth, and your agent stores and refreshes its own credentials.
   • Claude Code: restart it, run /mcp, pick spawnpoint, choose Authenticate.
   • Codex: run codex mcp login spawnpoint.
   • Cursor: run cursor-agent mcp login spawnpoint, or approve spawnpoint in the IDE's MCP settings.
   • opencode: run opencode mcp auth spawnpoint.
   • GitHub Copilot (CLI or VS Code): use any spawnpoint tool once and approve the sign-in prompt.
   • Other agents: see Supported agents.

   In the Claude desktop app, send the same message in the Code tab, then click Authenticate in the browser. In a chat with no terminal, add spawnpoint by hand: Settings → Connectors → Add custom connector, paste https://app.getspawnpoint.com/mcp.

3. Say "deploy." Your agent builds the app and puts it online, and a live link appears in your console.

Deploying

After the one-time setup, you ask your agent to deploy:

"deploy"   live at https://….spwt.app

Your agent handles the rest through the deploy_project tool. Four runtimes: static (any directory of files, including a built frontend), node, python, and docker. Your app listens on port 8080.

Server-rendered Node frameworks work too: a build script in package.json runs on deploy, and its start script starts the app. A Dockerfile at the project root deploys as docker: the machine builds and runs it, so compiled languages work inside a container. Not supported: pushing prebuilt images, or binaries outside a container.

Sharing

New projects are private by default: the link opens only for you and the people you choose. Say "share it with sam@example.com" and your agent adds them; they get an invite email with the link, and the first time they open it they verify with a one-time code sent to their address. They do not need an account. Say "make it public" for a link anyone can open, and switch it back at any time. When you remove someone, they lose access on their next click.

Updating

Most agents need no updates: they talk to the spawnpoint server directly and see new tools as soon as we release them.

Claude Code only (it has the plugin): the installer turns on auto-update for the plugin, so new versions install when Claude Code starts. To update now, ask your agent to install spawnpoint again, then restart Claude Code.

Manage & tear down

Every project you deploy shows up in your console with its live link, who it's shared with, and basic usage. Terminate a project with one click: its machine stops and its URL is freed at once.

Advanced: connect without the plugin

Any MCP client works. Point it at https://app.getspawnpoint.com/mcp over Streamable HTTP (if you run the binary yourself for development, use your local origin); clients that support OAuth discover the flow from the endpoint itself and prompt you to sign in:

{
  "mcpServers": {
    "spawnpoint": {
      "url": "https://app.getspawnpoint.com/mcp"
    }
  }
}

For a script or a client that can't do OAuth, create an API token and send it as a bearer credential instead:

{
  "mcpServers": {
    "spawnpoint": {
      "url": "https://app.getspawnpoint.com/mcp",
      "headers": { "Authorization": "Bearer spk_live_your_token" }
    }
  }
}

See the MCP server reference for the tool schemas.