Repository navigation
Releases
Releases · hacctarr/jira-mcp-bearer
v2.0.0
Changed
- BREAKING: credentials are now read from environment variables only (
JIRA_BASE_URL,JIRA_BEARER_TOKEN).config.jsonin the package directory is no longer read. Previously a config file took precedence over the environment, so a stale file could silently override the active token, and it kept a plaintext credential on disk outside the MCP client's own configuration. Migrate by passing both variables in the MCP server registration'senvblock. With neither variable set the server now exits at startup with an error on stderr instead of falling back to a file.
Removed
setup.jsinteractive setup andconfig.json.example(both existed only to produce the now-unsupported config file).
First release published via npm Trusted Publishing (OIDC) with provenance.
v1.6.0
1.6.0
Three capabilities that were previously unreachable through the MCP, plus completed CRUD over comments.
Status-transition history (changelog)
jira-get-issue-changelogparsesexpand=changeloginto a status timeline with the exact wall-clock duration spent in each status, answering "how long did this sit in a status before another" from real transition timestamps.jira-get-issuegained anexpandparam.changelogis a Jira EXPAND, not a field, so it could not be requested through the oldfields-only tool.- New pure module
lib/changelog.js; surfaces a truncation warning if the server returns fewer entries thanchangelog.total.
Priority
jira-list-prioritieslists the instance's priorities (id + name), mirroringjira-list-statuses.jira-create-issue/jira-update-issuegained apriorityparam (name or numeric id), normalized and applied so it wins over anyfields.priority. Setting priority still depends on the project's screen/field configuration allowing it.
Comments (CRUD completed)
jira-update-comment— edit a comment body (PUT .../comment/{id}).jira-delete-comment— delete a comment (DELETE .../comment/{id}).
Tests
+47 tests (105 to 152), all green. 35 tools total.
v1.5.0
v1.1.2 - Fix npm Package Files
Fixed
- Removed references to non-existent QUICKSTART.md and EXAMPLES.md files from package.json
- This fixes the npm publish workflow failure
Previous Changes (v1.1.0-v1.1.1)
- Added concise format option to prevent token limit errors
- Added lib/ and tools/ directories to npm package
- Fixed npm publish workflow to use NPM_TOKEN secret
v1.1.1 - Fix Missing Directories
Fixed
- Critical: Fixed npm package missing
lib/andtools/directories- Added
lib/andtools/to package.jsonfilesarray - v1.1.0 was published with missing dependencies and was broken
- This patch fixes the installation issue
- Added
Note
Please upgrade from v1.1.0 to v1.1.1 - v1.1.0 is broken and cannot be installed.
npm install -g jira-mcp-bearer@1.1.1All features from v1.1.0 are included in this release.
v1.1.0 - Concise Format Option
What's New
Concise Format Option - Solve token limit errors with an opt-in parameter! 🎉
New Feature
Add format: "concise" to search tools to get readable text with essential fields instead of verbose JSON:
- Reduces token usage by ~95% (10 results: 48,000 → 2,000 tokens)
- Available on:
jira-search-issues,jira-get-my-issues,jira-get-recent-issues - No breaking changes - default behavior unchanged
Example
// Opt into concise format to avoid token limits:
mcp__jira__jira-search-issues({
jql: "project = DEV AND status = Open",
maxResults: 10,
format: "concise" // ← Add this
})Output:
Total: 15, Returned: 10, StartAt: 0, MaxResults: 10
DEV-123: Login page not loading
Status: Open | Assignee: John Doe | Priority: High
Created: 2025-01-01 | Updated: 2025-01-15
DEV-124: Dashboard showing wrong data
Status: In Progress | Assignee: Jane Smith | Priority: Medium
Created: 2025-01-02 | Updated: 2025-01-16
Full Changelog
See CHANGELOG.md for details.