Ship releases without touching your browser
Trigger a release from your editor and let MCP handle the git log, tagging, MR, pipelines, and Slack announcement
Overview
Releasing should be simple, but the checklist keeps growing. Pull the latest commits, write a changelog, create the right tag, open an MR with a proper description, kick off pipelines, then hop over to Slack to announce it. Each step is small, but together they eat 15 minutes and break your flow.
How it works
A cursor rule defines your release process once. When you say create a new release, MCP pulls the git log since your last tag, generates a changelog, creates the proper version tag, and opens an MR with everything documented. It runs your deployment pipelines and sends a Slack message to your team channel with the release notes. One command, full release, no context switching.
Who this is for
Engineers and DevOps teams who release frequently and are tired of the manual checklist. Works best in Cursor where you can trigger the entire release flow without leaving your editor.
Suggested prompt
Help me set up an automated release workflow. Start by asking me for: (1) which GitLab repo I am releasing, (2) what channel I want release announcements sent to, (3) how I version my releases (semver, date-based, etc.), and (4) any other steps in my current release process. Once you have my answers, walk me through what the automation will do. When I say create a release, pull the git log since the last tag, generate a changelog, create the new tag, open an MR with the release notes, and send an announcement to Slack. Show me what you are about to do at each step and wait for my go-ahead before pushing anything.
Frequently asked questions
What does the release workflow actually automate?
It pulls the git log since your last tag, generates a changelog, creates the version tag, opens an MR with the release notes, and sends a Slack announcement to your team channel. One command handles the full release process.
Can I customize the versioning scheme?
Yes. You tell the AI how you version your releases (semver, date-based, etc.) when you set up the workflow. It follows your convention for tagging and changelog formatting.
Does it push directly to production?
It creates the tag and opens the MR, but you control when it gets merged and deployed. The AI shows you what it is about to do at each step and waits for your approval before pushing anything.
Which git hosting and chat tools does this support?
This template uses GitLab for code hosting and merge requests, and Slack for team announcements. It handles git log parsing, tagging, and MR creation through the GitLab API.