@jam-mcp/server 1.0.0 → 1.0.1

package/README.md

@@ -38,22 +38,29 @@ source, that source is what settles the question.
 
 ## Running it
 
-Normally you don't run this package directly — your coding agent launches
+Don't install this package to use JAM. Your coding agent launches
 [`@jam-mcp/launcher`](https://www.npmjs.com/package/@jam-mcp/launcher), which
-resolves which JAM build this machine runs and dispatches here. Going through
-the launcher is what keeps a committed `.mcp.json` free of machine-specific
-paths.
+reads your `~/.jam/config.yaml`, decides which JAM build this machine should
+run, and dispatches here. Naming the server directly instead pins one machine
+to one build and bypasses that choice — and it is what keeps a committed
+`.mcp.json` free of machine-specific paths.
 
-The `jam` CLI is the same binary:
+The same binary carries the CLI, and every command below is reachable through
+the launcher:
 
 ```text
-jam serve      Run the MCP server over stdio
-jam doctor     Diagnose config, credentials and Jira connectivity
-jam setup      Wire up JAM and verify (personal by default; --shared for the team)
-jam auth login Store Jira credentials in this user's OS secret store
-jam runtime    Show or change which JAM build this machine runs
+serve        Run the MCP server over stdio
+doctor       Diagnose config, credentials and Jira connectivity
+setup        Wire up JAM and verify (personal by default; --shared for the team)
+auth login   Store Jira credentials in this user's OS secret store
+runtime      Show or change which JAM build this machine runs
 ```
 
+Written out, that is `npx --yes @jam-mcp/launcher@1.0.1 doctor`, or just `jam
+doctor` if you took the launcher's optional global install. Starting from
+nothing — no install, no runtime chosen yet — use
+`npx --yes @jam-mcp/bootstrap@1.0.1 init` instead.
+
 Credentials come from the process environment or this user's OS secret store —
 never from a repository file — and never appear in logs, telemetry, or tool
 results. `stdout` is reserved for the MCP protocol and for JSON output;

package/dist/bootstrap/mcp-config-merger.d.ts

@@ -1,3 +1,4 @@
+import { LAUNCHER_PACKAGE_SPEC } from "@jam-mcp/launcher";
 /**
  * The canonical jam entry for a project's `.mcp.json`.
  *
@@ -9,10 +10,10 @@
  * Pinned to an exact version. A floating tag would silently change what a
  * teammate's editor launches.
  */
-export declare const LAUNCHER_PACKAGE_SPEC = "@jam-mcp/launcher@1.0.0";
+export { LAUNCHER_PACKAGE_SPEC };
 export declare const JAM_MCP_ENTRY: {
     readonly command: "npx";
-    readonly args: readonly ["--yes", "@jam-mcp/launcher@1.0.0", "serve"];
+    readonly args: readonly ["--yes", "@jam-mcp/launcher@1.0.1", "serve"];
 };
 /**
  * Recognise wiring from before the launcher existed: a hard-coded path to one
@@ -48,11 +49,11 @@ export declare function inspectMcpConfig(root: string): McpInspection;
  */
 export declare function writeJamMcpEntry(root: string, entry?: unknown): string;
 /**
- * Merge a PATH-based JAM entry into `.mcp.json`, preserving everything else.
+ * Merge the launcher entry into `.mcp.json`, preserving everything else.
  *
- * Deliberately does NOT record an absolute path to this JAM checkout - that
- * would break the moment a teammate clones to a different location. `command:
- * "jam"` relies on `jam` being on PATH (see `jam setup`'s PATH check), which is
- * what keeps this file safe to commit and share.
+ * Deliberately records neither an absolute path to a JAM checkout nor a bare
+ * `jam` - the first breaks the moment a teammate clones somewhere else, and
+ * the second assumes an optional global install every teammate would have to
+ * have made. `npx` at an exact launcher version assumes only npm.
  */
 export declare function mergeMcpConfig(root: string): McpMergeResult;

package/dist/bootstrap/mcp-config-merger.js

@@ -1,6 +1,6 @@
 import { existsSync, readFileSync, writeFileSync } from "node:fs";
 import { join } from "node:path";
-import { SERVER_VERSION } from "@jam-mcp/launcher";
+import { LAUNCHER_PACKAGE_SPEC } from "@jam-mcp/launcher";
 /**
  * The canonical jam entry for a project's `.mcp.json`.
  *
@@ -12,7 +12,7 @@ import { SERVER_VERSION } from "@jam-mcp/launcher";
  * Pinned to an exact version. A floating tag would silently change what a
  * teammate's editor launches.
  */
-export const LAUNCHER_PACKAGE_SPEC = `@jam-mcp/launcher@${SERVER_VERSION}`;
+export { LAUNCHER_PACKAGE_SPEC };
 export const JAM_MCP_ENTRY = {
     command: "npx",
     args: ["--yes", LAUNCHER_PACKAGE_SPEC, "serve"],
@@ -86,12 +86,12 @@ export function writeJamMcpEntry(root, entry = JAM_MCP_ENTRY) {
     return path;
 }
 /**
- * Merge a PATH-based JAM entry into `.mcp.json`, preserving everything else.
+ * Merge the launcher entry into `.mcp.json`, preserving everything else.
  *
- * Deliberately does NOT record an absolute path to this JAM checkout - that
- * would break the moment a teammate clones to a different location. `command:
- * "jam"` relies on `jam` being on PATH (see `jam setup`'s PATH check), which is
- * what keeps this file safe to commit and share.
+ * Deliberately records neither an absolute path to a JAM checkout nor a bare
+ * `jam` - the first breaks the moment a teammate clones somewhere else, and
+ * the second assumes an optional global install every teammate would have to
+ * have made. `npx` at an exact launcher version assumes only npm.
  */
 export function mergeMcpConfig(root) {
     const path = join(root, ".mcp.json");

package/dist/bootstrap/setup-plan.d.ts

@@ -57,6 +57,14 @@ export type SetupPlan = {
     }[];
     /** Why a requested migration was refused, when status is JAM_MIGRATION_TARGET_UNAVAILABLE. */
     migrationTarget?: MigrationTarget;
+    /**
+     * What a person or an agent has to do next.
+     *
+     * `command` is executable on a machine with nothing installed and no runtime
+     * configured - so it is an `npx` bootstrap invocation, never a bare `jam`.
+     * A human interface is free to render the short form; this field is the one
+     * a script runs, and a script has no PATH to rely on.
+     */
     nextAction?: {
         type: "authenticate" | "select_project" | "configure_runtime";
         command?: string;

package/dist/bootstrap/setup-plan.js

@@ -3,6 +3,7 @@ import { CONFIG_RELATIVE_PATH } from "../config/load-config.js";
 import { hostRegistration } from "./host-mcp.js";
 import { projectBindingsPath } from "./project-bindings.js";
 import { decideProjectKey } from "./project-config-bootstrapper.js";
+import { portableBootstrapCommand } from "@jam-mcp/launcher";
 /**
  * Decide what setup would do, changing nothing.
  *
@@ -47,7 +48,7 @@ export function computeSetupPlan(state, options = {}) {
             code: "JAM_PROJECT_SELECTION_REQUIRED",
             changes: [],
             requiresUserAction: true,
-            nextAction: { type: "select_project", command: "jam setup --project <KEY>" },
+            nextAction: { type: "select_project", command: portableBootstrapCommand("setup --project <KEY>") },
             project: { root: state.project.root },
         };
     }
@@ -122,7 +123,7 @@ function finish(changes, state, project) {
             code: "JAM_RUNTIME_CONFIG_MISSING",
             changes,
             requiresUserAction: true,
-            nextAction: { type: "configure_runtime", command: "jam runtime use package" },
+            nextAction: { type: "configure_runtime", command: portableBootstrapCommand("runtime use package") },
             project,
         };
     }

package/dist/cli/setup-wizard.js

@@ -133,7 +133,7 @@ async function chooseRuntime(ui, options) {
         {
             value: "package",
             label: "Use JAM",
-            hint: "Run the project-pinned package. Recommended for most users.",
+            hint: "Run the published JAM release. Recommended for most users.",
         },
         { value: "development", label: "Develop JAM", hint: "Run a local source checkout." },
     ], "Run: jam runtime use package");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jam-mcp/server",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "JAM (Jira Agent MCP) - agent-facing Jira access layer: MCP server, setup core, and CLI",
   "keywords": [
     "jira",
@@ -22,7 +22,7 @@
   "author": "colosair (https://github.com/colosair)",
   "type": "module",
   "bin": {
-    "jam": "dist/index.js"
+    "jam-server": "dist/index.js"
   },
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -41,7 +41,7 @@
     "test:watch": "vitest"
   },
   "dependencies": {
-    "@jam-mcp/launcher": "1.0.0",
+    "@jam-mcp/launcher": "1.0.1",
     "@modelcontextprotocol/sdk": "^1.30.0",
     "yaml": "^2.9.0",
     "zod": "^4.4.3"