Add SpringRoll as a custom connector
Custom connectors belong to your Claude account. Claude connects to SpringRoll from Anthropic's cloud, so one setup works in claude.ai, Claude Desktop and Claude's mobile apps. SpringRoll needs only its URL; there is no API key.
- Open Customize, then Connectors. Choose Add, then Add custom connector.
- Name: SpringRoll
- URL: https://springroll.dev/api/mcp
- Choose Continue. Claude detects SpringRoll's OAuth sign-in; keep the recommended settings, including Use Claude's published identity under OAuth client, and choose Add.
- Connect. On SpringRoll’s authorization page, choose Connect SpringRoll to start as a guest. No SpringRoll account or sign-in is needed. An existing signed-in session uses its workspace.
Name: SpringRoll
URL: https://springroll.dev/api/mcp
OAuth client: Use Claude's published identity (Recommended)Which OAuth client option to choose
Keep Claude's recommended option, Use Claude's published identity. Claude then identifies itself with a client ID metadata document it publishes at claude.ai. SpringRoll fetches that document, checks that it names itself and lists Claude's own callback address, and shows claude.ai on the sign-in page, so you can see which product is asking before you approve. There is no client ID or secret to enter.
Register automatically also works: Claude registers itself with SpringRoll through dynamic client registration instead. Use your own OAuth client is not needed, because SpringRoll does not issue client secrets. Whichever option you pick, the credential Claude receives belongs to your SpringRoll membership and carries only your permissions.
Free accounts can add one custom connector, which is enough for SpringRoll. Pro, Max and Ultra accounts can add more.
Add SpringRoll for a Team or Enterprise organization
On Team and Enterprise plans, an Owner adds the connector once for the organization: Organization settings, Connectors, Add, then Custom and Web. Enter the name SpringRoll and the URL https://springroll.dev/api/mcp, keep Use Claude's published identity under OAuth client, and add it. On Enterprise, people with a custom role that can manage access to Libraries can add it too.
Each member then opens Customize, Connectors, finds SpringRoll and chooses Connect. Members sign in to SpringRoll as themselves, so every deployment is recorded against the person who made it.
Turn SpringRoll on in a conversation
Choose the + button at the lower left of the chat box, then Connectors, and switch SpringRoll on for the conversation. Check the connection first:
Use SpringRoll to show which workspace and permissions you are connected with.Deploy an app from a Claude chat
SpringRoll takes an app's source three ways, so a chat can deploy without a local folder: a repository URL SpringRoll can read, files Claude writes in the conversation, or a project archive. For a single page or a small static app, Claude can send the files directly. For anything larger, push the project to a repository and give Claude its URL. Then ask:
Prepare this project for SpringRoll. Read the Company Blueprint, inspect my source and discover supported workloads and services. Check the build, workspace, owner and deployment workflow; show the exact deployment proposal for confirmation, then follow the build to its actual result.What happens when Claude deploys through SpringRoll
Claude reads your workspace with springroll.context, checks the build and shows you the deployment proposal. When you agree, it calls springroll.deploy. SpringRoll answers with the app's URL and a placement receipt naming the provider, plan, estimated cost and any limit, and Claude follows springroll.deploy.status until the build is READY or fails.
Apps on the Direct workflow go straight to Production. Apps on the Staged workflow start in Development and need a person's approval to reach Production. Then choose who can open the app in its Access controls, and it appears in their App Portal.
From a Claude artifact to a deployed app
If Claude built your tool as an artifact, ask it to turn the artifact into a small project and deploy those files through SpringRoll. The artifact stays in claude.ai; the deployed app gets a named owner, an audience you choose, releases and an audit trail.
What SpringRoll adds to Claude
These are the SpringRoll tools Claude uses most when shipping an app.
Scroll sideways to see all columns. With the table focused, use the arrow keys.
| Tool | What it does |
|---|---|
| springroll.context | Shows which organization, identity and permissions the connection acts as, and which runtimes can take a deployment. |
| springroll.placement.preview | Scores where the app would run and what it would cost on managed Vercel or Cloudflare, without deploying anything. |
| springroll.deploy | Registers the project if it is new, takes its source from a pushed repository or the files in your folder, and deploys it. |
| springroll.deploy.status | Follows the build from QUEUED to READY or failure, with build logs when you ask for them. |
| springroll.deploy.promote | Moves a tested release to the next environment, such as UAT to Production, reusing the built artifact. |
| springroll.approval.submit, springroll.approval.get | Asks the configured reviewers for a decision, such as a production promotion, and reports where it stands. |
| springroll.app.list, springroll.app.get, springroll.app.update | Finds your apps, reads an app's registry record and updates its App Portal details, such as description and support contact. |
| springroll.security.audit, springroll.security.status | Runs your company's configured security checks on a release and reads the findings. |
| springroll.connect.data_products, springroll.connect.request_access | Lists governed company data and requests specific fields for one environment, for a data owner to approve. |
| springroll.app.record_prompts | Attaches the conversation that produced the app to its record, for the next maintainer and the reviewer. |
What Claude cannot do through SpringRoll
Some actions are deliberately out of an agent's reach, so connecting Claude does not let it bypass your team's rules.
- It cannot approve its own requests. Agent connections cannot record approval decisions.
- It never returns a credential, connection string or secret, and it cannot grant itself access to data.
- It cannot widen an app's audience, transfer ownership, change a production domain, roll back or retire an app without a person's approval.
- Every call is recorded in the organization's audit log against the person who authorized the connection.
Custom connector, Claude Code or a local server: which to use
SpringRoll runs at a URL, so in claude.ai and Claude Desktop it is always a custom connector. Claude Desktop's claude_desktop_config.json and desktop extensions are for local servers that run on your computer, and Anthropic notes that local servers are not available in claude.ai.
Claude Code keeps its own list of MCP servers. Add SpringRoll there with claude mcp add when you deploy from a terminal or IDE. Claude Code can also load your claude.ai connectors, after its own local, project, user and plugin servers.
Scroll sideways to see all columns. With the table focused, use the arrow keys.
| Where you work | How SpringRoll connects | Where you set it up |
|---|---|---|
| claude.ai, Claude Desktop and the mobile apps | Custom connector, from Anthropic's cloud | Customize, Connectors |
| Claude Code in a terminal or IDE | claude mcp add --transport http springroll https://springroll.dev/api/mcp | ~/.claude.json, or .mcp.json for a project |
| Claude Desktop with a program on your computer | Local server; not used for SpringRoll | claude_desktop_config.json or a desktop extension |
Troubleshooting SpringRoll in Claude
Match what you see.
- The sign-in page says the client could not be verified: SpringRoll could not fetch or accept Claude's published metadata at that moment. Try again shortly; if it persists, edit the connector and choose Register automatically under OAuth client.
- SpringRoll is not in a member's Connectors list: on Team and Enterprise, an Owner has to add it in Organization settings first.
- You cannot add SpringRoll on a Free account: Free accounts can add one custom connector. Remove the existing one or upgrade.
- Claude does not use SpringRoll: check that it is switched on under + and Connectors for this conversation.
- You signed in to the wrong workspace: disconnect SpringRoll in Customize, Connectors, then connect again and choose the right workspace.
- springroll.context reports that no runtime can take a deployment: deployments are not set up for that workspace yet. Ask a workspace administrator.
- A deployment is refused with POLICY_BLOCKED: ask Claude to run springroll.policy.check for the app, which names what must change.
- A build fails: ask Claude to read springroll.deploy.status with build logs, fix the cause, then deploy again.
What this guide was checked against
Claude steps were checked against Anthropic's help center article on custom connectors using remote MCP on 8 November 2026. SpringRoll's tools and limits come from its live server card on the same day. If a label in Claude differs, the values stay the same: the name SpringRoll, the URL and Claude's recommended sign-in settings.
Frequently asked questions
Is a Claude connector the same as an MCP server?
A custom connector is Claude's saved connection to a remote MCP server. SpringRoll is the server; the connector is how Claude reaches it.
Can I add SpringRoll to Claude on a Free plan?
Yes. Free accounts can add one custom connector. Team and Enterprise members connect it after an Owner adds it for the organization.
Does SpringRoll need an API key in Claude?
No. Add its URL and approve the connection in your browser. You can start as a guest without a SpringRoll login. The credential carries only your workspace permissions.
Can Claude approve its own deployment through SpringRoll?
No. Agent connections cannot record approval decisions. On the Staged workflow a configured reviewer approves the release.