@jmrp.io/gitlab-mcp-server 2.7.5 → 3.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +10 -9
  2. package/cli.js +10 -11
  3. package/package.json +9 -7
package/README.md CHANGED
@@ -44,20 +44,21 @@ gitlab-mcp-server --help
44
44
  `GITLAB_URL` and `GITLAB_TOKEN` are the two required environment variables in
45
45
  stdio mode. Every flag and variable — HTTP mode, OAuth, read-only and safe
46
46
  modes, tool surfaces, tiers — is documented in the
47
- [configuration reference](https://jmrp.io/docs/gitlab-mcp-server/reference/configuration).
47
+ [configuration reference](https://jmrp.io/docs/gitlab-mcp-server/configuration/).
48
48
 
49
- ## Auto-update is off under npm
49
+ ## Updating
50
50
 
51
- The server can update itself in place, but that is disabled here: npm owns the
52
- binary, and letting it replace itself would desynchronize what npm has
53
- recorded. Update with your package manager instead (`npm update -g
54
- @jmrp.io/gitlab-mcp-server`). Setting `AUTO_UPDATE` explicitly still takes
55
- effect if you have a reason to override it.
51
+ `npm update -g @jmrp.io/gitlab-mcp-server`. The server never replaces its own
52
+ binary, on this or any other channel.
56
53
 
57
54
  ## Supported platforms
58
55
 
59
- Linux, macOS and Windows, on x64 and arm64. On any other platform the launcher
60
- exits with a message pointing to the
56
+ Linux, macOS and Windows, on x64 and arm64. The Linux packages declare
57
+ `libc: ["glibc"]`: the prebuilt binaries are PIE ELF executables that need the
58
+ glibc dynamic loader, so npm skips them on musl distributions such as Alpine.
59
+ Run the [Docker image](https://github.com/jmrplens/gitlab-mcp-server/pkgs/container/gitlab-mcp-server)
60
+ there, which is musl-based, or build from source. On any other platform the
61
+ launcher exits with a message pointing to the
61
62
  [release binaries](https://github.com/jmrplens/gitlab-mcp-server/releases) and
62
63
  the option to build from source.
63
64
 
package/cli.js CHANGED
@@ -11,6 +11,7 @@
11
11
  "use strict";
12
12
 
13
13
  const { spawnSync } = require("node:child_process");
14
+ const os = require("node:os");
14
15
 
15
16
  // platformKey maps Node's platform/arch names to the per-platform package
16
17
  // suffix. The suffixes follow Node's vocabulary (win32, x64), not Go's
@@ -74,18 +75,14 @@ if (!binary) {
74
75
  `the @jmrp.io/gitlab-mcp-server-${key} package is not installed. ` +
75
76
  "It is an optional dependency that carries the binary for this platform; " +
76
77
  "reinstall without --no-optional, or delete node_modules and the lockfile " +
77
- "and install again.",
78
+ "and install again. On musl systems (Alpine) the linux packages are " +
79
+ "skipped on purpose: the prebuilt binaries need the glibc dynamic loader — " +
80
+ "use the Docker image (musl-based) or build from source instead " +
81
+ "(https://github.com/jmrplens/gitlab-mcp-server).",
78
82
  );
79
83
  }
80
84
 
81
- // Self-update must stay off: npm owns this binary, and letting it replace
82
- // itself on disk would desynchronize what npm believes is installed — the same
83
- // reason the Homebrew formula and the Claude Desktop manifest pin it off. An
84
- // explicit AUTO_UPDATE from the caller still wins.
85
85
  const env = { ...process.env };
86
- if (env.AUTO_UPDATE === undefined) {
87
- env.AUTO_UPDATE = "false";
88
- }
89
86
 
90
87
  const result = spawnSync(binary, process.argv.slice(2), {
91
88
  stdio: "inherit",
@@ -99,8 +96,10 @@ if (result.error) {
99
96
  // so the launcher dies the same way rather than masking a SIGINT as exit 0.
100
97
  if (result.signal) {
101
98
  process.kill(process.pid, result.signal);
102
- // If the re-raise did not terminate us (signal ignored), fall through to a
103
- // conventional 128+signal code so the caller still sees a failure.
104
- process.exit(1);
99
+ // If the re-raise did not terminate us (signal ignored, or no default
100
+ // disposition), exit with the conventional 128+signal code so the caller
101
+ // still sees the child's terminating signal rather than a bare failure.
102
+ const signum = os.constants.signals[result.signal];
103
+ process.exit(signum ? 128 + signum : 1);
105
104
  }
106
105
  process.exit(result.status === null ? 1 : result.status);
package/package.json CHANGED
@@ -1,6 +1,7 @@
1
1
  {
2
2
  "name": "@jmrp.io/gitlab-mcp-server",
3
- "version": "2.7.5",
3
+ "version": "3.1.0",
4
+ "mcpName": "io.github.jmrplens/gitlab-mcp-server",
4
5
  "description": "Model Context Protocol (MCP) server exposing GitLab REST v4 and GraphQL as tools for AI assistants. Runs as a local binary over stdio or HTTP.",
5
6
  "keywords": [
6
7
  "mcp",
@@ -20,6 +21,7 @@
20
21
  "directory": "npm/gitlab-mcp-server"
21
22
  },
22
23
  "license": "MIT",
24
+ "funding": "https://github.com/sponsors/jmrplens",
23
25
  "author": "José M. Requena Plens",
24
26
  "type": "commonjs",
25
27
  "bin": {
@@ -30,12 +32,12 @@
30
32
  "README.md"
31
33
  ],
32
34
  "optionalDependencies": {
33
- "@jmrp.io/gitlab-mcp-server-linux-x64": "2.7.5",
34
- "@jmrp.io/gitlab-mcp-server-linux-arm64": "2.7.5",
35
- "@jmrp.io/gitlab-mcp-server-darwin-x64": "2.7.5",
36
- "@jmrp.io/gitlab-mcp-server-darwin-arm64": "2.7.5",
37
- "@jmrp.io/gitlab-mcp-server-win32-x64": "2.7.5",
38
- "@jmrp.io/gitlab-mcp-server-win32-arm64": "2.7.5"
35
+ "@jmrp.io/gitlab-mcp-server-linux-x64": "3.1.0",
36
+ "@jmrp.io/gitlab-mcp-server-linux-arm64": "3.1.0",
37
+ "@jmrp.io/gitlab-mcp-server-darwin-x64": "3.1.0",
38
+ "@jmrp.io/gitlab-mcp-server-darwin-arm64": "3.1.0",
39
+ "@jmrp.io/gitlab-mcp-server-win32-x64": "3.1.0",
40
+ "@jmrp.io/gitlab-mcp-server-win32-arm64": "3.1.0"
39
41
  },
40
42
  "engines": {
41
43
  "node": ">=18"