spryloom
OfficialPublishes an app straight from a GitHub repository — a repo path (e.g. github.com/owner/repo/tree/main/examples/weekly-status) can be packed and uploaded for deployment, alongside local folders and pages. The packed source is then run at a private address only invited people can open.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Spryloom
The publish button for coding agents. Your agent builds a small app; Spryloom runs it at a private address that only the people you invite can open, with a database, scheduled jobs and email if the app asks for them. You don't set up a server, a database or sign-in.
You: Publish this so my team can use it.
Agent: Published: https://weekly-status.acme.spryloom.app
Version 1
Sign-in people you invite
Data 5 tables
Want me to send this to anyone?This repository holds everything Spryloom puts on your machine: the agent
skill, the setup for each coding agent, and the source of the spry command
line and its MCP server. The service that runs your apps is not in it.
Install
You need Node.js 20.19 or later.
Claude Code, as a plugin:
/plugin marketplace add spryloom/spryloom
/plugin install spryloom@spryloomCodex, Cursor and other agents that read skills:
npx skills add spryloom/spryloomCursor, for the MCP server: copy cursor/mcp.json into
your project's .cursor/mcp.json.
Any MCP client: run npx -y spryloom mcp over stdio.
The command line:
npm install -g spryloom
spry login --email you@yourcompany.com
spry publish .Then ask your agent: "Publish this so my team can use it."
Related MCP server: unlocalhost
Starters
Finished apps to publish as they are, or to hand to your coding agent and make your own. Each runs locally against any Postgres, opens with example data you can remove in one click, and works in light and dark and on a phone.
Starter | For | What it does | Live demo |
Project and team leads | Everyone answers three questions per project on Friday. Blockers and missing updates come first, and admins get a Monday summary. | ||
Small companies | Request leave, approve it, see your balance, and see who's out on a team calendar. Weekends and company holidays aren't counted. | ||
Teams paying for AI and SaaS tools | What the team pays for each month, what renews next, which seats sit unused, and requests for new tools. |
The demos are shared by everyone who signs in, and go back to their example data every night.
Publish one straight from GitHub:
npx -y spryloom login --email you@yourcompany.com
npx -y spryloom publish github.com/spryloom/spryloom/tree/main/examples/weekly-statusOpen the address it prints. As the publisher, you are an admin: add a real project and its people, then remove the example data when you are ready. Add each coworker to the project and invite them to open the app:
npx -y spryloom invite weekly-status --email teammate@yourcompany.comThe project assignment asks for their weekly check-in; the Spryloom invitation gives them access to the app. Ask them to open the email link and check in. The full first-use path, including a prompt for your coding agent, is on spryloom.com/starters.
What's here
Folder | What it is |
The agent skill: how to write an app that publishes the first time, and how to publish it. | |
The Codex plugin: the same skill, written for the | |
MCP setup for Cursor. | |
A Claude Code marketplace. The plugin itself is published from spryloom/claude-plugin, which carries the MCP server ready to run. | |
| |
The MCP server and the tools it gives your agent. | |
Reads and checks | |
The requests the command line sends to Spryloom, and the answers it gets. | |
Works out how an app runs when its manifest doesn't say. | |
Packs a folder, a page or a GitHub repository for upload. | |
The starters above, one folder each. |
src/ is the TypeScript the spryloom npm package
is compiled from, so you can read what the MCP server does before you install
it. It is published here to be read, and doesn't build on its own.
How this repository is updated
It is generated from Spryloom's private repository on each release, one commit per version. Issues are welcome. A pull request can't be merged here directly, but we'll make the change upstream and credit you, and it will appear in the next release.
Docs: spryloom.com/docs · Support: hello@spryloom.com
Licence
MIT.
This server cannot be deployed
Maintenance
Related MCP Connectors
Publish an app your AI agent built, then choose who can open it, like sharing a doc.
Ask your AI to put your app online. Your colleagues get a web address, a sign-in and saved data.
Deploy a multi-user web app from your agent: hosting, auth, database, and permissions.
Deploy, share and run the Apps you build with AI, private to the people you invite.
Related MCP Servers
- AlicenseAqualityDmaintenancePublish live web pages from AI coding agents. Instant shareable URLs for dashboards, landing pages, and reports with password protection.41MIT
- AlicenseNot gradedqualityDmaintenanceEnables coding agents to deploy applications to private, authenticated URLs with a guest list, so only specified users can access them without writing auth code.3MIT
- AlicenseNot gradedqualityBmaintenancePublish what your agent just built to a durable link, with immutable versions, a diff between any two, and comments on the page itself.131 npmMIT

SnapHostofficial
AlicenseNot gradedqualityBmaintenanceSend a live, private link to a client from Claude. SnapHost publishes what your assistant builds as a shareable website with a stable URL, updates it in place, restricts viewers by email or password, rolls back bad versions, serves custom domains, and stores form and waitlist data with no backend.MIT