Sign inCreate an account
Create an account
Documentation

Search documentation

Try deployment, Codex, or data access.

    Browse documentation

    Deploy an app from an OAuth-capable MCP client

    SpringRoll exposes a remote MCP endpoint for clients that support streamable HTTP and a compatible OAuth authorization flow. The connection URL supplies discovery; workspace operations act within an authorized member's permissions. Start by connecting the client you use, then inspect the proposed deployment and follow it to a real build result.

    By Updated

    On this page

    Can any MCP client deploy through SpringRoll?

    Use a remote HTTP MCP client that supports OAuth. It needs to reach SpringRoll, authorize the intended workspace and supply the source and runtime details for the app. Choose the client-specific instructions below.

    https://springroll.dev/api/mcp

    Step 1: choose a connection your client supports

    Check that the client can register a remote HTTP server. Use SpringRoll's MCP endpoint from the connection catalog. A hosted client cannot reach the localhost address of a project on your laptop.

    Step 2: distinguish discovery from authorization

    Finding the public tools confirms that the server is reachable. A workspace action needs a signed-in member. In the browser, check the account and workspace before approving the connection.

    Step 3: ask for a reviewable deployment

    Give the agent the source project, app owner, build command, output path and required services. Ask which environment will receive the release. Authorize only the work you reviewed.

    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.

    Step 4: follow the actual deployment status

    Keep the release and deployment IDs. Follow the build until READY or failure. If it fails, inspect the error and correct the source or build settings before retrying. After READY, open the app and complete its main task.

    Why the agent cannot approve its own work

    The connection acts with the member's permissions. When policy requires a human reviewer, show that person the release, environment and requested change. An agent retry cannot supply the decision.

    Verify what a colleague can open

    From another account, open the link for the intended environment. Then check an account outside the audience, the direct provider URL, and a server operation the colleague must not perform.

    Keep the connection useful after the first release

    Before an update, check the workspace, current tools and last deployment result. If a builder leaves, transfer app ownership and revoke unneeded personal authorizations.

    Connect Claude Code

    From the app's project folder, register the remote server with the command below. Open /mcp in Claude Code, sign in to SpringRoll, choose the workspace that owns this project and authorize the connection. The MCP connection supplies the tools. Install the optional SpringRoll skill separately if you want the /springroll deploy command.

    claude mcp add --transport http springroll https://springroll.dev/api/mcp

    Connect Codex

    Run this in the repository that contains the app. It registers SpringRoll's HTTP MCP endpoint. Complete browser authorization for the intended workspace. If credentials are still pending, use the Codex MCP login command. Ask Codex to inspect the build command, runtime, environment variables and storage before requesting a release.

    codex mcp add springroll --url https://springroll.dev/api/mcp