Publish a changelog in Cursor

Setup

You need a secret key (nv_live_…) from Dashboard → API keys.

{
  "mcpServers": {
    "nordva": {
      "url": "https://mcp.nordva.dev",
      "headers": {
        "Authorization": "Bearer nv_live_..."
      }
    }
  }
}

Then ask Cursor

• 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.

For “Publish a changelog entry for the CSV export fix we just merged.” Cursor 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: The entry id, its status (published or scheduled) and the public URL of the entry on the hosted changelog page.

Changelog tools and arguments

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.
• Cursor's agent decides when to call a tool from the tool descriptions; naming the tool in the prompt ("use publish_changelog_entry") removes the guesswork.
• Tools that send email or remove content are flagged destructive by the server, and their descriptions tell the agent to confirm with you first.