René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add release management operations to releases toolset","articleBody":"### Describe the feature or problem you'd like to solve\n\nThe current toolset has no way to create, update, or delete GitHub releases. Agents can read repository tags and commits, but can't actually publish releases or attach assets.\n\nI hit this while trying to automate a changelog + release workflow. My agent could draft the release notes by reading commit history, but had no way to actually publish the release on GitHub.\n\n### Proposed solution\n\nAdd release lifecycle operations:\n\n| Tool | REST API Endpoint |\n|------|-------------------|\n| `create_release` | `POST /repos/{owner}/{repo}/releases` |\n| `update_release` | `PATCH /repos/{owner}/{repo}/releases/{release_id}` |\n| `delete_release` | `DELETE /repos/{owner}/{repo}/releases/{release_id}` |\n| `upload_release_asset` | `POST /repos/{owner}/{repo}/releases/{release_id}/assets` |\n\nThis mirrors the existing pattern for issues (`create_or_update_issue`) and PRs.\n\n### Example prompts or workflows\n\n1. \"Create a new release v2.1.0 with these changelog notes\"\n2. \"Upload the build artifacts to the latest release\"\n3. \"Mark release v2.0.0-beta as a prerelease\"\n4. \"Delete the accidental draft release I just created\"\n5. \"Bump the release from draft to published after CI passes\"\n\n### Additional context\n\nThe `releases` read operations already exist. Happy to submit a PR if this feature is accepted.","author":{"url":"https://github.com/gfortaine","@type":"Person","name":"gfortaine"},"datePublished":"2026-01-27T11:27:32.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/1909/github-mcp-server/issues/1909"}