Runway (runway.team)
Drive mobile release management from an AI agent — releases, checklists, fix requests and Build Distro. No tool submits a build to the App Store or Play Store, and none changes a rollout percentage. But two tools arm the automations that do.
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.
Connect Runway (runway.team) via MCP
https://mcp.runway.team/Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Runway (runway.team) Tools & Capabilities (56)
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,submitStepRunandsetSelectedBuildsStepRun; none is wrapped. Halting or accelerating a rollout is a dashboard action. - Two tools arm what the others cannot do directly.
update_scheduled_automationtoggles thesubmit,release,halt,promoteandresume_rolloutautomations, andset_automation_pausepauses 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,emailandoffline_access, and the RFC 9728 resource descriptor omitsscopes_supportedentirely. The only real boundary is API key scoping, which OAuth users do not get. trigger_ci_workflowspends 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
readOnlyHintis 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.txtcontains no occurrence of "MCP" or "Model Context Protocol", even though a dedicated MCP page exists atdocs.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
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.
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.
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.
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.
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.
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.
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.
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
- Runway OpenAPI specification,
mcpToolstag and REST operations (retrieved 2026-08-23). This is the document the nominatedapi-docs.runway.team/#tag/mcpToolspage renders; the fragment is not fetchable. · retrieved 2026-08-23 - Runway documentation, MCP server (retrieved 2026-08-23) · retrieved 2026-08-23
- Runway documentation, API overview and key scoping (retrieved 2026-08-23) · retrieved 2026-08-23
- Runway documentation, Types of automations (retrieved 2026-08-23) · retrieved 2026-08-23
- Runway documentation, Rollout and App submission — · (retrieved 2026-08-23) · retrieved 2026-08-23
- Runway documentation index and full corpus — · (retrieved 2026-08-23).
docs.runway.team/robots.txtcarriesContent-Signal: ai-train=yes, search=yes, ai-input=yes— the publisher expressly permits AI synthesis of this content. · retrieved 2026-08-23 - Live OAuth posture check: anonymous POST to
https://mcp.runway.team/returned 401 with aWWW-Authenticate: Bearer resource_metadataheader, and the RFC 9728 descriptor athttps://mcp.runway.team/.well-known/oauth-protected-resourcereturned 200 naming the authorization server (2026-08-23) · retrieved 2026-08-23 - Authorization server metadata (retrieved 2026-08-23) · retrieved 2026-08-23
- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-23 · retrieved 2026-08-23
- Runway support — <mailto:support@runway.team> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Developer Tools
- Developer
- Runway (runway.team)
- Tools
- 56
- Domain
- mcp.runway.team
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.