Resources · Claude connector

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

Overview

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.

Vocabulary

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

Connect Runway Team to Claude in three steps

  1. 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.

  2. 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.

  3. 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.

Tools

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

What Claude reads (26)

26 tools

Twenty-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.

When it helps
you need to see how an app is set up in Runway before working on its releases.

Sourceapi-docs.runway.team · October 1, 2026 ↗

get_bucket_build

Shows the details of one build stored in Build Distro, where Runway keeps builds grouped into buckets.

When it helps
you need the details of a specific build rather than the whole bucket's list.
Watch out
only builds in buckets your Runway account can reach show up, since Claude works with your rights.

Sourceapi-docs.runway.team · October 1, 2026 ↗

get_build_bucket

Returns the details of one Build Distro bucket. It describes the bucket itself; list_bucket_builds lists what's inside.

When it helps
you want a bucket's details before putting a build in it.
Watch out
for the builds themselves, get_bucket_build opens one and list_bucket_builds lists them all.

Sourceapi-docs.runway.team · October 1, 2026 ↗

get_checklist_item

Looks up the details of one checklist item on a release, when the full list isn't enough.

When it helps
you need to know exactly where a single checklist item stands.
Watch out
for every item on the release at once, list_release_checklist_items is the tool to call.

Sourceapi-docs.runway.team · October 1, 2026 ↗

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.

When it helps
you need a supplemental file attached to a build, not the build itself.

Sourceapi-docs.runway.team · October 1, 2026 ↗

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.

When it helps
you need the main binary of a build to install or inspect it.

Sourceapi-docs.runway.team · October 1, 2026 ↗

get_fix_request

Checks one fix request's current state: its status, who asked for it, and the approvals it still needs.

When it helps
someone wants to know why a fix hasn't made it into the release yet.
Watch out
for all the fix requests on a release, list_fix_requests gives the overview.

Sourceapi-docs.runway.team · October 1, 2026 ↗

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.

When it helps
a fix request is about to be opened and its form has to be filled in correctly.

Sourceapi-docs.runway.team · October 1, 2026 ↗

get_org

Pulls your Runway organization's details. It's the widest view, above the apps.

When it helps
you want to confirm which organization the connection belongs to before doing anything.
Watch out
the connection acts on your team's behalf, per Runway, so the organization you see is the one your account belongs to.

Sourceapi-docs.runway.team · October 1, 2026 ↗

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.

When it helps
you want a view of how releases have gone across the whole organization over a period.

Sourceapi-docs.runway.team · October 1, 2026 ↗

get_release

Fetches the details of one release, beyond the basic information the release list gives.

When it helps
you need the full details of a particular version.
Watch out
for a step-by-step view, list_release_steps and get_release_step go further, and the release list itself only gives basic information.

Sourceapi-docs.runway.team · October 1, 2026 ↗

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.

When it helps
you want to know how long a version waited in review.

Sourceapi-docs.runway.team · October 1, 2026 ↗

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.

When it helps
the sequence of events on a release has to be rebuilt.
Watch out
review timing comes from get_release_step, per the docs.

Sourceapi-docs.runway.team · October 1, 2026 ↗

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.

When it helps
you need to know when the next submission is planned and on which day.
Watch out
the cadence describes the plan; whether each scheduled automation is on is another matter, handled by update_scheduled_automation.

Sourceapi-docs.runway.team · October 1, 2026 ↗

get_user_group

Brings up the details of one user group in the organization.

When it helps
you need a group's details before giving it a role in a release.
Watch out
only groups in your own organization are visible, with your account's rights. The full list comes from list_user_groups.

Sourceapi-docs.runway.team · October 1, 2026 ↗

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.

When it helps
several apps share the organization and you need the exact name of one.

Sourceapi-docs.runway.team · October 1, 2026 ↗

list_bucket_builds

Lists the builds in a Build Distro bucket, where get_build_bucket only describes the bucket itself.

When it helps
you want to see which builds a bucket actually holds.
Watch out
the bucket's own details come from get_build_bucket, and a single build's from get_bucket_build.

Sourceapi-docs.runway.team · October 1, 2026 ↗

list_build_buckets

Lists the Build Distro buckets for an app, which is how you find the one you're after.

When it helps
you're looking for the right bucket before working on a build.
Watch out
buckets are listed per app, so the app has to be known first, through list_apps if needed.

Sourceapi-docs.runway.team · October 1, 2026 ↗

list_fix_requests

Goes through the fix requests on a release: status, requester, approvals so far and the work items each one covers.

When it helps
before submission, you want every fix still waiting and the approvals each one lacks.
Watch out
one request's state in detail comes from get_fix_request.

Sourceapi-docs.runway.team · October 1, 2026 ↗

list_integration_builds

Shows the builds uploaded to a Custom CI (MRM) integration for a given release.

When it helps
you want to check which builds the CI integration has sent for a release.
Watch out
the download links of a Custom CI build come from the two dedicated download tools, not from this list.

Sourceapi-docs.runway.team · October 1, 2026 ↗

list_integrations

Lists the integrations installed on an app: CI providers, app stores, version control and others hooked into Runway.

When it helps
you want to know whether an app is already linked to a CI provider or a store.
Watch out
the CI tool only starts a build on FlightPaths-enabled apps, per Runway.

Sourceapi-docs.runway.team · October 1, 2026 ↗

list_release_checklist_items

Lists every checklist item on a release in a single view.

When it helps
you want to see what's left on a release's checklist before submission.
Watch out
one item's details come from get_checklist_item, and ticking it off is done by update_checklist_item_status, in the other group.

Sourceapi-docs.runway.team · October 1, 2026 ↗

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.

When it helps
you want to see in one go which step a release has reached.
Watch out
per the docs, it returns each step's ID, type and status, and nothing more.

Sourceapi-docs.runway.team · October 1, 2026 ↗

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.

When it helps
you need to find a version in an app's release list.
Watch out
the list only carries release-level basics, by design.

Sourceapi-docs.runway.team · October 1, 2026 ↗

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.

When it helps
you want the open issues reported on one version.
Watch out
the triage tools only work with the Triage option on.

Sourceapi-docs.runway.team · October 1, 2026 ↗

list_user_groups

Lists the user groups in a Runway organization.

When it helps
you want to know which groups already exist in the organization and what they're called.
Watch out
one group's details come from get_user_group, and only groups of your own organization are listed.

Sourceapi-docs.runway.team · October 1, 2026 ↗

What Claude changes (30)

30 tools

Thirty tools that create, update, trigger or delete. No source spells out their confirmation: the general rule below applies.

approve_fix_request

Approval: see the rule

Approves a fix request on a release, one of the two ways to settle a request opened with create_fix_request.

What Claude asks for
no source describes a confirmation specific to approving a fix request; the general rule applies.
When it helps
a fix request is waiting for your approval on the current release.

Sourceapi-docs.runway.team · October 1, 2026 ↗

create_approval

Approval: see the rule

Creates an approval item on a release, alongside its checklist and regression items.

What Claude asks for
for creating an approval item, nothing is documented: the general rule is what counts.
When it helps
a release needs an approval item that isn't there yet.

Sourceapi-docs.runway.team · October 1, 2026 ↗

create_build_bucket

Approval: see the rule

Creates a bucket in Build Distro, the part of Runway where builds are grouped into buckets.

What Claude asks for
Runway's docs say nothing about a sign-off for creating a bucket, so the default rule holds.
When it helps
builds need a new bucket of their own.

Sourceapi-docs.runway.team · October 1, 2026 ↗

create_checklist_item

Approval: see the rule

Creates a generic checklist item on a release step, as opposed to regression testing items and approval items.

What Claude asks for
no source describes a confirmation specific to adding a generic checklist item; the general rule applies.
When it helps
a step needs a checklist item that is neither a regression test nor an approval.

Sourceapi-docs.runway.team · October 1, 2026 ↗

create_fix_request

Approval: see the rule

Creates 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.

What Claude asks for
for opening a fix request, nothing is documented: the general rule is what counts.
When it helps
a change has to land in the release that's in progress.

Sourceapi-docs.runway.team · October 1, 2026 ↗

create_regression_items

Approval: see the rule

Creates one or more regression testing items on a release in a single call.

What Claude asks for
Runway's docs say nothing about a sign-off for creating regression items, so the default rule holds.
When it helps
several regression tests have to be added to a release at once.

Sourceapi-docs.runway.team · October 1, 2026 ↗

create_regression_step_checklist_item

Approval: see the rule

Creates a checklist item directly on the release's regression testing step.

What Claude asks for
no source describes a confirmation specific to adding an item to the regression step; the general rule applies.
When it helps
the regression step needs one more item to check.

Sourceapi-docs.runway.team · October 1, 2026 ↗

create_triage_issue

Approval: see the rule

Creates a triage issue on an app, so a reported problem is tracked in Runway.

What Claude asks for
Runway's docs say nothing about a sign-off for creating a triage issue, so the default rule holds.
When it helps
a problem has been reported and has to be logged for triage.
Watch out
Triage has to be enabled on the app.

Sourceapi-docs.runway.team · October 1, 2026 ↗

create_user_group

Approval: see the rule

Creates a user group in the Runway organization.

What Claude asks for
no source describes a confirmation specific to creating a user group; the general rule applies.
When it helps
the organization needs a group that doesn't exist yet.
Watch out
the group is created for the whole organization, not just for you.

Sourceapi-docs.runway.team · October 1, 2026 ↗

delete_build

Approval: see the rule

Deletes a build from a Build Distro bucket.

What Claude asks for
for deleting a build, nothing is documented: the general rule is what counts.
When it helps
a build should no longer be in its bucket.
Watch out
Runway's documentation mentions no way to undo the deletion.

Sourceapi-docs.runway.team · October 1, 2026 ↗

delete_group

Approval: see the rule

Deletes a user group from the Runway organization.

What Claude asks for
Runway's docs say nothing about a sign-off for deleting a group, so the default rule holds.
When it helps
a group has no reason to exist anymore.
Watch out
nothing in the docs describes a way to restore a deleted group.

Sourceapi-docs.runway.team · October 1, 2026 ↗

delete_release

Approval: see the rule

Deletes a release from Runway.

What Claude asks for
no source describes a confirmation specific to deleting a release; the general rule applies.
When it helps
a release was created that shouldn't exist.
Watch out
no undo is described; skipping a release with skip_release is the softer move the docs list.

Sourceapi-docs.runway.team · October 1, 2026 ↗

developer_reject_submission

Approval: see the rule

Cancels or pulls back a build that's been submitted to the store but not yet released, a developer reject.

What Claude asks for
for pulling back a submission, nothing is documented: the general rule is what counts.
When it helps
a build submitted to the store must not be released.

Sourceapi-docs.runway.team · October 1, 2026 ↗

ignore_unignore_feature_readiness_items

Approval: see the rule

Ignores or un-ignores Feature Readiness work items on a release.

What Claude asks for
Runway's docs say nothing about a sign-off for ignoring or restoring readiness items, so the default rule holds.
When it helps
a work item tracked for a release has nothing to do with that version.

Sourceapi-docs.runway.team · October 1, 2026 ↗

reject_fix_request

Approval: see the rule

Rejects a fix request on a release, the other way to settle a request opened with create_fix_request.

What Claude asks for
no source describes a confirmation specific to rejecting a fix request; the general rule applies.
When it helps
a proposed fix should not go into this release.

Sourceapi-docs.runway.team · October 1, 2026 ↗

set_automation_pause

Approval: see the rule

Temporarily pauses or resumes an app's automations, reversibly, during a hotfix, a code freeze or an incident.

What Claude asks for
for pausing automations, nothing is documented: the general rule is what counts.
When it helps
automations have to stop for a while, during a hotfix, a code freeze or an incident.
Watch out
this is separate from each automation's saved configuration.

Sourceapi-docs.runway.team · October 1, 2026 ↗

skip_release

Approval: see the rule

Skips a release.

What Claude asks for
Runway's docs say nothing about a sign-off for skipping a release, so the default rule holds.
When it helps
a planned release is not going to ship.
Watch out
unskip_release reverses a skip, per Runway's tool list.

Sourceapi-docs.runway.team · October 1, 2026 ↗

trigger_ci_workflow

Approval: see the rule

Starts the CI build workflow for a release's release-candidate step.

What Claude asks for
no source describes a confirmation specific to kicking off a build; the general rule applies.
When it helps
a new release candidate build is needed.
Watch out
FlightPaths-enabled apps only.

Sourceapi-docs.runway.team · October 1, 2026 ↗

unskip_release

Approval: see the rule

Unskips a release that had been skipped.

What Claude asks for
for unskipping a release, nothing is documented: the general rule is what counts.
When it helps
a release that was skipped has to ship after all.
Watch out
it only applies to a release that was skipped before.

Sourceapi-docs.runway.team · October 1, 2026 ↗

update_bucket_build

Approval: see the rule

Updates a build stored in Build Distro.

What Claude asks for
Runway's docs say nothing about a sign-off for updating a build, so the default rule holds.
When it helps
a build's details in its bucket need changing.
Watch out
deleting a build from its bucket is a separate tool, delete_build.

Sourceapi-docs.runway.team · October 1, 2026 ↗

update_build_bucket

Approval: see the rule

Updates an existing Build Distro bucket.

What Claude asks for
no source describes a confirmation specific to updating a bucket; the general rule applies.
When it helps
a bucket's settings need changing.
Watch out
the docs give no detail on which bucket settings can change; the bucket's current details come from get_build_bucket.

Sourceapi-docs.runway.team · October 1, 2026 ↗

update_checklist_item_comment

Approval: see the rule

Updates the comment on a checklist item.

What Claude asks for
for a checklist comment, nothing is documented: the general rule is what counts.
When it helps
a checklist item needs a note explaining what was checked.
Watch out
the item's status is changed by another tool, update_checklist_item_status.

Sourceapi-docs.runway.team · October 1, 2026 ↗

update_checklist_item_status

Approval: see the rule

Updates the status of a checklist item on a release.

What Claude asks for
Runway's docs say nothing about a sign-off for a checklist status, so the default rule holds.
When it helps
a checklist item is done and its status has to say so.

Sourceapi-docs.runway.team · October 1, 2026 ↗

update_regression_status

Approval: see the rule

Updates the regression testing status of a release.

What Claude asks for
no source describes a confirmation specific to the regression status; the general rule applies.
When it helps
regression testing is over and the release's status has to reflect it.

Sourceapi-docs.runway.team · October 1, 2026 ↗

update_release

Approval: see the rule

Updates a release that already exists in Runway.

What Claude asks for
for updating a release, nothing is documented: the general rule is what counts.
When it helps
something about a planned version has changed.
Watch out
the docs don't list which release fields this tool can change.

Sourceapi-docs.runway.team · October 1, 2026 ↗

update_release_approval

Approval: see the rule

Approves or unapproves metadata or screenshots on a release.

What Claude asks for
Runway's docs say nothing about a sign-off for approving metadata, so the default rule holds.
When it helps
a release's metadata or screenshots have been reviewed.
Watch out
the store listing text itself is changed by update_release_metadata.

Sourceapi-docs.runway.team · October 1, 2026 ↗

update_release_metadata

Approval: see the rule

Updates App Store or Play Store listing metadata per locale: release notes, keywords, description and more.

What Claude asks for
no source describes a confirmation specific to the store listing metadata; the general rule applies.
When it helps
the listing text for one language has to change before submission.

Sourceapi-docs.runway.team · October 1, 2026 ↗

update_scheduled_automation

Approval: see the rule

Enables or disables a scheduled release automation: kickoff, submit, release, halt, promote or resume rollout.

What Claude asks for
for a scheduled automation, nothing is documented: the general rule is what counts.
When it helps
one scheduled step should run by hand from now on, or go back to automatic.
Watch out
this changes the saved configuration, unlike the temporary pause.

Sourceapi-docs.runway.team · October 1, 2026 ↗

update_user_group

Approval: see the rule

Updates a user group in the organization.

What Claude asks for
Runway's docs say nothing about a sign-off for updating a group, so the default rule holds.
When it helps
a group's members or details have changed.
Watch out
the group is shared across the organization, so the change applies to everyone in it.

Sourceapi-docs.runway.team · October 1, 2026 ↗

Approvals

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.

Plans

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.

Limits

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

Need help connecting Runway (runway.team) to Claude?

A person reads every message.

FAQ

FAQ about the Claude Runway Team connector

01What can Claude do with the Runway Team connector?
Claude can track and push your mobile app releases forward from the conversation. It looks up the organization, apps, releases, their steps and timelines, checklists, fix requests, Build Distro builds and user groups. It can also create or delete releases, open, approve or reject fixes, tick checklists, update store metadata, kick off CI and pause automations. Every tool on the sheet is described in Runway's docs. Each tool has its own note further up this page.
02Can Claude delete a release or pull back a submission?
Yes. Among the thirty write tools, some delete a release, a distributed build or a user group, and another pulls back a build that's been submitted to the store but not yet released. Others skip a release, switch off a scheduled automation or pause every automation. Runway's documentation mentions no undo for deletions, so read each request of that kind closely before you confirm. Those moves go through under your Runway identity.
03Does Claude ask before acting on a release?
By default, Claude asks for confirmation before any action it takes on an account for you. No source describes a confirmation specific to a Runway tool, so that default rule covers creates, updates, deletions and triggers. On a Team or Enterprise workspace, owners can decide whether some actions go through without a prompt, and they can shut off every write for the whole organization. Members can't override that themselves. The general rule is the only reference here.
04Which plans is it available on?
No official source publishes availability by plan, connector by connector, and none of the 819 directory sheets shows it. The general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner turning them on first on Team and Enterprise. The Runway sheet in the official directory remains the only place that shows the current status for your account. Check it before you plan around the connector.
05Does Claude see every app in my Runway organization?
It sees what your Runway account sees, and nothing more. Claude works with the rights of the person who connected it: an app or release that's closed to you in Runway stays closed in the conversation. Per the docs, the connector acts on your team's behalf, which makes those rights all the more important. On a Team or Enterprise workspace, an owner can also restrict what the connector may do.
06Why can't Claude kick off CI or create a triage issue?
Because those tools depend on app options in Runway. Starting the CI workflow only works on apps with FlightPaths enabled, and the triage tools assume Triage is enabled on the app. If those options aren't in place, the matching tools won't help. That's something to check on the Runway side, with whoever administers the app, before trying again in Claude. Runway's docs spell this out tool by tool, so the limits are stated in advance.
07Claude or an automation tool for managing releases?
They don't do the same job. With the connector, you ask Claude to check or advance a release, and it acts at the moment you ask. Nothing runs by itself afterwards: no tool wakes up when a build lands or a review ends. Runway has its own scheduled automations, and an automation tool handles reactions to outside events; the approaches complement each other. Use each for what it's good at.