Repository navigation
JAM v1.4.6
JAM 1.4.6 lets a session read Jira before it can see the tools. A session that
registers JAM cannot be shown the tools it just registered — Claude Code has no
reload for a running session — so jam jira search | context | full addresses the
same reads to the shell. The five-tool MCP surface is unchanged.
What changed
jam jira search <jql> [--scope preview|complete],jam jira context <KEY>…
andjam jira full <KEY>…. Each calls the same application function its MCP
tool calls, through the same deps, with the same field and pagination policies
and the samemeta—complete,evidenceScopeandlimitationsincluded.
Nothing here re-implements a read, and nothing here is a second source of
truth.- A failure is the same normalized error code the tools return.
error.code,
not a stack trace, so a caller reads one contract rather than two. - stdout stays one JSON document. Usage and diagnostics go to stderr, and an
invalid--scopeis refused before any request reaches Jira. - Reads only. Writing stays behind plan-then-apply, where a person's gate is.
Why
An agent that had just installed JAM was told to wait for its next session. What
it did instead was the substitution JAM exists to prevent: it answered Jira
questions from the code host, the git log and project documents. The tools being
unreachable for one session is a host constraint; answering from the wrong source
is a correctness failure, and this closes it.
Install / Upgrade
npx --yes @jam-mcp/bootstrap@1.4.6 initOptional persistent command:
npm install -g @jam-mcp/launcher@1.4.6Existing users: re-run setup. Bindings, runtime selection, host registration and
credentials are untouched.
Agent setup
The canonical entry is unchanged:
npx --yes @jam-mcp/bootstrap@1.4.6 setup --agentCompatibility
- Node 20 or newer, unchanged. The five-tool MCP surface is unchanged — same
names, same input schemas, same results. - Additive CLI only: a new
jiracommand group. Nothing existing changed shape. - No GitHub/GitLab runtime dependency.
Verified
- Build, launcher + server tests (488 passing),
release:check, pack and tarball
smoke — green locally and on CI (Ubuntu/Windows × Node 20/22). - Six new tests fix the shape: one JSON document, a multi-word JQL staying one
query, keys read as given,--scopepassed through and a bad one refused
before any read, a normalized error payload, and usage on stderr. - Read a real Jira issue through
jam jira searchfrom a shell in a session
whose MCP tools were registered afterwards. Zero mutations.
Known limitations
- Writes are not addressed to the shell. Creating or updating an issue stays
a two-step plan-then-apply through the MCP tools, where the person's gate is. - This does not make MCP tools appear in a running session. It is the read,
reachable another way, for the session that cannot see them yet. - Live
issue.createremains unexercised, as in 1.4.5, for the same reason:
an unwanted issue on a real board is not worth a disposable fixture.