Runway (runway.team)

Drive mobile release management: releases, checklists, fix requests, Build Distro.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Runway (runway.team) connector does

The Runway MCP server connects Runway — a mobile release management platform that orchestrates App Store and Play Store releases — to Claude, ChatGPT and any MCP-compatible agent. Anthropic lists 56 tools covering releases, checklists, approvals, fix requests, triage and Build Distro. No tool submits a build to a store or moves a rollout percentage.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Runway (runway.team) tools (56)

  • approve_fix_request
  • create_approval
  • create_build_bucket
  • create_checklist_item
  • create_fix_request
  • create_regression_items
  • create_regression_step_checklist_item
  • create_release
  • create_triage_issue
  • create_user_group
  • delete_build
  • delete_group
  • delete_release
  • developer_reject_submission
  • get_app
  • get_bucket_build
  • get_build_bucket
  • get_checklist_item
  • get_custom_ci_build_additional_file_download
  • get_custom_ci_build_artifact_download
  • get_fix_request
  • get_fix_request_form_fields_settings
  • get_org
  • get_org_metrics
  • get_release
  • get_release_step
  • get_release_timeline_events
  • get_schedule_cadence
  • get_user_group
  • ignore_unignore_feature_readiness_items
  • list_apps
  • list_bucket_builds
  • list_build_buckets
  • list_fix_requests
  • list_integration_builds
  • list_integrations
  • list_release_checklist_items
  • list_release_steps
  • list_releases
  • list_triage_issues
  • list_user_groups
  • reject_fix_request
  • set_automation_pause
  • skip_release
  • trigger_ci_workflow
  • unskip_release
  • update_bucket_build
  • update_build_bucket
  • update_checklist_item_comment
  • update_checklist_item_status
  • update_regression_status
  • update_release
  • update_release_approval
  • update_release_metadata
  • update_scheduled_automation
  • update_user_group

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • No store submission and no rollout control. Neither capability exists in the tool surface. Runway's REST API has submitRelease, submitStepRun and setSelectedBuildsStepRun; none is wrapped. Halting or accelerating a rollout is a dashboard action.
  • Two tools arm what the others cannot do directly. update_scheduled_automation toggles the submit, release, halt, promote and resume_rollout automations, and set_automation_pause pauses or resumes all of them at once. These are the tools to withhold from blanket approval.
  • Anthropic's listing is nine tools short of Runway's own. Most notably toggle_release_feature_flag, which Runway states affects production by propagating to your feature flag provider. Plan for 65 tools rather than 56.
  • OAuth grants no application boundary. The authorization server advertises only openid, profile, email and offline_access, and the RFC 9728 resource descriptor omits scopes_supported entirely. The only real boundary is API key scoping, which OAuth users do not get.
  • trigger_ci_workflow spends CI minutes and nothing observes the spend. No tool in the listing reports build cost, quota or remaining credit. Runway restricts the tool to FlightPaths-enabled apps but publishes no rate for a triggered build.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or readOnlyHint is published here. Tool descriptions come from Runway's OpenAPI specification.
  • Enterprise plan gate. Runway states the REST API — and therefore key-based MCP access — is available for Enterprise teams and above. Triage tools additionally require Triage enabled on the app.
  • Rate limits are documented for the REST API, not the MCP server. Runway publishes 5 requests per second and 8,000 per day for its REST API. Whether the same ceiling applies to MCP tool calls is not stated; treat it as the likely limit rather than a confirmed one.
  • Runway's own docs corpus does not mention MCP. Its 392KB llms-full.txt contains no occurrence of "MCP" or "Model Context Protocol", even though a dedicated MCP page exists at docs.runway.team/api/mcp-server. An agent relying on that corpus would conclude no connector exists.
  • The connector's documentation link is a fragment. Anthropic's directory nominates api-docs.runway.team/#tag/mcpTools, which is a client-rendered Redoc page. The tool list is reachable only by reading the OpenAPI JSON the page fetches.

Frequently asked questions

Can the Runway MCP server submit my app to the App Store or Play Store?

No. Runway's REST API has a submit endpoint, submitRelease, and its tool list wraps no such tool. The closest name, developer_reject_submission, pulls a submitted build back rather than pushing one. Runway documents submission as an automation or a manual dashboard action, so the store review queue is not reachable by a direct tool call.

Can an agent change my staged rollout percentage or halt a rollout?

No tool sets a percentage, halts a rollout or resumes one. Runway exposes rollout state as read data through get_release_step, which returns userFraction, dayNumber and adoption rates. Runway documents halt and release-to-100% as dashboard actions on the Rollout step. The listed tools observe a rollout; they do not steer one.

So which Runway tools actually reach production users?

Two, indirectly: update_scheduled_automation and set_automation_pause. Runway's schedule automations include submit, release, halt and resume_rollout, and update_scheduled_automation turns any of them on or off. Enabling submit or release arms an unattended path to the store; pausing halt disarms the safety automation that stops an unhealthy rollout.

Does the Runway connector reach signing keys or App Store Connect credentials?

No. Runway's REST API can rotate Apple and Google integration credentials through updateIntegrationAuth, which accepts a .p8 key or a service account JSON file, and no MCP tool wraps it. Signing keys are uploaded in app settings only. Runway states signing keys sit behind a VPC and are inaccessible from the open internet.

What OAuth permissions does the Runway MCP server request?

Only identity claims. Runway's authorization server, hosted on WorkOS AuthKit, advertised openid, profile, email and offline_access on 2026-08-23, and the server's RFC 9728 resource descriptor declares no scopes_supported at all. Nothing in the OAuth grant separates reading a release from deleting one.

How do I limit what an agent can do in Runway?

Use API key scoping rather than OAuth. Runway documents three fields on an API key: group scopes granting a user group's allowed actions, app scopes limiting which apps it touches, and an admin scope granting everything. Runway states that leaving group scopes empty and admin unchecked produces an org-wide read-only key.

Which Runway MCP tools can delete data?

Three: delete_release removes a Runway release, delete_group removes a user group, and delete_build removes a build from a Build Distro bucket. All three act inside Runway. None removes anything from the App Store or Play Store, and none affects a version already published to users.

Does the Runway connector need a paid plan?

Yes. Runway states its REST API is available for Enterprise teams and above, and its MCP docs say the server uses the same API key authentication as the REST API. Admin permissions are required to create a key. Triage tools additionally require Triage to be enabled on the app.

Sources

More Developer Tools connectors

  • Base44

    Build and edit Base44 apps from an AI assistant, and query data your app's users submit.

  • CircleCI

    Diagnose failed builds, read job logs, inspect test results and rerun or roll back deployments from your AI assistant.

  • Claude Managed Agents

    Create, run, monitor and debug Anthropic's Claude Managed Agents from inside Claude itself.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Runway (runway.team) to work.

Connect Runway (runway.team) once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.