github-mcp-server creates parent issues and sub-issues atomically
Introduced 2026-08-25 · score 0.95
HOW TO USE IT
When creating an issue as a sub-issue, call `issue_write` with `method: "create"` and `parent_issue_number`; the server creates and attaches it in the same operation. For a parent in another repository, also provide both `parent_owner` and `parent_repo`.
issue_write({"method":"create","owner":"<owner>","repo":"<repo>","title":"<sub-issue title>","parent_issue_number":<parent issue number>})issue_write({"method":"create","owner":"<owner>","repo":"<repo>","title":"<sub-issue title>","parent_issue_number":<parent issue number>,"parent_owner":"<parent owner>","parent_repo":"<parent repo>"})WHY THIS HELPS
Create a GitHub issue and its sub-issues as part of an issue workflow.
BEFORE THIS CHANGE
The PR states that creating and attaching an issue previously required separate calls, leaving a partial-failure window.
REQUIREMENTS AND LIMITATIONS
- Version: v1.11.0
- method (required): Use `create` to create a new issue.
- owner (required): Owner of the repository where the new issue is created.
- repo (required): Repository where the new issue is created.
- title (required): Title for the issue being created.
- parent_issue_number: Parent issue number; used with `method: create` to attach the new issue in the same operation. Cannot be combined with `issue_fields`.
- parent_owner: Parent repository owner. Provide together with `parent_repo`; omit both to use `owner` and `repo`.
- parent_repo: Parent repository name. Provide together with `parent_owner`; omit both to use `owner` and `repo`.
- Prerequisite: The tool documents OAuth scope `repo`.
FIRST-PARTY EVIDENCE
- https://github.com/github/github-mcp-server/releases/tag/v1.11.0
- https://github.com/github/github-mcp-server/pull/3134
- https://github.com/github/github-mcp-server?locale=en-US
Check the installed version and the source before using it. Entry JSON