Write and publish release notes from your AI assistant
The changelog is the last chore of every release, so hand it to the agent that wrote the code. Onset MCP lets Claude or Cursor draft, schedule, and publish your release notes without leaving the editor. Free plan, no credit card.
Onset is a release notes tool. The most common thing I hear from users is a confession: "we stopped posting updates." Writing the changelog is the last thing standing between you and being done with a release, so it slips. Then it's three months of shipped work nobody knows about.
Your agent already knows what shipped, it wrote half of it. It just had no way to publish.
That's Onset MCP. Point Claude, Cursor, or any MCP client at your workspace and say "write up what we shipped this week." It reads your releases and roadmap, drafts the notes, and publishes to your public page. You review before it goes out, always.
@lucy_rolff all of it. For example for tone you can just say it in the chat something like "make it shorter, no marketing voice, assume they read the last one"
Report
It would be useful to have different templates for major releases, small fixes, and security updates. That could save even more editing time.
@magdalena_anderson we have change types (New, Changed, Fixed, Removed, Deprecated, Security), which you can rename, recolour and reorder in workspace settings, so a security release reads differently from a batch of bug fixes on the page. Going through an agent you can also keep the shape in your project rules and it'll follow it every time.
Report
Can the agent pull change directly from a GitHub PR and turn them into a customer friendky update?
Inside the Onset editor, connect GitHub and the AI assistant pulls merged PRs into a draft (you can also use Linear and Jira).
Through MCP you don't need the integration at all, because Claude or Cursor already has the repo open. Ask it to read PR 412 and write the release, and it publishes through Onset. The MCP server itself never touches GitHub.
Report
I like that the focus is not just on writing notes, but also scheduling and publishing them. That makes the whole process feel more complete.
Report
Release notes are easy to postpone after shipping. I like the idea of making them part of the same workflow instead of another task to remember.
Onset.io
Hey Product Hunt 👋
I'm Sonny, and I build Onset.
Onset is a release notes tool. The most common thing I hear from users is a confession: "we stopped posting updates." Writing the changelog is the last thing standing between you and being done with a release, so it slips. Then it's three months of shipped work nobody knows about.
Your agent already knows what shipped, it wrote half of it. It just had no way to publish.
That's Onset MCP. Point Claude, Cursor, or any MCP client at your workspace and say "write up what we shipped this week." It reads your releases and roadmap, drafts the notes, and publishes to your public page. You review before it goes out, always.
Setup is one config block: https://docs.onset.io
It works on the free plan, which is free forever: unlimited releases, 1,000 subscribers, custom domain, no card.
I'd love to know what you'd want it to do that it doesn't yet. I'm here all day.
The branded changelog is a nice touch. Customers can actually see what changed without having to dig throught technical updates.
Onset.io
@mae_twyman Thanks Mae! You also get custom domain is on the free plan, so it sits on your own subdomain rather than ours :)
How much control do you have over the tone and level of detail before the relaese notes gets published?
Onset.io
@lucy_rolff all of it. For example for tone you can just say it in the chat something like "make it shorter, no marketing voice, assume they read the last one"
It would be useful to have different templates for major releases, small fixes, and security updates. That could save even more editing time.
Onset.io
@magdalena_anderson we have change types (New, Changed, Fixed, Removed, Deprecated, Security), which you can rename, recolour and reorder in workspace settings, so a security release reads differently from a batch of bug fixes on the page. Going through an agent you can also keep the shape in your project rules and it'll follow it every time.
Can the agent pull change directly from a GitHub PR and turn them into a customer friendky update?
Onset.io
@leo_henry6 Yes, two ways:
Inside the Onset editor, connect GitHub and the AI assistant pulls merged PRs into a draft (you can also use Linear and Jira).
Through MCP you don't need the integration at all, because Claude or Cursor already has the repo open. Ask it to read PR 412 and write the release, and it publishes through Onset. The MCP server itself never touches GitHub.
I like that the focus is not just on writing notes, but also scheduling and publishing them. That makes the whole process feel more complete.
Release notes are easy to postpone after shipping. I like the idea of making them part of the same workflow instead of another task to remember.