Repository navigation
Add ability to fetch issue relationships (parent, blocked by, etc..) #950
Description
Activity
➕ I would find this useful as well, especially for parent child relationships, as we are coming to rely on those internally as opposed to textual links, and Copilot is missing important context from parent issues, or the existence of child issues.
Would be great to not only support reading, but also support updating issue dependencies via MCP.
Reacted by Peter@tommaso-moro you could use my mcp while we are awaiting this to be implemented. link: https://github.com/[chuks-qua/github-issues-mcp-server](https://github.com/chuks-qua/github-issues-mcp-server).
does all you need.
I would love this to be assigned to me, although go lang is not my strong suite
- added 2 commits that reference this issue
on Feb 3, 2026 any update on this feature?
@huzii7 unfortunately, been waiting for ages but had to whip up mine. check if it helps
https://github.com/chuks-qua/github-issues-mcp-server
Reacted by Huzaifah Habib and ex-devoYeah looking for this too. Not just to fetch, but to update as well.
Yeah looking for this too. Not just to fetch, but to update as well.
Another options is the gh cli. i had a skill that uses the cli for that. not uploaded on my account but if you are interested i could make it public and maintain it if you want.
github-actions commented
on May 27, 2026 on May 27, 2026 – with GitHub ActionsContributorMore actionsThis issue is stale because it has been open for 30 days with no activity. Leave a comment to avoid closing this issue in 60 days.
✋🏻 I would still like this feaure Stalebot.
Reacted by PV and Jan Sebastian Siwygithub-actions commented
on Jun 28, 2026 on Jun 28, 2026 – with GitHub ActionsContributorMore actionsThis issue is stale because it has been open for 30 days with no activity. Leave a comment to avoid closing this issue in 60 days.
- added 4 commits that reference this issue
on Jul 8, 2026
The REST API has endpoints for dependencies (e.g. to see what an issue is blocked by) so that should be easy to integrate.
As to retrieving a parent's issue, at first glance there might be an API limitation making that difficult as the GET issue endpoint isn't returning information about the issue's parent in the response - this might need a closer look.