epics

[matejthetree]

is it possible to edit epics trough this, and add child issues?

[Kenneth-Sills]

Had a similar question myself! Taking a look: not currently.

The Gitlab API is in a bit of an awkward spot as they migrate from the two related APIs (Epics and Epics Issues) to Work Items with the new unified framework because... well... there's no REST API for that and the issue to do so is stalled on a GQL -> REST transform layer.

The deprecated API could be added to this project, and will likely work for the next year or so until removal in Gitlab 19+, but is a "dead end" so-to-speak. To use the GraphQL API would require some rework of the MCP, since this project seems to focus pretty heavily on the REST API.

I do wonder if you could use a GraphQL MCP (1, 2), which provides support for introspection queries and allows the AI to plan its own resource queries (as opposed to using the hard-coded queries like this project). Mutation is off by default as well, so likely just as safe as read-only mode here.

---

EDIT: Yeah, confirmed that using the GraphQL MCP works perfect. Just make sure to set a HEADERS env with an authorization header containing your [read-]api PAT. I did have to tell the AI to consistently use the introspect schema, or it'll try to use pre-existing knowledge of the GraphQL API that may be out of date.