v2.4.0 — plugin runs without Node, credentials from a config file

Download jira-mcp.plugin to install. Add jira-mcp.exe as well if the machine has no Node.

The plugin now works without Node

It launches through bin/jira-mcp.cmd, which resolves a runtime at startup:

Order	Source
1	JIRA_MCP_EXE — full path to the executable
2	jira-mcp.exe sitting in the plugin folder
3	node server.js

So a machine with no Node gets the full plugin, skills included:

setx JIRA_MCP_EXE "C:\Tools\jira-mcp.exe"

If none resolve, the launcher reports no runtime found on stderr rather than failing silently.

Credentials — environment variables or a config file

Resolution order, first hit wins:

1. JIRA_BASE_URL / JIRA_PAT environment variables
2. the path in JIRA_MCP_CONFIG
3. .jira-mcp.json in your home folder
4. jira-mcp.config.json beside the server or the executable

{ "baseUrl": "https://your-jira-host", "pat": "your-personal-access-token" }

The startup banner reports which source was used, never the value.

Do not put a token in the plugin's .mcp.json. That file ships inside the .plugin archive, so it would be shared with everyone you send it to. The four locations above sit outside the packaged artifact, and the packager refuses to build if it finds a literal credential in anything it would include.

Verified

The packaged plugin was extracted, Node was removed from PATH, and it was launched through its own declared command — 21 tools served with a clean stdout stream. Full suite: plugin validation, 24 library assertions across both runtimes, 5 credential-resolution assertions, 5 launcher assertions, 7 executable assertions.