- Home
- Resources
- Integrations
- Runway (runway.team)
Claude Runway Team connectorWhat Claude can do in your Runway Team account.
The Claude Runway Team connector exposes 56 tools: 26 read, 30 write, 0 undocumented. They cover releases, builds, fix requests, checklists and automations for your mobile apps. Below: what Claude reads, what it moves forward, and what it can delete.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for a mobile team
Runway orchestrates a mobile app release: schedule, builds, fixes, checklists, store submission. Per its documentation, the connector lets an assistant drive Runway on your team's behalf. You ask Claude, and it checks a release's state or acts on it without you opening the dashboard.
Know where the version stands. To see where a release is, list_release_steps shows which step the release has reached, get_release_step gives one step's details, review timing included, and list_fix_requests lists pending fixes.
Get a fix in. For a fix, get_fix_request_form_fields_settings gives the form fields, create_fix_request opens the request, then approve_fix_request or reject_fix_request settles it.
Respond to an incident. During an incident, set_automation_pause pauses automations, reversibly, and developer_reject_submission pulls back a build that's submitted but not yet live.
What Claude doesn't do here: nothing fires on its own, and no release wakes Claude up. The sheet doesn't publish every tool Runway's docs describe. Some tools depend on app options such as Triage or FlightPaths. For automatic reactions, you want an automation tool; the Integrations page covers that side, and Claude connectors gathers the rest.
The vocabulary in one minute
Five words worth knowing before you connect Runway.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work on it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs on its own; the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before finishing something that changes your account, shown in the chat right when it matters.
- MCP
- The common standard behind connectors: it's what lets an assistant like Claude hold a conversation with an outside service.
Connect Runway Team to Claude in three steps
- 01
Find Runway Team
In Claude's settings, open Customize, then Connectors, and spot Runway in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it before each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in through the window the service opens itself. If the link breaks one day, hit Disconnect and connect again: that's the intended fix.
- 03
Read the authorization screen
Read the authorization screen before you approve. It belongs to the service, not to Claude, and it decides what the access covers. Per Runway, the connector then drives Runway on your team's behalf.
The 56 tools of the Claude Runway Team connector
Runway (runway.team) gives Claude 56 tools: 26 that read your account, 30 that change something in it.
Two groups, per the tool list Runway publishes: what Claude reads, and what it creates, updates, triggers or deletes. Names stay as Claude shows them.
- 26 read
- 30 write
Tools index
- 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
- 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
- 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
- ignore_unignore_feature_readiness_items
- 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
What Claude reads (26)
26 toolsTwenty-six tools that look at apps, releases, steps, builds, fixes and groups.
get_app
Opens the details of an app tracked in Runway. It's a natural starting point before you look at its releases, steps or integrations.
get_bucket_build
Shows the details of one build stored in Build Distro, where Runway keeps builds grouped into buckets.
get_build_bucket
Returns the details of one Build Distro bucket. It describes the bucket itself; list_bucket_builds lists what's inside.
get_bucket_build opens one and list_bucket_builds lists them all.get_checklist_item
Looks up the details of one checklist item on a release, when the full list isn't enough.
list_release_checklist_items is the tool to call.get_custom_ci_build_additional_file_download
Returns a signed download URL for a supplemental file attached to a Custom CI build. The file stays with Runway; Claude passes you the link.
get_custom_ci_build_artifact_download
Generates a signed download URL for the primary binary artifact of a Custom CI (MRM) build: the build file itself, not a supplemental one.
get_fix_request
Checks one fix request's current state: its status, who asked for it, and the approvals it still needs.
list_fix_requests gives the overview.get_fix_request_form_fields_settings
Returns the app's configured fix request form fields, with their IDs and any required or minimum-length rules: the answers a fix request expects.
get_org
Pulls your Runway organization's details. It's the widest view, above the apps.
get_org_metrics
Aggregates metrics across every app and release in the organization over a past date range: release durations, review rejection rates, build counts and more.
get_release
Fetches the details of one release, beyond the basic information the release list gives.
list_release_steps and get_release_step go further, and the release list itself only gives basic information.get_release_step
Returns details for a release step by type: feature readiness, release candidate builds and the other step types the docs describe, each with its own data. Per Runway, review timing comes from here.
get_release_timeline_events
Returns a release's timeline events, to see what happened and in what order. The docs say not to use them to compute durations.
get_release_step, per the docs.get_schedule_cadence
Gives the app's release cadence (weekly, biweekly or monthly), its target kickoff, submit and release days and times, and its time zone.
update_scheduled_automation.get_user_group
Brings up the details of one user group in the organization.
list_user_groups.list_apps
Lists every app in a Runway organization, so Claude knows which app you mean, under its exact name, before it goes after that app's releases.
list_bucket_builds
Lists the builds in a Build Distro bucket, where get_build_bucket only describes the bucket itself.
get_build_bucket, and a single build's from get_bucket_build.list_build_buckets
Lists the Build Distro buckets for an app, which is how you find the one you're after.
list_apps if needed.list_fix_requests
Goes through the fix requests on a release: status, requester, approvals so far and the work items each one covers.
get_fix_request.list_integration_builds
Shows the builds uploaded to a Custom CI (MRM) integration for a given release.
list_integrations
Lists the integrations installed on an app: CI providers, app stores, version control and others hooked into Runway.
list_release_checklist_items
Lists every checklist item on a release in a single view.
get_checklist_item, and ticking it off is done by update_checklist_item_status, in the other group.list_release_steps
Gives a lightweight list of a release's steps, with each step's ID, type and status. For one step's details, get_release_step takes over.
list_releases
Lists an app's releases with basic release-level information only. For the full details of one of them, get_release takes over.
list_triage_issues
Pulls up an app's triage issues, with optional filters for version, status, source, owner, reporter, destination and a free-text search.
list_user_groups
Lists the user groups in a Runway organization.
get_user_group, and only groups of your own organization are listed.What Claude changes (30)
30 toolsThirty tools that create, update, trigger or delete. No source spells out their confirmation: the general rule below applies.
approve_fix_request
Approval: see the ruleApproves a fix request on a release, one of the two ways to settle a request opened with create_fix_request.
create_approval
Approval: see the ruleCreates an approval item on a release, alongside its checklist and regression items.
create_build_bucket
Approval: see the ruleCreates a bucket in Build Distro, the part of Runway where builds are grouped into buckets.
create_checklist_item
Approval: see the ruleCreates a generic checklist item on a release step, as opposed to regression testing items and approval items.
create_fix_request
Approval: see the ruleCreates a fix request on a release, flagging a pull request, commit or ticket as a fix that needs to land, with answers to the app's form fields.
create_regression_items
Approval: see the ruleCreates one or more regression testing items on a release in a single call.
create_regression_step_checklist_item
Approval: see the ruleCreates a checklist item directly on the release's regression testing step.
create_release
Approval: see the ruleCreates a release for an app in Runway.
create_triage_issue
Approval: see the ruleCreates a triage issue on an app, so a reported problem is tracked in Runway.
create_user_group
Approval: see the ruleCreates a user group in the Runway organization.
delete_build
Approval: see the ruleDeletes a build from a Build Distro bucket.
delete_group
Approval: see the ruleDeletes a user group from the Runway organization.
delete_release
Approval: see the ruleDeletes a release from Runway.
skip_release is the softer move the docs list.developer_reject_submission
Approval: see the ruleCancels or pulls back a build that's been submitted to the store but not yet released, a developer reject.
ignore_unignore_feature_readiness_items
Approval: see the ruleIgnores or un-ignores Feature Readiness work items on a release.
reject_fix_request
Approval: see the ruleRejects a fix request on a release, the other way to settle a request opened with create_fix_request.
set_automation_pause
Approval: see the ruleTemporarily pauses or resumes an app's automations, reversibly, during a hotfix, a code freeze or an incident.
skip_release
Approval: see the ruleSkips a release.
unskip_release reverses a skip, per Runway's tool list.trigger_ci_workflow
Approval: see the ruleStarts the CI build workflow for a release's release-candidate step.
unskip_release
Approval: see the ruleUnskips a release that had been skipped.
update_bucket_build
Approval: see the ruleUpdates a build stored in Build Distro.
delete_build.update_build_bucket
Approval: see the ruleUpdates an existing Build Distro bucket.
get_build_bucket.update_checklist_item_comment
Approval: see the ruleUpdates the comment on a checklist item.
update_checklist_item_status.update_checklist_item_status
Approval: see the ruleUpdates the status of a checklist item on a release.
update_regression_status
Approval: see the ruleUpdates the regression testing status of a release.
update_release
Approval: see the ruleUpdates a release that already exists in Runway.
update_release_approval
Approval: see the ruleApproves or unapproves metadata or screenshots on a release.
update_release_metadata.update_release_metadata
Approval: see the ruleUpdates App Store or Play Store listing metadata per locale: release notes, keywords, description and more.
update_scheduled_automation
Approval: see the ruleEnables or disables a scheduled release automation: kickoff, submit, release, halt, promote or resume rollout.
update_user_group
Approval: see the ruleUpdates a user group in the organization.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. The request shows up in the chat, right when it matters.
No source says whether Claude asks before deleting a release, pulling back a submission or switching off an automation: that default rule covers all thirty write tools. On a Team or Enterprise workspace, owners decide whether a member can let certain actions through without being asked again, and they can shut off a connector's writes for the whole organization. Nobody overrides that from their own account.
Which plans include it
Out of 819 sheets in the official directory, none shows availability by plan. Connector by connector, the answer isn't published anywhere: it's a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before each member can connect. For the current status, the Runway sheet in the official directory is where to look.
Where Runway stops inside Claude
A connector isn't an automation. Claude calls these tools while it answers you: nothing starts when a build lands or a review wraps up.
Only the publisher documents this connector, in the tool list of its API docs: neither Claude's help center nor Anthropic's docs mention it. Runway's docs also describe tools missing from the sheet, which this page leaves out because the sheet doesn't list them. This page sticks to what the sheet lists, tool by tool. The partner badge isn't a security audit, and Anthropic doesn't guarantee a publisher's tools behave as described.
Need help connecting Runway (runway.team) to Claude?
A person reads every message.