spawnpoint

com.getspawnpointPublished by getspawnpoint.comOfficial publisherv0.16.7Updated Nov 8, 2026

The launchpad for your AI-enabled business: deploy what your agent builds to a private link.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Remote MCP server that lets an assistant deploy the apps, tools and MCP servers it builds to a private link and share it with teammates.

What you can do
  • Deploy apps the assistant builds, picking a runtime (static, Node, Python or Docker) and following the deploy until it is live
  • Return a private link, then share it with one email address or the whole company, change the app, or take it down
  • Attach supporting resources such as databases, file storage and MCP servers to a deployed app
  • Audit an app before shipping: find leaked API keys, files that should not upload, port and bind issues, and unauthenticated admin or upload routes
  • Optionally switch an app's OpenAI or Anthropic calls to open models hosted by the service, without a provider account or key
When to use it
Useful when you want an assistant to turn something it built into a running, shareable web app without setting up hosting yourself, and to hand the link to colleagues who do not create accounts.
Requirements
A remote endpoint at app.getspawnpoint.com over Streamable HTTP; OAuth sign-in in a browser is required and there are no keys to copy. For Claude, the plugin is added from its marketplace and connected; other MCP clients connect to the MCP endpoint directly.
Before you install
Deploying publishes code to a third-party hosting service and creates links that can be shared with individuals or the whole company. The security audit can fix some issues automatically and stops the deploy on others, so review what it changes. Apps may include databases, file storage and secrets, so check what gets uploaded before deploying.

Installation

In SourceWeft

  1. Open spawnpoint in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.getspawnpoint%2Fspawnpoint/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

[spawnpoint]

spawnpoint plugin for Claude

spawnpoint is the place where your team's AI lives. With this plugin, Claude puts the tools, MCP servers, and apps it builds for you online and hands you a link, in a chat, in Cowork, or in Claude Code. The link is private until you share it, with one person's email or with everyone at your company, and the people you share it with never make an account.

Install

In claude.ai or the Claude desktop app:

  1. Open Customize, then Plugins, then Add, then Add marketplace, and enter https://github.com/spawnpoint-inc/spawnpoint-plugin.
  2. Install spawnpoint, open its Connectors tab, and click Connect.
  3. Sign in to spawnpoint in the browser that opens and click Approve.

In Claude Code, one command sets up Claude Code, Codex, Cursor, Copilot, and many more agents:

sh
curl -fsSL https://getspawnpoint.com/install | bash

Or install just this plugin by hand:

sh
claude plugin marketplace add spawnpoint-inc/spawnpoint-pluginclaude plugin install spawnpoint@spawnpoint

Restart Claude Code, run /mcp, select spawnpoint, choose Authenticate, and approve in the browser. You sign in once; there are no keys to copy.

Then ask for something: "make a page where my running club says who is coming on Saturday, and deploy it with spawnpoint." Claude builds it, deploys it, and gives you the link. Ask it to share the link with a teammate, change the app, or take it down.

What's in it

The spawnpoint connector (the tools Claude uses to deploy) and three skills, in plugin/spawnpoint/skills/:

  • deploy-to-spawnpoint: picks the runtime (static, Node, Python, or Docker), sends the app, follows the deploy until it is live, and hands back the link. It also covers sharing, databases, file storage, MCP servers, and team apps.
  • security-audit: checks an app before it ships. It finds leaked API keys and files that should not upload, checks the port and bind address spawnpoint needs, and flags debug mode and admin or upload routes with no login. It fixes what is safe to fix and stops the deploy on what is not. Run it yourself with /spawnpoint:security-audit.
  • open-models: when an app calls OpenAI or Anthropic, asks once whether to run it on open models through spawnpoint instead (no provider account, no key), picks the model, and makes the edit.

The skills are tested against a mock spawnpoint server before each release, so changes are measured, not guessed.

Not using Claude?

spawnpoint is a remote MCP server. Any MCP client can connect to https://app.getspawnpoint.com/mcp (Streamable HTTP, OAuth sign-in in the browser). It is listed in the official MCP registry as com.getspawnpoint/spawnpoint. Steps for each agent: supported agents.

Update

Run /plugin, open Marketplaces, select spawnpoint, and turn on auto-update. Marketplaces from outside Anthropic have it off by default; after that one toggle, Claude Code picks up new versions on its own.

To update by hand, run these two commands, then restart Claude Code:

sh
claude plugin marketplace update spawnpointclaude plugin update spawnpoint@spawnpoint

New MCP tools need no plugin update: agents get them from the server.

Links

This repo is the published plugin only. It is synced from spawnpoint's main repository on every release.

Source: README.md at commit 1127ef5

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

4
  1. v0.15.1Oct 18, 2026
  2. v0.7.0Oct 5, 2026
  3. v0.6.0Oct 4, 2026
  4. v0.5.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts