Documentation

Connect your agent and choose Connect SpringRoll to start as a guest. If you already have an account, you can sign in and use its workspace instead. The optional skill below adds a guided deployment workflow. Check the workspace before deploying.

npx skills add springroll-dev/springroll-skill --skill springroll

• Follow the quick start →

With the skill installed, ask your agent to deploy with /springroll deploy. If you connected MCP manually, ask the agent in plain language to prepare and deploy the project. SpringRoll records the application and release, then starts a build. Follow the deployment in the app overview.

• Read: Publish an app →

Set the audience before sending a SpringRoll link. A colleague signs in to the workspace and the portal checks launch access for that environment. Ask a colleague outside the audience to try the link, then test the direct provider URL separately.

• Read: Share the working app →

Ask your agent to deploy the changed source. Follow the new attempt in Deployments. The current working version stays available while the update builds.

• Read: Publish an update →

For a failed build, open View build error. For blocked publication, follow the named remedy or review the approval request. If a colleague cannot launch, check the audience and the selected environment.

• Read: If you get stuck →

On the app's Data tab, request the fields it needs from a defined data product. Review the request, approved scope and expiry with the data owner.

• Read: Access and data →

Use /docs/api for authentication, rate limits, versioning and errors. /openapi.json describes REST endpoints, and /api/v1/capabilities lists tools and manifest requirements.

• Read: API and MCP reference →

Start with a static app, or an app whose build and runtime fit managed Vercel or Cloudflare. The example collection includes dependency-free static apps you can try and deploy from the browser.

• Static HTML, CSS and JavaScript: provide the build command and output folder. These examples use npm run build and dist.
• Apps with a server: have your agent check the framework, build command, runtime, environment variables and external services before deploying.
• Background workers, long-lived connections or persistent local files: ask the team to review the runtime design before choosing a deployment target. Use shared storage or a database for team records.

• Read: Choose a good first app →

Name the owner, verify the release and test the launch link with an intended colleague and an unapproved account.

• Read: Launch an app with your team →