Skip to main content

MCP server for changelogs

The agent that wrote the change already knows what changed. With the Nordva Launch MCP server connected, it can publish the release note to your hosted changelog at the end of the session, schedule it for later, or check what has already been posted.

Get an API key → Changelog API overview

Things to ask

  • Publish a changelog entry for what we just shipped. Category: fix.
  • Draft an entry for the new export feature and schedule it for Monday 09:00 UTC.
  • What did we publish on the changelog this month?
  • Archive the entry about the beta importer, it went out by mistake.

One call, start to finish

You type: “Publish a changelog entry for the CSV export fix we just merged.” The agent calls publish_changelog_entry with:

{
  "title": "CSV export no longer drops rows with commas in the name",
  "body_markdown": "Names containing a comma were split into two columns, which shifted every field after them. Values are now quoted.\n\nAffects exports made since 2 September. Re-export to get a correct file.",
  "category": "fix",
  "version": "v1.8.2"
}

Returned to the agent: The entry id, its status (published or scheduled) and the public URL of the entry on the hosted changelog page.

Tools and arguments

publish_changelog_entry

Publish or schedule a changelog entry

titlerequiredstring, max 200User-facing headline.
body_markdownrequiredstring, max 50,000Full description in Markdown.
categoryrequired"feature" | "fix" | "improvement" | "security" | "breaking"Use 'breaking' only when customers must change code/config.
versionoptionalstring, max 64Free-form version string. Not validated as semver.
scheduled_atoptionalstringISO 8601 timestamp. If set, entry is scheduled, not published.

list_changelog_entries

Read-only

List recent changelog entries

limitoptionalnumber, 1–50
categoryoptional"feature" | "fix" | "improvement" | "security" | "breaking"
statusoptional"draft" | "published" | "scheduled" | "archived"
sinceoptionalstring

archive_changelog_entry

Confirms first

Remove a changelog entry from public view

entry_idrequiredstringThe id of the changelog entry to archive (e.g. ce_01hwxyz...).

Behaviour worth knowing

  • Without scheduled_at the entry is public immediately. With it, the entry stays in scheduled status until a cron that runs every minute publishes it.
  • Archiving is a soft delete: the entry leaves the public page and feed at once but is not destroyed.
  • On the Free plan the eleventh published entry is refused with PLAN_LIMIT_REACHED. The tool description tells the agent to show the upgrade link and stop rather than retry.
  • Published entries are emailed to confirmed subscribers on plans that include subscribers.

Questions

Can the agent publish without asking me?
That is decided by your client's permission settings, not by the server. Claude Code, Cursor and VS Code all ask before a tool's first call unless you allow it. The tool description also tells the agent to ask whether a draft should be scheduled or published.
What stops a retry from posting the same entry twice?
The server hashes the title, body, category, version and schedule into an Idempotency-Key. An identical retry within 24 hours returns the original entry instead of creating another.
Can it edit an entry that is already published?
Not through MCP today. Editing drafts and scheduled entries is a REST call, PATCH /v1/changelog/entries/{id}. The MCP tools cover publish, list and archive.