SpringRoll

npx add-mcp 'https://springroll.dev/api/mcp'

Deploy and share your app

Connect your coding agent to SpringRoll. Deploy an existing app, choose a release workflow, share the right team link and manage approved data access.

Connect your coding agent, publish an existing app and give colleagues a useful team link. SpringRoll currently deploys to managed Vercel and Cloudflare. Start with the worked example or use this reference for later updates.

Connect your coding agent

Install the SpringRoll skill with the command below. On the first live call, sign in through the browser, choose your workspace and authorize your agent. Check the workspace before deploying.

OAuth-capable MCP clients can connect directly to /api/mcp. Public discovery describes available tools and manifest requirements; workspace actions require authentication.

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

Start with a runnable synthetic app Read authentication details

Publish an app

Ask your agent to deploy with /springroll deploy. SpringRoll records the application and release, then starts a build. Follow the deployment in the app overview.

Direct to Production is the default. Required checks still apply. A Tenant Admin can configure staged Development, UAT and Production when a human review is required. Read the selected workflow before assuming the first link is a preview.

Wait for READY, then open the working app. Verify its core task, release and intended environment before sharing. A build result and a working application are separate checks.

Understand the deployment handoff Choose a review workflow

Share the working app

From the app overview, choose Copy app link. Check who can open it beside the link. Copying a link does not change permissions; use Access to manage the audience.

Production and Test links are labelled separately. A Public app page introduces an app with images and a description; publishing it does not change access to the running app.

Plan the team portal handoff

Publish an update

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

Open View build error if an attempt fails. Fix the source or build settings, then record a new release. For staged apps, review and promote the intended immutable release rather than a moving source branch.

Review runtime fit and hosting

If you get stuck

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.

Request a fresh sign-in email link if the old one has expired. Contact SpringRoll with the app name, error and a redacted reproduction when you need help. Keep passwords and tokens out of the message.

Get help

Access and data

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.

SpringRoll launch links check membership and access rules for the selected environment. Development previews are for app managers. A direct provider URL uses the provider's access settings, so protect that path with application or provider authentication as well.

For the data-product gateway, active grants scope fields, rows and query volume. Source credentials stay on the server. Revoke stops future gateway access without redeploying; it does not retrieve data the app already read or stored.

Connector grants are a separate path that may inject approved credentials into an app runtime. Verify enforcement for the exact source and path. Natural-language queries need a configured planner, and available operations depend on source capabilities.

Roles determine who can publish, review requests and manage data. Governed operations and their audit records are saved together. Workspace administrators can inspect these in Audit trail.

Review data-product grants Read detailed security boundaries

API and MCP reference

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

These public pages also support Markdown through Accept: text/markdown. /llms.txt is an index and /llms-full.txt contains their text. These formats help agents read the same content; they are not a ranking or inclusion guarantee.

Read API reference Read OpenAPI Inspect the synthetic example

Product workflow: Install, authorize, deploy, verify

01 · Setup: Install the skill

Use the setup command in Docs with your coding agent.

02 · Workspace: Authorize the first live call

Sign in and choose the workspace. There is no token to paste.

03 · Publish: Ask the agent to deploy

SpringRoll records the app and release, then starts the deployment.

04 · Verify and share: Check the build result

After READY, open the app and share the intended environment link.

A deployment result is the handoff record. Opening the app checks that the result actually works.

---

Canonical: https://springroll.dev/docs

Machine-readable: llms.txt · OpenAPI · API index · MCP server card