@jam-mcp/bootstrap 1.0.0 → 1.0.1
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.
- package/README.md +15 -9
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -6,8 +6,8 @@ This package exists so the *first* command a person or a coding agent runs needs
|
|
|
6
6
|
nothing installed beforehand:
|
|
7
7
|
|
|
8
8
|
```bash
|
|
9
|
-
npx --yes @jam-mcp/bootstrap@1.0.
|
|
10
|
-
npx --yes @jam-mcp/bootstrap@1.0.
|
|
9
|
+
npx --yes @jam-mcp/bootstrap@1.0.1 init # for a person
|
|
10
|
+
npx --yes @jam-mcp/bootstrap@1.0.1 setup --agent # for a coding agent, JSON only
|
|
11
11
|
```
|
|
12
12
|
|
|
13
13
|
`init` chooses how JAM runs on this machine and wires up the current project.
|
|
@@ -19,20 +19,26 @@ authenticating).
|
|
|
19
19
|
|
|
20
20
|
It is an end-user entry point, but it holds **no setup logic of its own**. It
|
|
21
21
|
depends on `@jam-mcp/server` at an exact version and forwards to the same
|
|
22
|
-
commands
|
|
23
|
-
|
|
24
|
-
|
|
22
|
+
commands JAM's own CLI would run; anything other than `init` is passed through
|
|
23
|
+
unchanged. Any decision made here would be a second implementation to keep in
|
|
24
|
+
sync with the setup core.
|
|
25
|
+
|
|
26
|
+
That pass-through is also why bootstrap is what JAM names in machine-readable
|
|
27
|
+
instructions. On a machine that has just met JAM there is no global command to
|
|
28
|
+
call and no configured runtime for the launcher to dispatch to — bootstrap
|
|
29
|
+
needs neither, so `npx --yes @jam-mcp/bootstrap@1.0.1 <anything>` works when
|
|
30
|
+
nothing else does.
|
|
25
31
|
|
|
26
32
|
The three packages divide up like this:
|
|
27
33
|
|
|
28
34
|
| Package | Role |
|
|
29
35
|
|---|---|
|
|
30
|
-
| `@jam-mcp/bootstrap` | first run
|
|
36
|
+
| `@jam-mcp/bootstrap` | first run and recovery — needs nothing installed |
|
|
31
37
|
| `@jam-mcp/launcher` | what a coding agent registers; resolves which JAM build runs |
|
|
32
|
-
| `@jam-mcp/server` | JAM itself: MCP tools, setup core,
|
|
38
|
+
| `@jam-mcp/server` | JAM itself: MCP tools, setup core, CLI |
|
|
33
39
|
|
|
34
|
-
|
|
35
|
-
|
|
40
|
+
Day to day you don't need this package: your coding agent launches the
|
|
41
|
+
launcher, and if you installed the launcher globally you have `jam` too.
|
|
36
42
|
|
|
37
43
|
## More
|
|
38
44
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@jam-mcp/bootstrap",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.1",
|
|
4
4
|
"description": "Zero-install entry point for JAM (Jira Agent MCP) - first-run setup for humans and coding agents",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"jira",
|
|
@@ -37,7 +37,7 @@
|
|
|
37
37
|
"build": "tsc"
|
|
38
38
|
},
|
|
39
39
|
"dependencies": {
|
|
40
|
-
"@jam-mcp/server": "1.0.
|
|
40
|
+
"@jam-mcp/server": "1.0.1"
|
|
41
41
|
},
|
|
42
42
|
"devDependencies": {
|
|
43
43
|
"@types/node": "^24.0.0",
|