feat: build mcpb bundle and attach to github releases (1.15.2)#34
Merged
Conversation
Adds a one-click install path for Claude Desktop. The Release workflow
now produces gitlab-mcp-community-${VERSION}.mcpb alongside the existing
npm and GHCR artifacts and attaches it to each GitHub Release.
- mcpb/manifest.template.json describes the bundle: name
gitlab-mcp-community, display name "GitLab (community, read-only)"
to disambiguate from GitLab Inc.'s first-party MCP server. Exposes
GITLAB_URL and GITLAB_READ_TOKEN as user_config; the read token is
marked sensitive so OS keychain storage applies. Writes are not
exposed in the bundle — users needing write access install via npm
or GHCR.
- scripts/build-mcpb.mjs runs npm pack, installs the tarball into
dist-mcpb/ with --omit=dev --ignore-scripts, substitutes the version
in the manifest, and zips manifest.json + node_modules into the
final .mcpb. Invoked as `npm run build:mcpb`.
- release.yml: new "Build MCPB bundle" step plus an asset arg on
gh release create, so the bundle ships with every tag push.
- README: documents the drag-and-drop install option in the Claude
Desktop section and points to the latest release.
- .gitignore: ignores dist-mcpb/ and *.mcpb so local builds stay out
of the repo.
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-mcp-community-${VERSION}.mcpb— a drag-and-drop install bundle for Claude Desktop. The Release workflow now attaches it to each GitHub Release alongside the existing npm and GHCR artifacts.GITLAB_READ_TOKENonly). Display nameGitLab (community, read-only)and namegitlab-mcp-communitydisambiguate from GitLab Inc.'s first-party MCP server. Users who need write access install via npm or GHCR.Implementation
mcpb/manifest.template.json— versioned manifest with__VERSION__placeholder, substituted at build time.scripts/build-mcpb.mjs— runsnpm pack, installs the tarball intodist-mcpb/with--omit=dev --ignore-scripts --no-package-lock, writes the manifest, then zipsmanifest.json+node_modules/intogitlab-mcp-community-${VERSION}.mcpb. Local build verified at 5.7 MB..github/workflows/release.yml— new "Build MCPB bundle" step plus a positional asset arg ongh release create..gitignore— ignoresdist-mcpb/and*.mcpb.Test plan
npm run build:mcpblocally — produces 5.7 MB bundlenode node_modules/@ttpears/gitlab-mcp-server/dist/index.jswithGITLAB_READ_TOKENset — server starts, loads config, attempts introspection (401 with fake token as expected), continues listeningv1.15.2tag firesrelease.yml, MCPB attached to the GitHub release