AI assistants are showing up everywhere in the mobile engineering workflow. In your editor, in your terminal, in the tabs you already had open. Ask one to write a function and it does a pretty good job. Ask it about your next release and you get something that sounds confident and is mostly wrong.
That's not the model's fault. And you don't solve it by hooking your agent up to every individual MCP, either. You'd be pulling signals from App Store Connect, Play Console, your CI, your version control — but you'd still be missing the additional layer that combines all those signals in the right way to give you the complete picture: a state machine. Runway already builds it. The Runway MCP exposes it.
The result: the AI tools your team already uses can finally answer questions about what's shipping, what's stuck, and what's about to change, instead of guessing.
In this session, we will walk through it end to end: how to connect the Runway MCP in under two minutes, real release scenarios where it makes a difference, what's coming next, and live Q&A.
We'll cover:
- What MCP is, and why it matters specifically for mobile release work
- A live setup — connecting the Runway MCP to your AI assistant of choice
- Real release scenarios, walked through in real time
- What's next on the MCP roadmap, and how to get access
- Open Q&A
