Getting started

spawnpoint deploys the small apps your agent builds and hands you a public link. One command connects whichever coding agent you use: Claude Code, Codex, Cursor, opencode, or GitHub Copilot. Then you just talk to your agent.

The idea

Agents are great at building small, purpose-built software: a dashboard, a tracker, a quick internal tool. The hard part was never building it, it was deploying and sharing it. spawnpoint collapses that into a couple of sentences you say to your agent.

Three steps

1. Add spawnpoint. One command in your terminal. It detects every supported agent on your machine and wires each one (Claude Code additionally gets the plugin and its skills), so there is nothing else to configure.
   curl -fsSL https://getspawnpoint.com/install | bashCopy
2. Log in. One browser sign-in per agent, and there is never a key to copy: every flow is OAuth, and your agent stores and refreshes its own credentials.
   • Claude Code: after curl -fsSL https://getspawnpoint.com/install | bash, restart it, run /mcp, pick spawnpoint, choose Authenticate.
   • Codex: after curl -fsSL https://getspawnpoint.com/install | bash, run codex mcp login spawnpoint.
   • Cursor: after curl -fsSL https://getspawnpoint.com/install | bash, run cursor-agent mcp login spawnpoint, or approve spawnpoint in the IDE's MCP settings.
   • opencode: after curl -fsSL https://getspawnpoint.com/install | bash, run opencode mcp auth spawnpoint.
   • GitHub Copilot (CLI or VS Code): after curl -fsSL https://getspawnpoint.com/install | bash, use any spawnpoint tool once and approve the sign-in prompt.
3. Say "deploy." Your agent builds and ships the app, and a live link appears in your console. Share it with anyone.

That's the whole flow

No config files, no manual server setup. After the one-time install, it's one sentence:

"deploy"   live at https://….s.getspawnpoint.com

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

Server-rendered Node frameworks deploy as themselves: a package.json build script runs on deploy, a start script is what starts. 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. No account needed on their side. Say "make it public" for a link anyone can open, and flip it back whenever. Un-sharing someone takes effect on their very next click.

Updating

For most agents there is nothing to update, ever: they talk to the spawnpoint server directly and discover new tools the moment we ship them.

Claude Code only (it carries the plugin): run /plugin once, open Marketplaces, select spawnpoint, and enable auto-update; new plugin versions then arrive on their own. Prefer manual? Re-running the install command updates the plugin in place (restart Claude Code to apply).

Manage & tear down

Everything you spawn shows up in your console with its live link, who it's shared with, and basic usage. Terminate any project in one click, the machine stops and the URL frees immediately.

Advanced: connect without the plugin

Any MCP client works. Point it at https://app.getspawnpoint.com/mcp over Streamable HTTP (running 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.