Reading a JIRA issue is a small feature. Doing it without a long-lived API token sitting in a plaintext MCP settings file is not — that file is easy to sync, easy to back up, and easy to forget about. Resolving the token from 1Password at launch is a pattern worth copying even if you end up using a fuller JIRA server. The scope here really is one read: no creating, no commenting, no search.
A small MCP server that fetches JIRA issue details by key. What distinguishes it is the credential handling: the JIRA API token is not written into the client config — the config holds a 1Password reference, and a start script resolves it through the 1Password CLI when the server launches.
- The full detail of a JIRA issue from its key, such as `PROJ-123`, read into the conversation — `get_issue`
- A credential path that keeps the token out of your settings file: `JIRA_API_TOKEN` holds an `op://` reference, and `start-server.sh` resolves it via the 1Password CLI at launch
- Working configuration for a VS Code MCP settings file, which is where the setup usually goes wrong
A JIRA API token from id.atlassian.com, stored in 1Password; the 1Password desktop app with CLI integration enabled, and the 1Password CLI installed. Three variables: `JIRA_HOST` for your Atlassian domain, `JIRA_EMAIL` for the account, and `JIRA_API_TOKEN` holding the 1Password field path. There is no published package: clone, `npm install`, `npm run build`, and point the client at `start-server.sh`. The README is written in Japanese.
One command plus a key — npx -y mcp-server-jira, then supply credentials