Using Spryloom from your agent

Spryloom's MCP server gives your coding agent the tools to publish what it built, invite people, read logs and roll back, so you can do all of it by asking. It runs on your own machine and acts as you.

You need Node 20.19 or newer, which you have if you are running a coding agent. You do not need to install spry first: each setup below either carries the server or starts it with npx.

1. Add it to your agent, once

Claude Code

The plugin brings the server and the skill together:

/plugin marketplace add spryloom/claude-plugin
/plugin install spryloom@spryloom

Restart Claude Code, then type /mcp: spryloom should be listed as connected.

If you would rather not use the plugin, add the server and the skill yourself. The skill goes in each project; the server is added once:

npx -y spryloom skill
claude mcp add spryloom -- npx -y spryloom mcp

Codex

codex mcp add spryloom -- npx -y spryloom mcp

Cursor

Open Cursor Settings → MCP → Add new MCP server, or put this in ~/.cursor/mcp.json for every project (or .cursor/mcp.json for one):

{ "mcpServers": { "spryloom": { "command": "npx", "args": ["-y", "spryloom", "mcp"] } } }

Any other MCP client

Spryloom is a local (stdio) server. Whatever the client calls it, the command is npx and the arguments are -y spryloom mcp. If spry is installed, spry mcp is the same server.

It runs on your machine, so it works in agents on your computer. It does not run inside claude.ai or ChatGPT in a browser.

You don't have to do anything ahead of time. The first time the agent uses a Spryloom tool, it says Spryloom is not signed in and asks for your email address. Then:

Spryloom emails you a sign-in link, and the agent shows you a short code.
Open the link and check that the page shows the same code. Confirm.
Tell the agent you have confirmed. It finishes signing in and carries on.

This happens once per machine. The agent and the spry command share the sign-in, so if you have already run spry login, the agent is signed in too.

The agent only signs in with an address you give it. To switch to a different account, run spry logout and then spry login in a terminal; the agent will not switch accounts for you.

3. Ask

Ask the way you would ask a colleague. A few that work:

Publish this for the finance team. Only people I invite should get in.

Invite emily@yourcompany.com and sam@yourcompany.com to expense-notes.

Is anyone using the onboarding checklist? Which version is live?

The last change broke the totals. Roll expense-notes back.

Who has Camera B on the gear wall page?

Before publishing, the agent asks who should be able to open it if you haven't said. A publish takes a few minutes for an app and seconds for a page; the agent can tell you which stage it is on. When it finishes, it gives you the address.

The tools

Tool	What it does
`publish`	Publishes a folder, a zip, a GitHub repository, or one `.html` or `.md` file. Asks who it is for.
`invite`	Invites people to an app by email.
`uninvite`	Removes someone from an app.
`status`	Whether an app is running, which version is live, how many people use it.
`logs`	Recent output from a running app.
`rollback`	Returns an app to an earlier version. Data is left as it is.
`restore`	Brings back an archived app.
`export`	An app's settings, people, versions and history as JSON.
`page_data`	Reads the records of a page that saves data.
`save_page_record`	Adds, changes or deletes a record you saved, when you ask it to.
`custom_domain`	Adds, verifies, lists or removes a custom domain.
`sign_in`, `finish_sign_in`	Sign in, the first time.

Deleting an app is not a tool. Run spry delete yourself, or use the dashboard.

What the skill adds

The tools publish. The skill is what makes the app publish on the first attempt: which port to listen on, committing a lockfile, writing spryloom.yaml, and choosing a page, a page that saves data or an app. The Claude Code plugin includes it. In Claude Code without the plugin, npx -y spryloom skill writes it into the project. Codex and Cursor read the same guidance from the tool descriptions.

If it doesn't work

See your agent and Spryloom on the troubleshooting page: the tools don't appear, npx can't be found, or every call says Spryloom is not signed in.