Getting started

spawnpoint deploys the small apps your agent builds and hands you a public link. It's fully skill-driven: install one plugin, then 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 adds the plugin marketplace, installs both skills, and points Claude Code at spawnpoint, so there is nothing else to configure.
   curl -fsSL https://spawnpoint.lol/install | bashCopy
2. Log in. Restart Claude Code, run /mcp, pick spawnpoint, and choose Authenticate. Sign in through the browser and approve. Claude Code keeps the credentials in your OS keychain and refreshes them itself: there is no key to copy.
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://spawn-….run.openrelay.inc

Your agent handles the rest through the deploy_project tool. Static sites, Node services, and Python tools are all supported.

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 your spawnpoint's /mcp endpoint over Streamable HTTP (spawnpoint runs on your machine today, so that is http://localhost:8080/mcp by default); clients that support OAuth discover the flow from the endpoint itself and prompt you to sign in:

{
  "mcpServers": {
    "spawnpoint": {
      "url": "http://localhost:8080/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": "http://localhost:8080/mcp",
      "headers": { "Authorization": "Bearer spk_live_your_token" }
    }
  }
}

See the MCP server reference for the tool schemas.