feat: enable write access in MCPB bundle (1.17.0)#37
Merged
Conversation
The Claude Desktop / MCPB bundle now exposes a single GITLAB_TOKEN field instead of GITLAB_READ_TOKEN, letting users pick the PAT scope themselves — read_api for read-only, api for read+write. Drops the 'read-only' qualifier from the display name and description. Existing installs will prompt to re-enter the PAT on upgrade because the user_config field was renamed gitlab_read_token → gitlab_token.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
GITLAB_TOKENinstead ofGITLAB_READ_TOKEN. Users pick the scope:read_apifor read-only,apito also allow writes.package.json,.claude-plugin/plugin.json,package-lock.json.Upgrade impact
Existing MCPB installs will prompt the user to re-enter the PAT on upgrade because the
user_configfield key changed (gitlab_read_token→gitlab_token). Called out in the CHANGELOG.Server-side behavior unchanged
The four-step token resolution in
gitlab-client.tsalready supportsGITLAB_TOKENfor both reads and writes — this PR only changes which env var the bundle wires up.Test plan
release.ymlproducesgitlab-mcp-community-1.17.0.mcpband attaches it to the v1.17.0 GitHub Releaseapi-scoped PAT, confirm a write tool (e.g.create_note) succeeds