Your App Store for Everything You Build with AI
AI built it.
Now ship it.
Your team builds the app with the AI tools they already use. SpringRoll gives it a home, gets the right people to approve it, and connects it to company data without handing over the keys.
Build on one side. Data on the other.
SpringRoll brings them together.
Your coding agent sends the app. Your company systems provide the data. SpringRoll puts approvals, identity, and a clear record between them before the app reaches your team.
AI coding agents
Claude Code · Codex · ChatGPT · Claude Desktop
Source · owner · releaseOne approved app record
Identity · approval · policy · audit
Company data
PostgreSQL · Notion · Salesforce · SAP
Fields · rows · limitsA URL your team can open and share.
https://your-app.vercel.appUse the preview for feedback, then promote the same release.
AI coding agents send application source and release details to SpringRoll. Company systems send approved data through SpringRoll. SpringRoll applies identity, approval, policy, and audit controls before Finance, Demand, and Operations applications receive a live URL their users can open and share.
What you get
A real home for every internal app.
See what is running, who owns it, what data it can use, and who approved it. When something changes, the history stays with the app.
Deploy
- App Registry
- Immutable Releases
- DEV / UAT / Production
- Human approval
- RBAC
- Rollback
- Provenance
Connect
- App Identity
- Connectors
- Data Products
- Access grants
- Gateway enforcement
- Revocation
Control plane
- Tenant isolation
- Secrets
- SSO / SAML / OIDC
- SCIM
- Policies
- Immutable audit trail
Try it from your coding agent
Copy. Approve. Deploy.
Choose your agent, copy one command, and approve the connection in your browser. SpringRoll takes care of the app record, release, and development preview.
Terminal. One command, then authorize.
- 01
Add SpringRoll
Run this once, from anywhere.claude mcp add --transport http springroll https://springroll.dev/api/mcp
Then start Claude and authorize. Your browser opens by itself./mcp
- 02
Authorize
Choose your organization in the browser and approve the connection. No credential is exposed for you to store.
- 03
Deploy
Ask the agent to register, validate, and deploy the project.
/springroll deploy
Also claude.ai. Added as a custom connector.
Custom connectors are a paid feature on Claude — Pro, Max, Team, or Enterprise.
- 01
Add SpringRoll
Open Settings, then Connectors.
Choose Add custom connector.
NameSpringRoll
URLhttps://springroll.dev/api/mcp
Save, then connect. Claude opens this authorization page itself.
- 02
Authorize
Choose your organization in the browser and approve the connection. No credential is exposed for you to store.
- 03
Deploy
Ask the agent to register, validate, and deploy the project.
Deploy this project to SpringRoll.
Web. Needs developer mode turned on first.
Connectors are available on ChatGPT Pro and Plus, on the web. This endpoint must be reachable from the internet, so it will not work against a localhost SpringRoll.
- 01
Add SpringRoll
In Settings, open Connectors, then Advanced settings, and turn on Developer mode.
Back in Connectors, choose Create.
NameSpringRoll
MCP server URLhttps://springroll.dev/api/mcp
AuthenticationOAuth
Create, then authorize. The connector appears under Developer mode in the composer.
- 02
Authorize
Choose your organization in the browser and approve the connection. No credential is exposed for you to store.
- 03
Deploy
Ask the agent to register, validate, and deploy the project.
Deploy this project to SpringRoll.
Terminal. The CLI finds the authorization server itself.
- 01
Add SpringRoll
Run this once. Codex probes the URL, sees it supports OAuth, and opens your browser.codex mcp add springroll --url https://springroll.dev/api/mcp
The entry is written to ~/.codex/config.toml. Add it inside a project to scope it to that project instead.
- 02
Authorize
Choose your organization in the browser and approve the connection. No credential is exposed for you to store.
- 03
Deploy
Ask the agent to register, validate, and deploy the project.
Deploy this project to SpringRoll.
One URL. Nothing else to configure.
- 01
Add SpringRoll
Remote MCP endpointhttps://springroll.dev/api/mcp
Any MCP client that speaks streamable HTTP can be pointed straight at this URL. It still opens a browser to authorize — the endpoint advertises its own authorization server, so the URL is the only thing to configure.
Clients that register a private-use redirect scheme without a dot in it, such as Cursor and Windsurf, are refused at registration. That rule is RFC 8252 §7.1 and it is not a bug.
- 02
Authorize
Choose your organization in the browser and approve the connection. No credential is exposed for you to store.
- 03
Deploy
Ask the agent to register, validate, and deploy the project.
Deploy this project to SpringRoll.
Questions before you deploy
The short answers.
SpringRoll is built for the handoff after an AI coding tool has made the app: deployment, approval, access, and a URL your team can actually use.
What happens after I connect my coding agent?
Your agent registers the app, creates an immutable release, and deploys a development preview. SpringRoll returns a live URL you can open and share with your team.
Does the app get our database password?
No. SpringRoll keeps the source credential. The app receives its own identity and can only request the fields, rows, and volume a data owner approved.
Can an AI agent deploy straight to production?
No. An agent can request a promotion, but a person with the right role must approve production and governed data access.
Which coding agents can I use?
Claude Code, Codex, ChatGPT, Claude Desktop, and other OAuth-compatible MCP clients are supported. Cursor is not listed while its redirect scheme remains incompatible with SpringRoll's OAuth policy.
Can I share the deployed app?
Yes. Every deployment returns a URL. Share the development preview for feedback, then promote the same recorded release through UAT and Production.