MCP and API Functions for Inline Merge Request Comments
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
A GitLab Self-Managed GitLab Premium GitLab Duo Enterprise customer reported in ZD#698280 that external agents need MCP and API functions to post inline merge request comments.
Release notes
Enable external agents to post inline comments on merge requests using their composite identity through new MCP server functions and API endpoints, eliminating the need for separate service accounts and custom MCP servers.
Problem to solve
External agents using composite identity cannot post inline comments on merge requests through the official GitLab MCP server. This forces users to maintain a separate service account for API authentication and run custom MCP servers, creating confusion when the reviewing agent and commenting service account are different entities.
Proposal
Add the following MCP server functions to the GitLab MCP server:
- Create Merge Request Comment
- Update Merge Request Comment
- Delete Merge Request Comment
- List Merge Request Comment
Another possibility might be allowing to merge_requests API endpoint with service account.
Intended users
Feature Usage Metrics
Does this feature require an audit event?
Probably yes! Inline comments created by external agents should be auditable to track AI-generated feedback on code changes.