If your Mastra project lives in GitHub, you can now automatically deploy changes to the Mastra platform.
Making CI-driven deployment easier with GitHub
When launching the new Mastra platform, we prioritized the current happy path for agents: all deploys ran through the CLI. While this allowed for local and CI-driven deployments, we knew that it could be easier than having to wire it all up yourself.
Now we’re running tens of thousands of deploys per month, and over half of them are from CI, so we decided it was time to make that even easier.
With our new GitHub app, you can connect any Mastra project to the platform and get new deployments on every merge to main.
Deploy on merge
Bring your own repo and we check that it's a Mastra project and link it to a new platform project in a couple of clicks.
Once a repository is connected, merging into main is the deploy. The platform listens for pushes to your branch, builds your project, and ships a new version — your Mastra server (the deployed runtime your agents and MCP servers run on) and your studio (the hosted workspace where you collaborate, evaluate, and iterate) both update from the same merge.
You can point server and studio at different branches if you want them on separate release cadences, and scope which file paths trigger a deploy so unrelated changes don't rebuild the world.
Get started
If you already have a Mastra project on the platform, open it, connect your GitHub repository, and merge a commit to main to watch it deploy.
For the full walkthrough, see the GitHub integration docs.
