mcp-release-notes

# Draft MCP Server Release Notes for $ARGUMENTS Follow the workflow defined in `.claude/skills/release-notes-base/SKILL.md`, substituting the following values: | Placeholder | Value | |--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `{VERSION}` | `$ARGUMENTS` | | `{GITHUB_REPO}` | `mongodb-js/mongodb-mcp-server` | | `{RELEASE_NOTES_FILE}` | `content/mcp-server/source/release-notes.txt` | | `{PRODUCT_SUBSTITUTION}` | bare version number only (e.g. `1.9.0`) — no substitution constant, no `v` prefix | | `{VERSION_KEY}` | N/A — `content/mcp-server/snooty.toml` has no version key; skip step 6 | | `{SNOOTY_TOML}` | N/A | | `{CHANGELOG_LINK}` | Multi-line inline RST hyperlink — see format overrides below for the exact format | ## Format overrides These rules override the shared defaults in `release-notes-base`. For RST formatting (heading style, changelog link), read `references/rst-formatting.md`. - **Section labels:** before drafting, ask the writer which section labels to use. Present the following options and allow free input: - `New features and updates:` - `Bug Fixes:` - A custom label the writer provides - Omit a section entirely if it has no entries. If the release has both new features and bug fixes, confirm whether to use both sections or combine them under a single label.