@zereight/mcp-gitlab 2.1.60 → 2.1.62

package/README.ko.md

@@ -17,7 +17,7 @@ PAT, OAuth, 읽기 전용 모드, 동적 API URL, 원격 인증을 지원하며
 
 ### 왜 이 GitLab MCP를 사용하나요?
 
-- **232개 도구 + `discover_tools`** — 작은 toolset으로 시작하고, 런타임에 카테고리 활성화
+- **261개 도구 + `discover_tools`** — 작은 toolset으로 시작하고, 런타임에 카테고리 활성화
 - **MR 2단계 리뷰** — `list_merge_request_changed_files` → 배치 `get_merge_request_file_diff`
 - **Agent Skill 내장** — `skills/gitlab-mcp/` 워크플로우 가이드
 - **유연한 인증** — Personal Access Token, 로컬 OAuth2 브라우저 플로우, MCP OAuth 프록시, 요청별 원격 인증
@@ -30,7 +30,7 @@ PAT, OAuth, 읽기 전용 모드, 동적 API URL, 원격 인증을 지원하며
 | | @zereight/mcp-gitlab | GitLab MCP A (커뮤니티 CQRS형) |
 |---|----------------------|--------------------------------|
 | **적합한 경우** | AI 에이전트 워크플로우 | 엔터프라이즈 멀티 인스턴스 / 그룹형 도구 |
-| **도구 모델** | ~232개 세분화 도구 + `discover_tools` | ~50–60개 `browse_*` / `manage_*` 그룹 도구 |
+| **도구 모델** | ~261개 세분화 도구 + `discover_tools` | ~50–60개 `browse_*` / `manage_*` 그룹 도구 |
 | **MR 리뷰** | 2단계 배치 diff | 서버마다 다름 |
 | **Node.js** | >=18.17 | 보통 >=24 |
 | **라이선스** | MIT | 서버마다 다름 |
@@ -110,7 +110,7 @@ command = lib.getExe inputs.gitlab-mcp.packages.${system}.default;
 
 예시는 기존 `mcp-gitlab`보다 충돌 가능성이 낮은 `zereight-mcp-gitlab` 별칭을 사용합니다. MCP 클라이언트가 찾지 못하면 `which zereight-mcp-gitlab`의 절대 경로를 사용하세요.
 
-전역 설치를 쓰지 않으려면 `npx -y @zereight/mcp-gitlab@2.1.59`처럼 직전 안정 버전(문서가 권장하는 버전)으로 고정하세요. 항상 최신 버전을 원하면 `npx -y @zereight/mcp-gitlab@latest`를 사용하세요. 새 버전이 나오면 서버가 시작 시 stderr로 알려줍니다(`GITLAB_DISABLE_VERSION_CHECK=true`로 비활성화 가능).
+전역 설치를 쓰지 않으려면 `npx -y @zereight/mcp-gitlab@2.1.61`처럼 직전 안정 버전(문서가 권장하는 버전)으로 고정하세요. 항상 최신 버전을 원하면 `npx -y @zereight/mcp-gitlab@latest`를 사용하세요. 새 버전이 나오면 서버가 시작 시 stderr로 알려줍니다(`GITLAB_DISABLE_VERSION_CHECK=true`로 비활성화 가능).
 
 #### CLI 인자 사용하기(환경 변수 문제가 있는 클라이언트용)
 

package/README.md

@@ -22,7 +22,7 @@ Supports PAT, OAuth, read-only mode, dynamic API URLs, and remote authorization
 
 ### Why use this GitLab MCP?
 
-- **232 tools + `discover_tools`** — start with a small toolset; activate more at runtime without CQRS-style grouping
+- **261 tools + `discover_tools`** — start with a small toolset; activate more at runtime without CQRS-style grouping
 - **MR 2-step review** — `list_merge_request_changed_files` → batched `get_merge_request_file_diff`
 - **Agent Skill built in** — workflow guidance in `skills/gitlab-mcp/`
 - **Flexible auth** — Personal Access Token, local OAuth2 browser flow, MCP OAuth proxy, and per-request remote authorization
@@ -35,7 +35,7 @@ Supports PAT, OAuth, read-only mode, dynamic API URLs, and remote authorization
 | | @zereight/mcp-gitlab | GitLab MCP A (community CQRS-style) |
 |---|----------------------|-------------------------------------|
 | **Best for** | AI agent workflows | Enterprise multi-instance / grouped tools |
-| **Tool model** | ~232 granular tools + `discover_tools` | ~50–60 grouped `browse_*` / `manage_*` tools |
+| **Tool model** | ~261 granular tools + `discover_tools` | ~50–60 grouped `browse_*` / `manage_*` tools |
 | **MR review** | 2-step batched diff | Varies |
 | **Node.js** | >=18.17 | Often >=24 |
 | **License** | MIT | Varies |
@@ -115,7 +115,7 @@ The store path is pinned by your lock file; update it with `nix flake update git
 
 The examples use `zereight-mcp-gitlab`, a less collision-prone alias for the legacy `mcp-gitlab` binary. If your MCP client cannot find it, use the absolute path from `which zereight-mcp-gitlab`.
 
-No global install? Pin `npx` to the previous stable release (the version these docs recommend), for example `npx -y @zereight/mcp-gitlab@2.1.59`. If you always want the newest release, use `npx -y @zereight/mcp-gitlab@latest` instead. The server prints a notice to stderr on startup when a newer version is available (disable with `GITLAB_DISABLE_VERSION_CHECK=true`).
+No global install? Pin `npx` to the previous stable release (the version these docs recommend), for example `npx -y @zereight/mcp-gitlab@2.1.61`. If you always want the newest release, use `npx -y @zereight/mcp-gitlab@latest` instead. The server prints a notice to stderr on startup when a newer version is available (disable with `GITLAB_DISABLE_VERSION_CHECK=true`).
 
 #### Using CLI Arguments (for clients with env var issues)
 
@@ -583,23 +583,23 @@ Register the skill directory in your AI client to get optimal tool usage guidanc
 
 <!-- TOOLS-START -->
 
-1. `merge_merge_request` - Merge a merge request in a GitLab project
-2. `approve_merge_request` - Approve a merge request (requires appropriate permissions)
-3. `unapprove_merge_request` - Unapprove a previously approved merge request
-4. `get_merge_request_approval_state` - Get merge request approval details including approvers (uses `approval_state` when available, otherwise falls back to `approvals`)
-5. `get_merge_request_conflicts` - Get the conflicts of a merge request in a GitLab project
-6. `list_merge_request_pipelines` - List pipelines for a merge request with pagination support
+1. `merge_merge_request` - Merge a merge request
+2. `approve_merge_request` - Approve a merge request
+3. `unapprove_merge_request` - Unapprove a merge request
+4. `get_merge_request_approval_state` - Get merge request approval details including approvers
+5. `get_merge_request_conflicts` - Get the conflicts of a merge request
+6. `list_merge_request_pipelines` - List pipelines for a merge request with pagination
 7. `execute_graphql` - Execute a GitLab GraphQL query
-8. `create_or_update_file` - Create or update a single file in a GitLab project
+8. `create_or_update_file` - Create or update a file in a GitLab project
 9. `search_repositories` - Search for GitLab projects
 10. `create_repository` - Create a new GitLab project
-11. `create_group` - Create a new GitLab group or subgroup (name, path, description, visibility, and optional parent_id)
-12. `get_file_contents` - Get the contents of a file or directory from a GitLab project
-13. `push_files` - Push multiple files to a GitLab project in a single commit
-14. `create_issue` - Create a new issue in a GitLab project
-15. `create_merge_request` - Create a new merge request in a GitLab project
-16. `fork_repository` - Fork a GitLab project to your account or specified namespace
-17. `create_branch` - Create a new branch in a GitLab project
+11. `create_group` - Create new group or subgroup
+12. `get_file_contents` - Get contents of a file or directory from a GitLab project
+13. `push_files` - Push multiple files in a single commit
+14. `create_issue` - Create a new issue
+15. `create_merge_request` - Create a new merge request
+16. `fork_repository` - Fork a project to your account or specified namespace
+17. `create_branch` - Create a new branch
 18. `get_branch` - Get branch details (commit, protection status)
 19. `list_branches` - List branches in project with search filter
 20. `delete_branch` - Delete branch from project
@@ -608,15 +608,15 @@ Register the skill directory in your AI client to get optimal tool usage guidanc
 23. `protect_branch` - Protect a repository branch (set push/merge/unprotect access levels)
 24. `unprotect_branch` - Remove protection from a previously protected branch
 25. `update_default_branch` - Change the default branch of a project
-26. `get_merge_request` - Get details of a merge request with compact deployment summary, behind-count, commit addition summary, and approval summary (Either mergeRequestIid or branchName must be provided)
-27. `get_merge_request_diffs` - Get the changes/diffs of a merge request (Either mergeRequestIid or branchName must be provided)
-28. `list_merge_request_changed_files` - STEP 1 of code review workflow. Returns ONLY the list of changed file paths in a merge request — WITHOUT diff content. Call this first to get file paths, then call get_merge_request_file_diff with multiple files in a single batched call (recommended 3-5 files per call). Supports excluded_file_patterns filtering using regex. (Either mergeRequestIid or branchName must be provided)
-29. `list_merge_request_diffs` - List merge request diffs with pagination support (Either mergeRequestIid or branchName must be provided)
-30. `get_merge_request_file_diff` - STEP 2 of code review workflow. Get diffs for one or more files from a merge request. Call list_merge_request_changed_files first, then pass them as an array to fetch diffs efficiently. Batching multiple files (recommended 3-5) is supported. (Either mergeRequestIid or branchName must be provided)
+26. `get_merge_request` - Get details of a merge request (mergeRequestIid or branchName required). Set include_summaries=true for deployment/commit/approval summaries
+27. `get_merge_request_diffs` - Get the changes/diffs of a merge request (mergeRequestIid or branchName required)
+28. `list_merge_request_changed_files` - List changed file paths in a merge request without diff content (mergeRequestIid or branchName required)
+29. `list_merge_request_diffs` - List merge request diffs with pagination (mergeRequestIid or branchName required)
+30. `get_merge_request_file_diff` - Get diffs for specific files from a merge request (mergeRequestIid or branchName required)
 31. `list_merge_request_versions` - List all versions of a merge request
 32. `get_merge_request_version` - Get a specific version of a merge request
-33. `get_branch_diffs` - Get the changes/diffs between two branches or commits in a GitLab project
-34. `update_merge_request` - Update a merge request (Either mergeRequestIid or branchName must be provided)
+33. `get_branch_diffs` - Get diffs between two branches or commits
+34. `update_merge_request` - Update a merge request (mergeRequestIid or branchName required)
 35. `create_note` - Create a new note (comment) to an issue or merge request
 36. `create_merge_request_thread` - Create a new thread on a merge request
 37. `resolve_merge_request_thread` - Resolve a thread on a merge request
@@ -624,18 +624,18 @@ Register the skill directory in your AI client to get optimal tool usage guidanc
 39. `delete_merge_request_discussion_note` - Delete a discussion note on a merge request
 40. `update_merge_request_discussion_note` - Update a discussion note on a merge request
 41. `create_merge_request_discussion_note` - Add a new discussion note to an existing merge request thread
-42. `create_merge_request_note` - Add a new note to an existing merge request thread
+42. `create_merge_request_note` - Add a new note to a merge request
 43. `delete_merge_request_note` - Delete an existing merge request note
 44. `get_merge_request_note` - Get a specific note for a merge request
 45. `get_merge_request_notes` - List notes for a merge request
-46. `update_merge_request_note` - Modify an existing merge request thread note
+46. `update_merge_request_note` - Modify an existing merge request note
 47. `get_draft_note` - Get a single draft note from a merge request
 48. `list_draft_notes` - List draft notes for a merge request
 49. `create_draft_note` - Create a draft note for a merge request
 50. `update_draft_note` - Update an existing draft note
 51. `delete_draft_note` - Delete a draft note
 52. `publish_draft_note` - Publish a single draft note
-53. `bulk_publish_draft_notes` - Publish all draft notes for a merge request
+53. `bulk_publish_draft_notes` - Publish all draft notes for a merge request. Optionally sets reviewer_state and posts a summary note (GitLab 19.2+). Can set reviewer_state even with no drafts.
 54. `list_merge_request_emoji_reactions` - List all emoji reactions on a merge request
 55. `list_merge_request_note_emoji_reactions` - List all emoji reactions on a merge request note. Pass discussion_id for discussion thread replies.
 56. `create_merge_request_emoji_reaction` - Add an emoji reaction to a merge request (e.g. thumbsup, rocket, eyes)
@@ -643,30 +643,30 @@ Register the skill directory in your AI client to get optimal tool usage guidanc
 58. `create_merge_request_note_emoji_reaction` - Add an emoji reaction to a merge request note. Pass discussion_id for discussion thread replies.
 59. `delete_merge_request_note_emoji_reaction` - Remove an emoji reaction from a merge request note. Pass discussion_id for discussion thread replies.
 60. `update_issue_note` - Modify an existing issue thread note
-61. `create_issue_note` - Add a new note to an existing issue thread
+61. `create_issue_note` - Add a note to an issue, optionally replying to a discussion thread
 62. `list_issue_emoji_reactions` - List all emoji reactions on an issue
 63. `list_issue_note_emoji_reactions` - List all emoji reactions on an issue note. Pass discussion_id for discussion thread replies.
 64. `create_issue_emoji_reaction` - Add an emoji reaction to an issue (e.g. thumbsup, rocket, eyes)
 65. `delete_issue_emoji_reaction` - Remove an emoji reaction from an issue
 66. `create_issue_note_emoji_reaction` - Add an emoji reaction to an issue note. Pass discussion_id for discussion thread replies.
 67. `delete_issue_note_emoji_reaction` - Remove an emoji reaction from an issue note. Pass discussion_id for discussion thread replies.
-68. `list_issues` - List issues (default: created by current user only; use scope='all' for all accessible issues)
-69. `my_issues` - List issues assigned to the authenticated user (defaults to open issues)
-70. `get_issue` - Get details of a specific issue in a GitLab project
-71. `update_issue` - Update an issue in a GitLab project
-72. `update_issue_description_patch` - Apply a patch (search/replace or unified diff) to an issue description. Reduces token usage by sending only the change instead of the full description. Supports `dry_run` to preview and `create_note` to summarize.
-73. `delete_issue` - Delete an issue from a GitLab project
+68. `list_issues` - List issues (default: created by current user; use scope='all' for all)
+69. `my_issues` - List issues assigned to the authenticated user
+70. `get_issue` - Get details of a specific issue. Returns a slim milestone by default; set full_response=true for the complete milestone object
+71. `update_issue` - Update an issue. Returns a slim confirmation by default; set full_response=true for the complete updated issue object
+72. `update_issue_description_patch` - Apply a patch (search/replace or unified diff) to an issue description. Reduces token usage by allowing small changes without sending the full description. Supports dry_run to preview changes and create_note to summarize updates.
+73. `delete_issue` - Delete an issue
 74. `list_todos` - List GitLab to-do items for the current user
 75. `mark_todo_done` - Mark a GitLab to-do item as done
 76. `mark_all_todos_done` - Mark all pending GitLab to-do items as done for the current user
 77. `list_issue_links` - List all issue links for a specific issue
-78. `list_issue_discussions` - List discussions for an issue in a GitLab project
+78. `list_issue_discussions` - List discussions for an issue
 79. `get_issue_link` - Get a specific issue link
 80. `create_issue_link` - Create an issue link between two issues
 81. `delete_issue_link` - Delete an issue link
-82. `list_namespaces` - List all namespaces available to the current user
-83. `get_namespace` - Get details of a namespace by ID or path
-84. `verify_namespace` - Verify if a namespace path exists
+82. `list_namespaces` - List all namespaces (users and groups) available to the current user. Filter by kind='group' for groups only.
+83. `get_namespace` - Get details of a namespace (user or group) by ID or path. Groups are namespaces with kind='group'.
+84. `verify_namespace` - Verify if a namespace path exists. Use parent_id to scope the check to a specific parent namespace — required for nested namespaces where the same path may exist under different parents.
 85. `get_project` - Get details of a specific project
 86. `list_projects` - List projects accessible by the current user
 87. `update_project` - Update project settings such as description, visibility, default branch, and feature access levels
@@ -677,39 +677,39 @@ Register the skill directory in your AI client to get optimal tool usage guidanc
 92. `create_label` - Create a new label in a project
 93. `update_label` - Update an existing label in a project
 94. `delete_label` - Delete a label from a project
-95. `list_group_projects` - List projects in a GitLab group with filtering options
-96. `list_wiki_pages` - List wiki pages in a GitLab project
+95. `list_group_projects` - List projects in a group
+96. `list_wiki_pages` - List wiki pages in a project
 97. `get_wiki_page` - Get details of a specific wiki page
-98. `create_wiki_page` - Create a new wiki page in a GitLab project
-99. `update_wiki_page` - Update an existing wiki page in a GitLab project
-100. `delete_wiki_page` - Delete a wiki page from a GitLab project
-101. `list_group_wiki_pages` - List wiki pages in a GitLab group
+98. `create_wiki_page` - Create a wiki page in a project
+99. `update_wiki_page` - Update a wiki page in a project
+100. `delete_wiki_page` - Delete a wiki page from a project
+101. `list_group_wiki_pages` - List wiki pages in a group
 102. `get_group_wiki_page` - Get details of a specific group wiki page
-103. `create_group_wiki_page` - Create a new wiki page in a GitLab group
-104. `update_group_wiki_page` - Update an existing wiki page in a GitLab group
-105. `delete_group_wiki_page` - Delete a wiki page from a GitLab group
-106. `get_repository_tree` - Get the repository tree for a GitLab project (list files and directories)
-107. `list_pipelines` - List pipelines in a GitLab project with filtering options
-108. `get_pipeline` - Get details of a specific pipeline in a GitLab project
+103. `create_group_wiki_page` - Create a wiki page in a group
+104. `update_group_wiki_page` - Update a wiki page in a group
+105. `delete_group_wiki_page` - Delete a wiki page from a group
+106. `get_repository_tree` - List files and directories in a repository
+107. `list_pipelines` - List pipelines with filtering options
+108. `get_pipeline` - Get details of a specific pipeline
 109. `get_pipeline_variables` - Get variables configured for a pipeline
 110. `get_pipeline_test_report` - Get pipeline test report
 111. `get_pipeline_test_report_summary` - Get pipeline test report summary
 112. `delete_pipeline` - Delete a pipeline. Requires the project Owner role, cannot be undone, and does not automatically delete child pipelines.
 113. `update_pipeline_metadata` - Update pipeline metadata
-114. `list_deployments` - List deployments in a GitLab project with filtering options
-115. `get_deployment` - Get details of a specific deployment in a GitLab project
+114. `list_deployments` - List deployments with filtering options
+115. `get_deployment` - Get deployment details, including approval_summary, approvals, and pending_approval_count when GitLab provides them
 116. `create_deployment` - Create a deployment
 117. `update_deployment` - Update a deployment status
 118. `delete_deployment` - Delete a deployment
 119. `list_deployment_merge_requests` - List merge requests shipped with a deployment
 120. `approve_deployment` - Approve or reject a protected-environment deployment
-121. `list_environments` - List environments in a GitLab project
-122. `get_environment` - Get details of a specific environment in a GitLab project
+121. `list_environments` - List environments in a project
+122. `get_environment` - Get details of a specific environment
 123. `update_environment` - Update an environment
 124. `delete_environment` - Delete a stopped environment
 125. `stop_environment` - Stop an environment
 126. `stop_stale_environments` - Stop eligible stale environments; protected environments are excluded and environments are stopped, not deleted
-127. `delete_review_app_environments` - Schedule deletion of stopped review-app environments one week later; `dry_run` defaults to true and actual scheduling requires `dry_run=false`
+127. `delete_review_app_environments` - Schedule deletion of stopped review-app environments one week later; dry_run defaults to true and actual scheduling requires dry_run=false
 128. `list_pipeline_triggers` - List project pipeline trigger tokens
 129. `get_pipeline_trigger` - Get a project pipeline trigger
 130. `create_pipeline_trigger` - Create a project pipeline trigger
@@ -717,11 +717,11 @@ Register the skill directory in your AI client to get optimal tool usage guidanc
 132. `delete_pipeline_trigger` - Delete a project pipeline trigger
 133. `trigger_pipeline` - Trigger a pipeline with a pipeline trigger token
 134. `list_pipeline_jobs` - List all jobs in a specific pipeline
-135. `list_pipeline_trigger_jobs` - List all trigger jobs (bridges) in a specific pipeline that trigger downstream pipelines
+135. `list_pipeline_trigger_jobs` - List trigger jobs (bridges) in a pipeline
 136. `get_pipeline_job` - Get details of a GitLab pipeline job number
-137. `get_pipeline_job_output` - Get the output/trace of a GitLab pipeline job with optional pagination to limit context window usage
+137. `get_pipeline_job_output` - Get the output/trace of a pipeline job with optional pagination
 138. `validate_ci_lint` - Validate provided GitLab CI/CD YAML content for a project
-139. `validate_project_ci_lint` - Validate an existing `.gitlab-ci.yml` configuration for a project
+139. `validate_project_ci_lint` - Validate an existing .gitlab-ci.yml configuration for a project
 140. `list_ci_catalog_resources` - List GitLab CI/CD Catalog resources/components visible to the user
 141. `get_ci_catalog_resource` - Get details for a GitLab CI/CD Catalog resource, including versions and components
 142. `create_pipeline` - Create a new pipeline for a branch or tag
@@ -733,7 +733,7 @@ Register the skill directory in your AI client to get optimal tool usage guidanc
 148. `create_pipeline_schedule` - Create a new pipeline schedule for a branch or tag
 149. `update_pipeline_schedule` - Update an existing pipeline schedule
 150. `delete_pipeline_schedule` - Delete a pipeline schedule
-151. `play_pipeline_schedule` - Run a pipeline schedule immediately, without changing its next scheduled run
+151. `play_pipeline_schedule` - Run a pipeline schedule immediately
 152. `take_ownership_pipeline_schedule` - Take ownership of a pipeline schedule
 153. `get_pipeline_schedule_variable` - Get a single variable of a pipeline schedule
 154. `create_pipeline_schedule_variable` - Create a variable for a pipeline schedule
@@ -746,25 +746,25 @@ Register the skill directory in your AI client to get optimal tool usage guidanc
 161. `erase_pipeline_job` - Erase a pipeline job log and artifacts
 162. `wait_for_pipeline` - Wait for a pipeline to reach a terminal status
 163. `wait_for_job` - Wait for a job to reach a terminal status
-164. `list_job_artifacts` - List artifact files in a job's artifacts archive. Returns file names, paths, types, and sizes
-165. `download_job_artifacts` - Download the entire artifact archive (zip) for a job to a local path. Returns the saved file path
-166. `get_job_artifact_file` - Get the content of a single file from a job's artifacts by its path within the archive
-167. `list_merge_requests` - List merge requests globally or in a specific GitLab project with filtering options (project_id is now optional)
-168. `list_group_merge_requests` - List merge requests across all projects of a group and its subgroups with filtering options
-169. `list_milestones` - List milestones in a GitLab project with filtering options
+164. `list_job_artifacts` - List artifact files in a job's archive
+165. `download_job_artifacts` - Download job artifact archive (zip) and save to a local path
+166. `get_job_artifact_file` - Get content of a single file from a job's artifacts
+167. `list_merge_requests` - List merge requests (without project_id: user's MRs; with project_id: project MRs)
+168. `list_group_merge_requests` - List merge requests across all projects of a group and its subgroups
+169. `list_milestones` - List milestones with filtering options
 170. `get_milestone` - Get details of a specific milestone
-171. `create_milestone` - Create a new milestone in a GitLab project
-172. `edit_milestone` - Edit an existing milestone in a GitLab project
-173. `delete_milestone` - Delete a milestone from a GitLab project
+171. `create_milestone` - Create a new milestone
+172. `edit_milestone` - Edit an existing milestone
+173. `delete_milestone` - Delete a milestone
 174. `get_milestone_issue` - Get issues associated with a specific milestone
 175. `get_milestone_merge_requests` - Get merge requests associated with a specific milestone
 176. `promote_milestone` - Promote a milestone to the next stage
 177. `get_milestone_burndown_events` - Get burndown events for a specific milestone
-178. `list_group_milestones` - List milestones in a GitLab group with filtering options
+178. `list_group_milestones` - List group milestones with filtering options
 179. `get_group_milestone` - Get details of a specific group milestone
-180. `create_group_milestone` - Create a new milestone in a GitLab group
+180. `create_group_milestone` - Create a new group milestone
 181. `edit_group_milestone` - Edit an existing group milestone
-182. `delete_group_milestone` - Delete a milestone from a GitLab group
+182. `delete_group_milestone` - Delete a group milestone
 183. `get_group_milestone_issue` - Get issues associated with a specific group milestone
 184. `get_group_milestone_merge_requests` - Get merge requests associated with a specific group milestone
 185. `get_group_milestone_burndown_events` - Get burndown events for a specific group milestone
@@ -775,72 +775,76 @@ Register the skill directory in your AI client to get optimal tool usage guidanc
 190. `get_commit` - Get details of a specific commit
 191. `get_commit_diff` - Get changes/diffs of a specific commit
 192. `get_file_blame` - Get git blame for a file at a given ref. Each entry maps a contiguous range of source lines to the commit that last changed them (id, author, authored_date, message). Use range_start/range_end to limit blame to specific lines.
-193. `list_commit_statuses` - List statuses for a specific commit
-194. `create_commit_status` - Create or update the status of a specific commit
+193. `list_commit_statuses` - List statuses for a commit
+194. `create_commit_status` - Create or update the status of a commit
 195. `list_group_iterations` - List group iterations with filtering options
-196. `upload_markdown` - Upload a file to a GitLab project for use in markdown content
-197. `download_attachment` - Download an uploaded file from a GitLab project by secret and filename
-198. `health_check` - Verify server status and authentication; when authenticated, reports GitLab instance version from `/api/v4/version` (`version`, `revision`, `enterprise`)
-199. `list_events` - List all events for the currently authenticated user
-200. `get_project_events` - List all visible events for a specified project
+196. `upload_markdown` - Upload a file for use in markdown content
+197. `download_attachment` - Download an uploaded file from a project (images returned as base64; use local_path to save to disk)
+198. `health_check` - Verify server status and authentication. Always reports the MCP server version (mcp_server_version). When authenticated, also reports the GitLab instance version from GET /api/v4/version (version, revision, enterprise). Version lookup failures do not fail the health check — those fields are omitted.
+199. `list_events` - List events for the authenticated user (before/after: YYYY-MM-DD)
+200. `get_project_events` - List events for a project (before/after: YYYY-MM-DD)
 201. `list_releases` - List all releases for a project
 202. `get_release` - Get a release by tag name
-203. `create_release` - Create a new release in a GitLab project
-204. `update_release` - Update an existing release in a GitLab project
-205. `delete_release` - Delete a release from a GitLab project (does not delete the associated tag)
-206. `create_release_evidence` - Create release evidence for an existing release (GitLab Premium/Ultimate only)
+203. `create_release` - Create a new release
+204. `update_release` - Update an existing release
+205. `delete_release` - Delete a release (does not delete the tag)
+206. `create_release_evidence` - Create release evidence (Premium/Ultimate)
 207. `download_release_asset` - Download a release asset file by direct asset path
-208. `list_tags` - List repository tags with filtering and pagination support
-209. `get_tag` - Get details of a specific repository tag
-210. `create_tag` - Create a new tag in the repository
-211. `delete_tag` - Delete a tag from the repository
-212. `get_tag_signature` - Get the signature of a signed tag
-213. `get_work_item` - Get a single work item with full details including status, hierarchy (parent/children), type, labels, assignees, and all widgets
-214. `list_work_items` - List work items in a project with filters (type, state, search, assignees, labels). Returns items with status and hierarchy info
-215. `create_work_item` - Create a new work item (issue, task, incident, test_case, epic, key_result, objective, requirement, ticket). Supports setting title, description, labels, assignees, weight, parent, health status, start/due dates, milestone, and confidentiality
-216. `update_work_item` - Update a work item. Can modify title, description, labels, assignees, weight, state, status, parent hierarchy, children, health status, start/due dates, milestone, confidentiality, linked items, and custom fields
-217. `convert_work_item_type` - Convert a work item to a different type (e.g. issue to task, task to incident)
-218. `list_work_item_statuses` - List available statuses for a work item type in a project. Requires GitLab Premium/Ultimate with configurable statuses
-219. `list_custom_field_definitions` - List available custom field definitions for a work item type in a project. Returns field names, types, and IDs needed for setting custom fields via update_work_item
-220. `move_work_item` - Move a work item (issue, task, etc.) to a different project. Uses GitLab GraphQL issueMove mutation
-221. `list_work_item_notes` - List notes and discussions on a work item. Returns threaded discussions with author, body, timestamps, and system/internal flags
-222. `create_work_item_note` - Add a note/comment to a work item. Supports Markdown, internal notes, and threaded replies
+208. `list_tags` - List repository tags for a project
+209. `get_tag` - Get a repository tag by name
+210. `create_tag` - Create a new repository tag
+211. `delete_tag` - Delete a repository tag
+212. `get_tag_signature` - Get the X.509 signature of a signed tag (404 if unsigned)
+213. `get_work_item` - Get a work item with full details including status, hierarchy, type, and widgets
+214. `list_work_items` - List work items with filters (type, state, search, assignees, labels)
+215. `create_work_item` - Create a work item (issue, task, incident, epic, etc.) with full field support
+216. `update_work_item` - Update a work item (title, description, labels, assignees, state, parent, custom fields, etc.)
+217. `convert_work_item_type` - Convert a work item to a different type
+218. `list_work_item_statuses` - List available statuses for a work item type (Premium/Ultimate)
+219. `list_custom_field_definitions` - List custom field definitions for a work item type
+220. `move_work_item` - Move a work item to a different project
+221. `list_work_item_notes` - List notes and discussions on a work item
+222. `create_work_item_note` - Add a note to a work item (supports Markdown, internal notes, threads)
 223. `list_work_item_emoji_reactions` - List all emoji reactions on a work item
 224. `list_work_item_note_emoji_reactions` - List all emoji reactions on a work item note (comment, thread, or thread reply)
 225. `create_work_item_emoji_reaction` - Add an emoji reaction to a work item (e.g. thumbsup, rocket, eyes)
 226. `delete_work_item_emoji_reaction` - Remove an emoji reaction from a work item
 227. `create_work_item_note_emoji_reaction` - Add an emoji reaction to a work item note (comment, thread, or thread reply)
 228. `delete_work_item_note_emoji_reaction` - Remove an emoji reaction from a work item note (comment, thread, or thread reply)
-229. `get_timeline_events` - List timeline events for an incident. Returns chronological events with notes, timestamps, and tags
-230. `create_timeline_event` - Create a timeline event on an incident. Supports tags: 'Start time', 'End time', 'Impact detected', 'Response initiated', 'Impact mitigated', 'Cause identified'
-231. `list_webhooks` - List all configured webhooks for a GitLab project or group. Provide either project_id or group_id
-232. `create_webhook` - Create a webhook on a GitLab project or group
+229. `get_timeline_events` - List timeline events for an incident
+230. `create_timeline_event` - Create a timeline event on an incident
+231. `list_webhooks` - List webhooks for a project or group
+232. `create_webhook` - Create a webhook on a project or group
 233. `update_webhook` - Update an existing project or group webhook
 234. `delete_webhook` - Delete a project or group webhook
-235. `list_webhook_events` - List recent webhook events (past 7 days) for a project or group webhook. Use summary mode for overview, then get_webhook_event for full details
-236. `get_webhook_event` - Get full details of a specific webhook event by ID, including request/response payloads
-237. `search_code` - Search for code across all projects on the GitLab instance (requires advanced search or exact code search to be enabled)
-238. `search_project_code` - Search for code within a specific GitLab project (requires advanced search or exact code search to be enabled)
-239. `search_group_code` - Search for code within a specific GitLab group (requires advanced search or exact code search to be enabled)
-240. `list_project_variables` - List CI/CD variables for a project with optional environment scope filter
-241. `get_project_variable` - Get a single CI/CD variable from a project by key, with optional environment scope filter
-242. `create_project_variable` - Create a new CI/CD variable in a project
-243. `update_project_variable` - Update an existing CI/CD variable in a project, with optional filter to disambiguate by environment scope
-244. `delete_project_variable` - Delete a CI/CD variable from a project, with optional filter to disambiguate by environment scope
-245. `list_group_variables` - List CI/CD variables for a group with optional environment scope filter
-246. `get_group_variable` - Get a single CI/CD variable from a group by key, with optional environment scope filter
-247. `create_group_variable` - Create a new CI/CD variable in a group
-248. `update_group_variable` - Update an existing CI/CD variable in a group, with optional filter to disambiguate by environment scope
-249. `delete_group_variable` - Delete a CI/CD variable from a group, with optional filter to disambiguate by environment scope
-250. `get_dependency_proxy_settings` - Get dependency proxy settings for a group (enabled status, blob count, total size, image prefix, TTL policy)
+235. `list_webhook_events` - List recent webhook events (past 7 days)
+236. `get_webhook_event` - Get full details of a specific webhook event
+237. `search_code` - Search for code across all projects (requires advanced search or Zoekt)
+238. `search_project_code` - Search for code within a specific project (requires advanced search or Zoekt)
+239. `search_group_code` - Search for code within a specific group (requires advanced search or Zoekt)
+240. `list_project_variables` - List CI/CD variables for a project
+241. `get_project_variable` - Get a single CI/CD variable from a project
+242. `create_project_variable` - Create a CI/CD variable for a project
+243. `update_project_variable` - Update an existing CI/CD variable in a project
+244. `delete_project_variable` - Delete a CI/CD variable from a project
+245. `list_group_variables` - List CI/CD variables for a group
+246. `get_group_variable` - Get a single CI/CD variable from a group
+247. `create_group_variable` - Create a CI/CD variable for a group
+248. `update_group_variable` - Update an existing CI/CD variable in a group
+249. `delete_group_variable` - Delete a CI/CD variable from a group
+250. `get_dependency_proxy_settings` - Get dependency proxy settings for a group
 251. `update_dependency_proxy_settings` - Update dependency proxy settings for a group (enable/disable, credentials for authenticated Docker Hub pulls)
-252. `list_dependency_proxy_blobs` - List cached dependency proxy blobs for a group with cursor-based pagination
+252. `list_dependency_proxy_blobs` - List cached dependency proxy blobs for a group
 253. `purge_dependency_proxy_cache` - Schedule purge of all cached dependency proxy blobs for a group
 254. `list_project_vulnerabilities` - List vulnerabilities for a project with optional state, severity, and report type filters (GraphQL-backed, cursor pagination)
 255. `get_vulnerability` - Get full details of a specific vulnerability
 256. `dismiss_vulnerability` - Dismiss a vulnerability with a reason (acceptable_risk, false_positive, used_in_tests, mitigating_control, not_applicable) and optional comment
 257. `confirm_vulnerability` - Confirm a vulnerability as a real finding requiring remediation
-258. `discover_tools` - Discover and activate additional tool categories for this session. Available categories: merge_requests, issues, repositories, branches, projects, labels, ci, groups, pipelines, milestones, wiki, releases, tags, users, workitems, webhooks, search, variables, dependency_proxy, vulnerabilities. Already-active categories are listed in the response.
+258. `orbit_query` - Execute a GitLab Orbit graph query over the indexed SDLC knowledge graph
+259. `orbit_get_schema` - Fetch the current GitLab Orbit graph schema (node and edge types)
+260. `orbit_get_status` - Check GitLab Orbit indexing status for the enabled scope
+261. `orbit_list_tools` - List the MCP tool definitions exposed by GitLab Orbit
+262. `discover_tools` - Discover and activate additional tool categories for this session. Available categories: merge_requests, issues, repositories, branches, projects, labels, ci, groups, pipelines, milestones, wiki, releases, tags, users, workitems, webhooks, search, variables, dependency_proxy, vulnerabilities, orbit. Already-active categories are listed in the response.
 
 <!-- TOOLS-END -->
 

package/README.zh-CN.md

@@ -17,7 +17,7 @@
 
 ### 为什么使用这个 GitLab MCP？
 
-- **232 个工具 + `discover_tools`** — 从小型 toolset 开始，运行时按需激活类别
+- **261 个工具 + `discover_tools`** — 从小型 toolset 开始，运行时按需激活类别
 - **MR 两步审查** — `list_merge_request_changed_files` → 批量 `get_merge_request_file_diff`
 - **内置 Agent Skill** — `skills/gitlab-mcp/` 工作流指南
 - **认证灵活** — Personal Access Token、本地 OAuth2 浏览器流程、MCP OAuth 代理、按请求远程授权
@@ -30,7 +30,7 @@
 | | @zereight/mcp-gitlab | GitLab MCP A（社区 CQRS 型） |
 |---|----------------------|------------------------------|
 | **更适合** | AI 代理工作流 | 企业多实例 / 分组工具 |
-| **工具模型** | ~232 个细粒度工具 + `discover_tools` | ~50–60 个 `browse_*` / `manage_*` 分组工具 |
+| **工具模型** | ~261 个细粒度工具 + `discover_tools` | ~50–60 个 `browse_*` / `manage_*` 分组工具 |
 | **MR 审查** | 两步批量 diff | 因服务器而异 |
 | **Node.js** | >=18.17 | 通常 >=24 |
 | **许可证** | MIT | 因服务器而异 |
@@ -110,7 +110,7 @@ command = lib.getExe inputs.gitlab-mcp.packages.${system}.default;
 
 示例使用 `zereight-mcp-gitlab`，这是比旧的 `mcp-gitlab` 更不容易冲突的别名。如果 MCP 客户端找不到它，请使用 `which zereight-mcp-gitlab` 输出的绝对路径。
 
-如果不想全局安装，请将 `npx` 固定到上一个稳定版本（即文档推荐的版本），例如 `npx -y @zereight/mcp-gitlab@2.1.59`。如果始终想使用最新版本，请改用 `npx -y @zereight/mcp-gitlab@latest`。有新版本发布时，服务器会在启动时通过 stderr 提示（可用 `GITLAB_DISABLE_VERSION_CHECK=true` 关闭）。
+如果不想全局安装，请将 `npx` 固定到上一个稳定版本（即文档推荐的版本），例如 `npx -y @zereight/mcp-gitlab@2.1.61`。如果始终想使用最新版本，请改用 `npx -y @zereight/mcp-gitlab@latest`。有新版本发布时，服务器会在启动时通过 stderr 提示（可用 `GITLAB_DISABLE_VERSION_CHECK=true` 关闭）。
 
 #### 使用 CLI 参数（适用于环境变量有问题的客户端）
 

package/build/index.js

@@ -10233,6 +10233,7 @@ async function handleToolCall(params) {
                                 status: authenticated ? "ok" : "error",
                                 authenticated,
                                 gitlab_url: getEffectiveApiUrl(),
+                                mcp_server_version: SERVER_VERSION,
                                 ...(versionMetadata ?? {}),
                             }),
                         },
@@ -10389,7 +10390,7 @@ async function handleToolCall(params) {
         // Sensitive fields are also covered by REDACT_PATHS if arguments are logged elsewhere.
         logger.debug({ tool: params.name }, "Tool call failed");
         if (error instanceof z.ZodError) {
-            throw new Error(`Invalid arguments: ${error.errors
+            throw new Error(`Invalid arguments: ${error.issues
                 .map(e => `${e.path.join(".")}: ${e.message}`)
                 .join(", ")}`);
         }
@@ -11583,6 +11584,7 @@ async function startStreamableHTTPServer() {
         }
         res.status(isHealthy ? 200 : 503).json({
             status: isHealthy ? "healthy" : "degraded",
+            version: SERVER_VERSION,
             activeSessions,
             maxSessions: MAX_SESSIONS,
             uptime: process.uptime(),

package/build/schemas.js

@@ -589,9 +589,9 @@ export const CreatePipelineTriggerSchema = z.object({ project_id: z.coerce.strin
 export const UpdatePipelineTriggerSchema = PipelineTriggerIdSchema.extend({ description: z.string() });
 export const TriggerPipelineSchema = z.object({
     project_id: z.coerce.string(), token: z.string(), ref: z.string(),
-    variables: z.record(z.string()).optional(),
+    variables: z.record(z.string(), z.string()).optional(),
     inputs: z
-        .record(z.unknown())
+        .record(z.string(), z.unknown())
         .optional()
         .describe("Structured pipeline inputs; supported from GitLab 17.10 behind a feature flag and generally available from GitLab 18.1. Omit on older GitLab versions."),
 });
@@ -663,7 +663,9 @@ export const GitLabPipelineScheduleSchema = z.object({
     inputs: z
         .array(z.object({
         name: z.string(),
-        value: z.unknown(),
+        // Optional: Zod 4 rejects a missing key on required unknown (Zod 3 accepted it),
+        // and schedule inputs is a new API surface (18.1+) whose response shape is still settling.
+        value: z.unknown().optional(),
     }))
         .optional(),
 });
@@ -870,11 +872,11 @@ export const PlayPipelineJobSchema = z.object({
     }))
         .optional()
         .describe("Custom job variables to use when running the job"),
-    job_inputs: z.record(z.unknown()).optional().describe("Typed job input values"),
+    job_inputs: z.record(z.string(), z.unknown()).optional().describe("Typed job input values"),
 });
 // Schema for retrying a job
 export const RetryPipelineJobSchema = PipelineJobControlSchema.extend({
-    job_inputs: z.record(z.unknown()).optional().describe("Typed job input values"),
+    job_inputs: z.record(z.string(), z.unknown()).optional().describe("Typed job input values"),
 });
 // Schema for canceling a job
 export const CancelPipelineJobSchema = z.object({
@@ -1263,8 +1265,8 @@ export const GitLabCommitSchema = z.object({
         total: z.coerce.number().optional().nullable(),
     })
         .optional(), // Only present when with_stats=true
-    trailers: z.record(z.string()).optional().default({}), // Git trailers, may be empty object
-    extended_trailers: z.record(z.array(z.string())).optional().default({}), // Extended trailers, may be empty object
+    trailers: z.record(z.string(), z.string()).optional().default({}), // Git trailers, may be empty object
+    extended_trailers: z.record(z.string(), z.array(z.string())).optional().default({}), // Extended trailers, may be empty object
 });
 export const GitLabCommitStatusSchema = z
     .object({
@@ -2129,8 +2131,7 @@ const MergeRequestParamsSchema = ProjectParamsSchema.extend({
     project_id: z
         .preprocess(value => (value === undefined || value === null ? value : String(value)), z
         .string({
-        required_error: "project_id is required",
-        invalid_type_error: "project_id is required",
+        error: "project_id is required",
     })
         .refine(value => value === "" || value.trim().length > 0, "project_id is required")
         .transform(value => (value === "" ? value : value.trim())))
@@ -2283,8 +2284,7 @@ export const ListMergeRequestPipelinesSchema = ProjectParamsSchema.extend({
     merge_request_iid: z
         .preprocess(value => (value === undefined || value === null ? value : String(value)), z
         .string({
-        required_error: "merge_request_iid is required",
-        invalid_type_error: "merge_request_iid is required",
+        error: "merge_request_iid is required",
     })
         .refine(value => value.trim().length > 0, "merge_request_iid is required")
         .transform(value => value.trim()))
@@ -2806,7 +2806,7 @@ export const GitLabWikiPageSchema = z.object({
     slug: z.string(),
     format: z.string(),
     content: z.string().optional(),
-    front_matter: z.record(z.unknown()).optional(),
+    front_matter: z.record(z.string(), z.unknown()).optional(),
     created_at: z.string().optional(),
     updated_at: z.string().optional(),
 });
@@ -2978,7 +2978,7 @@ export const GitLabDraftNoteSchema = z
     merge_request_id: z.coerce.number().nullable().optional(),
     commit_id: z.string().nullable().optional(),
     discussion_id: z.string().nullable().optional(),
-    position: z.record(z.unknown()).nullable().optional(),
+    position: z.record(z.string(), z.unknown()).nullable().optional(),
     resolve_discussion: z.coerce.boolean().optional(),
 })
     .transform(data => ({
@@ -3564,7 +3564,10 @@ export const GitLabMergeRequestVersionDetailSchema = GitLabMergeRequestVersionSc
 // GraphQL generic execution schema
 export const ExecuteGraphQLSchema = z.object({
     query: z.string().describe("GraphQL query string"),
-    variables: z.record(z.any()).optional().describe("Variables object for the GraphQL query"),
+    variables: z
+        .record(z.string(), z.any())
+        .optional()
+        .describe("Variables object for the GraphQL query"),
 });
 // Release schemas
 export const GitLabReleaseAssetLinkSchema = z.object({
@@ -3857,10 +3860,10 @@ export const GitLabTagSignatureSchema = z.object({
 });
 // --- Work item schemas (GraphQL-based) ---
 // Case-insensitive work item type enum (accepts "ISSUE", "Issue", "issue")
-const workItemTypeEnum = z
-    .string()
-    .transform(v => v.toLowerCase())
-    .pipe(z.enum([
+// Case-insensitive enum: lowercase the input, then validate against allowed values.
+// (z.preprocess form so the enum stays visible to JSON Schema conversion;
+// a transform().pipe() chain only exposes its input side as a plain string.)
+const workItemTypeEnum = z.preprocess(v => (typeof v === "string" ? v.toLowerCase() : v), z.enum([
     "issue",
     "task",
     "incident",

package/build/test/gitlab-pipeline-schedule-schema.test.js

@@ -0,0 +1,32 @@
+import assert from "node:assert/strict";
+import { test } from "node:test";
+import { GitLabPipelineScheduleSchema } from "../schemas.js";
+const BASE_SCHEDULE = {
+    id: 13,
+    description: "Nightly build",
+    cron: "0 1 * * *",
+    active: true,
+    created_at: "2026-01-01T00:00:00Z",
+    updated_at: "2026-02-01T00:00:00Z",
+};
+test("pipeline schedule response accepts inputs without value", () => {
+    // Zod 4 rejects a missing key on required unknown (Zod 3 accepted it);
+    // schedule inputs must tolerate a valueless entry.
+    const parsed = GitLabPipelineScheduleSchema.parse({
+        ...BASE_SCHEDULE,
+        inputs: [{ name: "deploy_strategy" }],
+    });
+    assert.equal(parsed.inputs?.[0].name, "deploy_strategy");
+    assert.equal("value" in (parsed.inputs?.[0] ?? {}), false);
+});
+test("pipeline schedule response keeps inputs with value", () => {
+    const parsed = GitLabPipelineScheduleSchema.parse({
+        ...BASE_SCHEDULE,
+        inputs: [
+            { name: "deploy_strategy", value: "blue-green" },
+            { name: "matrix", value: { os: "linux" } },
+        ],
+    });
+    assert.equal(parsed.inputs?.[0].value, "blue-green");
+    assert.deepEqual(parsed.inputs?.[1].value, { os: "linux" });
+});

package/build/test/group-milestone-schema.test.js

@@ -17,8 +17,9 @@ test("group milestone response keeps group_id and rejects missing group_id", ()
     });
     assert.equal(parsed.group_id, "16");
     assert.equal("project_id" in parsed, false);
-    // Project schema coerces missing project_id to "undefined" — why group schema exists
-    const coerced = GitLabMilestonesSchema.parse({
+    // Project schema rejects a group payload (missing project_id) — why group schema exists.
+    // (Zod 3 coerced the missing key to the string "undefined"; Zod 4 rejects it.)
+    assert.throws(() => GitLabMilestonesSchema.parse({
         id: 12,
         iid: 3,
         group_id: 16,
@@ -30,8 +31,7 @@ test("group milestone response keeps group_id and rejects missing group_id", ()
         updated_at: "2013-10-02T09:24:18Z",
         created_at: "2013-10-02T09:24:18Z",
         expired: false,
-    });
-    assert.equal(coerced.project_id, "undefined");
+    }));
 });
 test("group milestone issues schema accepts page and per_page", () => {
     const parsed = GetGroupMilestoneIssuesSchema.parse({

package/build/test/streamable-http-concurrent-session.test.js

@@ -1,11 +1,18 @@
 import { after, before, describe, test } from "node:test";
 import assert from "node:assert";
 import { Buffer } from "node:buffer";
+import fs from "node:fs";
+import path, { dirname } from "node:path";
+import { fileURLToPath } from "node:url";
 import { cleanupServers, findAvailablePort, HOST, launchServer, TransportMode, } from "./utils/server-launcher.js";
 import { findMockServerPort, MockGitLabServer } from "./utils/mock-gitlab-server.js";
 import { CustomHeaderClient } from "./clients/custom-header-client.js";
 const MOCK_TOKEN = "mock-concurrent-token-12345";
 const TEST_PROJECT_ID = "123";
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = dirname(__filename);
+const packageJsonPath = path.resolve(__dirname, "../package.json");
+const PACKAGE_VERSION = JSON.parse(fs.readFileSync(packageJsonPath, "utf8")).version;
 function fileResponse(filePath, content) {
     return {
         file_name: filePath.split("/").at(-1),
@@ -129,6 +136,14 @@ describe("Streamable HTTP health check capacity logging", { timeout: 20_000 }, (
         if (mockGitLab)
             await mockGitLab.stop();
     });
+    test("reports server version when healthy", async () => {
+        const response = await fetch(`${baseUrl}/health`);
+        const body = (await response.json());
+        assert.strictEqual(response.status, 200);
+        assert.strictEqual(body.status, "healthy");
+        assert.strictEqual(body.version, PACKAGE_VERSION);
+        assert.strictEqual(body.activeSessions, 0);
+    });
     test("logs active session capacity when health check is degraded", async () => {
         const client = new CustomHeaderClient({ Authorization: `Bearer ${MOCK_TOKEN}` });
         await client.connect(mcpUrl);
@@ -137,6 +152,7 @@ describe("Streamable HTTP health check capacity logging", { timeout: 20_000 }, (
             const body = (await response.json());
             assert.strictEqual(response.status, 503);
             assert.strictEqual(body.status, "degraded");
+            assert.strictEqual(body.version, PACKAGE_VERSION);
             assert.strictEqual(body.activeSessions, 1);
             assert.strictEqual(body.maxSessions, 1);
             // ponytail: poll stdout; fixed 100ms sleep flakes under CI jitter

package/build/test/test-health-check.js

@@ -1,8 +1,15 @@
 import { describe, test } from "node:test";
 import assert from "node:assert";
 import { spawn } from "child_process";
+import fs from "node:fs";
+import path, { dirname } from "node:path";
+import { fileURLToPath } from "node:url";
 import { MockGitLabServer, findMockServerPort } from "./utils/mock-gitlab-server.js";
 const MOCK_TOKEN = "glpat-mock-token-12345";
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = dirname(__filename);
+const packageJsonPath = path.resolve(__dirname, "../package.json");
+const PACKAGE_VERSION = JSON.parse(fs.readFileSync(packageJsonPath, "utf8")).version;
 function createMockGitLabServer(port) {
     return new MockGitLabServer({
         port,
@@ -73,6 +80,7 @@ describe("When health_check runs", () => {
                 const result = await callHealthCheckAsync(baseEnv(mockGitLab.getUrl()));
                 assert.equal(result.status, "ok");
                 assert.equal(result.authenticated, true);
+                assert.equal(result.mcp_server_version, PACKAGE_VERSION);
                 assert.equal(result.version, "18.3.1-ee");
                 assert.equal(result.revision, "abc1234");
                 assert.equal(result.enterprise, true);
@@ -94,6 +102,7 @@ describe("When health_check runs", () => {
                 const result = await callHealthCheckAsync(baseEnv(mockGitLab.getUrl()));
                 assert.equal(result.status, "ok");
                 assert.equal(result.authenticated, true);
+                assert.equal(result.mcp_server_version, PACKAGE_VERSION);
                 assert.equal("version" in result, false);
                 assert.equal("revision" in result, false);
                 assert.equal("enterprise" in result, false);

package/build/test/test-update-project.js

@@ -101,7 +101,7 @@ describe("update_project", () => {
         await assert.rejects(() => callUpdateProject({ project_id: TEST_PROJECT_ID, issues_access_level: "public" }, {
             GITLAB_API_URL: "https://gitlab.example.com/api/v4",
             GITLAB_PERSONAL_ACCESS_TOKEN: MOCK_TOKEN,
-        }), /Invalid enum value/);
+        }), /(Invalid enum value|Invalid option)/);
     });
     test("rejects empty updates before calling GitLab", async () => {
         await assert.rejects(() => callUpdateProject({ project_id: TEST_PROJECT_ID }, {

package/build/test/tool-description-quality.test.js

@@ -1,6 +1,11 @@
 import assert from "node:assert/strict";
 import { describe, it } from "node:test";
 import { allTools, TOOLSET_DEFINITIONS } from "../tools/registry.js";
+function getExposedTool(name) {
+    const tool = allTools.find(candidate => candidate.name === name);
+    assert.ok(tool);
+    return tool;
+}
 function getDefaultToolNames() {
     return new Set(TOOLSET_DEFINITIONS.filter(definition => definition.isDefault).flatMap(definition => [
         ...definition.tools,
@@ -17,9 +22,29 @@ describe("When MCP tool descriptions are exposed", () => {
     });
     describe("with create_branch", () => {
         it("should explain its source revision and neighboring branch operations", () => {
-            const tool = allTools.find(candidate => candidate.name === "create_branch");
-            assert.ok(tool);
+            const tool = getExposedTool("create_branch");
             assert.match(tool.description, /source branch|tag|commit[\s\S]*protect_branch[\s\S]*already-exists/i);
         });
     });
+    describe("with list_issues", () => {
+        it("should include issue-management guidance and omit group_id", () => {
+            const tool = getExposedTool("list_issues");
+            assert.match(tool.description, /issue management/i);
+            assert.doesNotMatch(tool.description, /group_id/);
+        });
+    });
+    describe("with my_issues", () => {
+        it("should include issue-management guidance and omit group_id", () => {
+            const tool = getExposedTool("my_issues");
+            assert.match(tool.description, /issue management/i);
+            assert.doesNotMatch(tool.description, /group_id/);
+        });
+    });
+    describe("with get_issue", () => {
+        it("should include issue-management guidance and omit group_id", () => {
+            const tool = getExposedTool("get_issue");
+            assert.match(tool.description, /issue management/i);
+            assert.doesNotMatch(tool.description, /group_id/);
+        });
+    });
 });

package/build/test/utils/merge-request-position.test.js

@@ -51,7 +51,7 @@ describe("When omitIncompleteMergeRequestPosition runs", () => {
                     start_sha: "ghi",
                     position_type: "text",
                 }),
-            }), /Expected string, received null/);
+            }), /expected string, received null/i);
         });
     });
 });

package/build/tools/registry.js

@@ -1,4 +1,3 @@
-import { zodToJsonSchema } from "zod-to-json-schema";
 import { toJSONSchema } from "../utils/schema.js";
 import { USE_GITLAB_WIKI, USE_MILESTONE, USE_PIPELINE, SSE, STREAMABLE_HTTP, } from "../config.js";
 import { getToolDescription } from "./tool-descriptions.js";
@@ -39,7 +38,7 @@ export const allTools = [
     {
         name: "execute_graphql",
         description: "Execute a GitLab GraphQL query",
-        inputSchema: zodToJsonSchema(ExecuteGraphQLSchema),
+        inputSchema: toJSONSchema(ExecuteGraphQLSchema),
     },
     {
         name: "create_or_update_file",
@@ -917,7 +916,7 @@ export const allTools = [
     },
     {
         name: "health_check",
-        description: "Verify server status and authentication. When authenticated, also reports the GitLab instance version from GET /api/v4/version (version, revision, enterprise). Version lookup failures do not fail the health check — those fields are omitted.",
+        description: "Verify server status and authentication. Always reports the MCP server version (mcp_server_version). When authenticated, also reports the GitLab instance version from GET /api/v4/version (version, revision, enterprise). Version lookup failures do not fail the health check — those fields are omitted.",
         inputSchema: toJSONSchema(HealthCheckSchema),
     },
     {

package/build/tools/tool-descriptions.js

@@ -8,6 +8,9 @@ const TOOL_GUIDANCE = {
     create_or_update_file: "Use this for a single repository file when you know whether the target path is new or already exists; use `push_files` for a multi-file commit. Optional `encoding` (`text` or `base64`) defaults to `GITLAB_REPO_FILE_ENCODING` so existing callers stay unchanged. The operation creates or updates remote content in a commit, requires repository write permission, and returns the commit result or a conflict/validation error.",
     push_files: "Use this to commit several file changes atomically; use `create_or_update_file` when only one path is involved. Each file defaults to action `create`; optional per-file `action` (create/update/delete/move) and `encoding` (text/base64) are additive. `GITLAB_PERMISSION_MODE=modify` rejects `delete` and `move`. The operation writes repository history on the selected branch, requires repository write permission, and returns the commit result or a validation, conflict, or protected-branch error.",
     create_issue: "Use this to open a new issue; use `update_issue` for an existing issue and `create_issue_note` to add discussion without changing issue fields. The operation creates remote project data, requires issue creation permission, and returns the new issue or a validation, permission, or duplicate-related error.",
+    list_issues: "Use this for issue management: list GitLab issues, optionally scoped with `project_id`. Use `get_issue` when the issue iid is already known and `my_issues` for issues assigned to the current user. It is read-only and paginated, requires issue read permission, and returns issue records or GitLab errors for invalid identifiers, missing resources, or rate limits.",
+    my_issues: "Use this for issue management: list issues assigned to the authenticated user. Use `list_issues` for project-wide or author-scoped listing and `get_issue` for one issue. It is read-only and paginated, requires authentication, and returns assigned issue records or permission/rate-limit errors.",
+    get_issue: "Use this for issue management: inspect one issue's fields; use `list_issues` or `my_issues` to discover issues first. It is read-only, requires issue read permission, and returns the issue or an error when the identifier is invalid, the issue is missing, or access is denied.",
     create_merge_request: "Use this to open a new merge request from an existing source branch to a target branch; use `update_merge_request` after it exists. The operation creates remote review state, requires project access, and returns the new merge request or a validation, permission, branch, or duplicate-related error.",
     fork_repository: "Use this to create a copy of an existing project in the current user's namespace or a permitted namespace; use `search_repositories` or `get_project` to inspect projects without copying them. The operation creates a new project, requires fork permission, and returns the forked project or a namespace/permission error.",
     create_branch: "Use this to create a branch from a branch, tag, or commit; use `get_branch` or `list_branches` to inspect branches and `protect_branch` to configure protection afterward. The operation changes remote repository state, requires branch-creation permission, and returns the new branch or a validation, missing-ref, protected-project, or already-exists error. `project_id` accepts a numeric ID or URL-encoded path, `branch` is the new name, and `ref` selects its starting revision.",

package/build/utils/schema.js

@@ -1,30 +1,50 @@
 import { z } from "zod";
-import { zodToJsonSchema } from "zod-to-json-schema";
 /**
  * Convert a Zod schema to JSON Schema, fixing nullable/optional fields
  * so they are not marked as required, and extracting required fields from the Zod schema.
  */
 export const toJSONSchema = (schema) => {
-    const jsonSchema = zodToJsonSchema(schema, { $refStrategy: "none" });
+    // Zod 4 native conversion. (zod-to-json-schema only understands Zod 3
+    // internals and silently emits an empty schema for Zod 4 schemas.)
+    // draft-7 keeps output closest to the previous converter; io:"input"
+    // describes tool arguments (preprocess/coerce evaluated input-side).
+    const jsonSchema = z.toJSONSchema(schema, { target: "draft-7", io: "input" });
+    // Public classes only (no _def access): works on both Zod 3 and Zod 4,
+    // whose internals differ (_def.typeName vs _zod.def.type).
     const isOptionalLikeField = (zodType) => {
-        const def = zodType._def;
-        const typeName = def?.typeName;
-        if (["ZodOptional", "ZodNullable", "ZodDefault", "ZodCatch"].includes(typeName)) {
+        if (zodType instanceof z.ZodOptional ||
+            zodType instanceof z.ZodNullable ||
+            zodType instanceof z.ZodDefault ||
+            zodType instanceof z.ZodCatch) {
             return true;
         }
-        if (typeName === "ZodEffects") {
-            return isOptionalLikeField(def.schema);
+        // ZodEffects (v3 preprocess/refine/transform): unwrap the inner schema.
+        const ZodEffects = z.ZodEffects;
+        if (ZodEffects &&
+            zodType instanceof ZodEffects &&
+            typeof zodType.innerType === "function") {
+            return isOptionalLikeField(zodType.innerType());
         }
-        if (typeName === "ZodBranded") {
-            return isOptionalLikeField(def.type);
+        // ZodBranded: unwrap to the branded schema.
+        const ZodBranded = z.ZodBranded;
+        if (ZodBranded &&
+            zodType instanceof ZodBranded &&
+            typeof zodType.unwrap === "function") {
+            return isOptionalLikeField(zodType.unwrap());
         }
-        if (typeName === "ZodPipeline") {
-            return isOptionalLikeField(def.in);
+        // Pipes (v3 ZodPipeline / v4 ZodPipe/ZodPreprocess from preprocess/transform):
+        // optional-like when either side is optional-like.
+        const maybeIn = zodType.in;
+        const maybeOut = zodType.out;
+        if (maybeIn instanceof z.ZodType && maybeOut instanceof z.ZodType) {
+            return isOptionalLikeField(maybeIn) || isOptionalLikeField(maybeOut);
         }
         return false;
     };
-    // Extract required fields from Zod schema
-    const zodRequiredFields = (() => {
+    // Extract required fields from Zod schema (authoritative for the root object:
+    // the native converter marks defaulted fields as required, we keep the
+    // previous convention that defaulted/optional-like fields are not required).
+    const { zodRequiredFields, hasAuthoritativeRequired } = (() => {
         if (schema instanceof z.ZodObject) {
             const shape = schema.shape;
             const requiredFields = [];
@@ -34,9 +54,9 @@ export const toJSONSchema = (schema) => {
                     requiredFields.push(key);
                 }
             });
-            return requiredFields;
+            return { zodRequiredFields: requiredFields, hasAuthoritativeRequired: true };
         }
-        return [];
+        return { zodRequiredFields: [], hasAuthoritativeRequired: false };
     })();
     // Post-process to fix nullable/optional fields and strip verbose keys
     function fixNullableOptional(obj, isRoot = false) {
@@ -47,14 +67,13 @@ export const toJSONSchema = (schema) => {
             delete obj.additionalProperties;
             // If this object has properties, process them
             if (obj.properties) {
-                const requiredSet = new Set(obj.required || []);
-                // Add required fields extracted from Zod schema (only for root object)
-                if (isRoot) {
-                    zodRequiredFields.forEach(field => {
-                        if (obj.properties[field]) {
-                            requiredSet.add(field);
-                        }
-                    });
+                let requiredSet;
+                if (isRoot && hasAuthoritativeRequired) {
+                    // Zod shape is the source of truth at root level.
+                    requiredSet = new Set(zodRequiredFields.filter(field => obj.properties[field]));
+                }
+                else {
+                    requiredSet = new Set(obj.required || []);
                 }
                 Object.keys(obj.properties).forEach(key => {
                     const prop = obj.properties[key];
@@ -66,6 +85,10 @@ export const toJSONSchema = (schema) => {
                     else if (Array.isArray(prop.type) && prop.type.includes("null")) {
                         requiredSet.delete(key);
                     }
+                    // Fields with defaults are not required (previous converter semantics).
+                    if (prop && typeof prop === "object" && "default" in prop) {
+                        requiredSet.delete(key);
+                    }
                     // Recursively process nested objects (not root)
                     obj.properties[key] = fixNullableOptional(prop, false);
                 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zereight/mcp-gitlab",
-  "version": "2.1.60",
+  "version": "2.1.62",
   "mcpName": "io.github.zereight/gitlab-mcp",
   "description": "GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more",
   "keywords": [
@@ -85,8 +85,7 @@
     "tldts": "^6.1.86",
     "tough-cookie": "^5.1.2",
     "undici": "^6.28.0",
-    "zod": "^3.24.2",
-    "zod-to-json-schema": "3.24.5"
+    "zod": "^4.6.5"
   },
   "devDependencies": {
     "@types/express": "^5.0.2",