gitlab_create_merge_request_note_internal
Add a comment to a GitLab merge request with the option to mark it as an internal note, visible only to project members, for secure and targeted communication.
Instructions
Add a comment to a merge request with option to make it an internal note
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | The content of the note/comment | |
| internal | No | If true, the note will be marked as an internal note visible only to project members | |
| merge_request_iid | Yes | The internal ID of the merge request | |
| project_id | Yes | The ID or URL-encoded path of the project |
Input Schema (JSON Schema)
You must be authenticated.
Other Tools from GitLab MCP Server
- gitlab_add_group_member
- gitlab_add_project_member
- gitlab_add_webhook
- gitlab_compare_branches
- gitlab_create_cicd_variable
- gitlab_create_merge_request_note
- gitlab_create_merge_request_note_internal
- gitlab_create_trigger_token
- gitlab_delete_cicd_variable
- gitlab_delete_trigger_token
- gitlab_delete_webhook
- gitlab_disable_slack_integration
- gitlab_get_cicd_variable
- gitlab_get_group
- gitlab_get_integration
- gitlab_get_merge_request
- gitlab_get_merge_request_changes
- gitlab_get_project
- gitlab_get_repository_file
- gitlab_get_trigger_token
- gitlab_get_user
- gitlab_get_webhook
- gitlab_list_branches
- gitlab_list_cicd_variables
- gitlab_list_group_members
- gitlab_list_groups
- gitlab_list_integrations
- gitlab_list_issues
- gitlab_list_merge_requests
- gitlab_list_project_members
- gitlab_list_projects
- gitlab_list_trigger_tokens
- gitlab_list_users
- gitlab_list_webhooks
- gitlab_test_webhook
- gitlab_trigger_pipeline
- gitlab_update_cicd_variable
- gitlab_update_merge_request
- gitlab_update_slack_integration
- gitlab_update_trigger_token
- gitlab_update_webhook
Related Tools
- @rifqi96/mcp-gitlab
- @ZephyrDeng/mcp-server-gitlab
- @modelcontextprotocol/gitlab