About spawnpoint
spawnpoint is a remote MCP server and Claude plugin for deploying apps, tools, and MCP servers built by Claude. It provides private links that can be shared with selected people or a company, without requiring recipients to create accounts.
Key features
- 01Deploy static, Node, Python, or Docker apps
- 02Share deployed apps through private links
- 03Run a pre-deployment security audit
- 04Use open models through spawnpoint
Use cases
- 01Publish a Claude-built app for a team
- 02Check an app for exposed keys before deployment
- 03Share an internal tool without recipient accounts
MCP support
spawnpoint is a remote MCP server at `https://app.getspawnpoint.com/mcp`, using Streamable HTTP and browser-based OAuth. MCP clients can connect to its deployment and sharing tools.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://app.getspawnpoint.com/mcpclaude mcp add --transport http com-getspawnpoint-spawnpoint https://app.getspawnpoint.com/mcp{"mcpServers":{"com-getspawnpoint-spawnpoint":{"type":"http","url":"https://app.getspawnpoint.com/mcp"}}}Open in Cursor{"servers":{"com-getspawnpoint-spawnpoint":{"type":"http","url":"https://app.getspawnpoint.com/mcp"}}}Open in VS Code{"mcpServers":{"com-getspawnpoint-spawnpoint":{"type":"http","url":"https://app.getspawnpoint.com/mcp"}}}{"mcpServers":{"com-getspawnpoint-spawnpoint":{"serverUrl":"https://app.getspawnpoint.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project README
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:
- Open Customize, then Plugins, then Add, then Add marketplace, and enter
https://github.com/spawnpoint-inc/spawnpoint-plugin. - Install spawnpoint, open its Connectors tab, and click Connect.
- 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:
curl -fsSL https://getspawnpoint.com/install | bash
Or install just this plugin by hand:
claude plugin marketplace add spawnpoint-inc/spawnpoint-plugin
claude 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:
claude plugin marketplace update spawnpoint
claude plugin update spawnpoint@spawnpoint
New MCP tools need no plugin update: agents get them from the server.
Links
- Docs: getting started and the MCP server and its tools
- For agents: llms.txt and llms-full.txt
- Security, privacy, and terms
- Questions and security reports: [email protected]
This repo is the published plugin only. It is synced from spawnpoint's main repository on every release.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.