Jira Mcp Server — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Jira Mcp Server (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
An MCP (Model Context Protocol) server that lets AI assistants create, search, and manage Jira issues. Authenticates using Chrome browser cookies, so it works seamlessly with SSO-protected Jira Cloud instances -- no API tokens needed.
Instead of requiring a Jira API token, this server extracts session cookies from your Chrome browser. If you're logged into Jira in Chrome, the server can make API calls using your existing session. This is especially useful for organizations that use SSO (Azure AD, Okta, etc.) where generating long-lived API tokens isn't practical.
git clone https://github.com/chaholl/jira-mcp-server.git
cd jira-mcp-server
npm install
npm run build
npm run setup # interactive wizard -- discovers your Jira instance configThe setup wizard will:
jira-config.json file (gitignored)| Tool | Description |
|---|---|
jira_auth_check | Verify authentication and display the current user |
jira_create_issue | Create a new issue (story, bug, task, etc.) |
jira_get_issue | Fetch and display an issue by key |
jira_edit_description | Update an issue's description |
jira_edit_acceptance_criteria | Update the acceptance criteria field |
jira_add_comment | Add a comment to an issue |
jira_transition_issue | Move an issue to a new status |
jira_search | Search issues using JQL |
jira_lookup_user | Look up a user's account ID by email |
jira_list_components | List available project components |
jira_reassign_issue | Reassign an issue to a different user |
jira_reparent_issue | Change an issue's parent (epic/story) |
npm run setupThis interactively discovers your Jira instance's issue types, priorities, and custom fields, then writes jira-config.json.
Alternatively, set environment variables:
export JIRA_BASE_URL="https://your-org.atlassian.net"
export JIRA_PROJECT_KEY="MYPROJECT"Or create jira-config.json in the project root:
{
"jiraBaseUrl": "https://your-org.atlassian.net",
"projectKey": "MYPROJECT",
"issueTypes": {
"story": "10001",
"bug": "10004",
"task": "10002"
},
"priorities": {
"critical": "1",
"high": "2",
"medium": "3",
"low": "4"
},
"customFields": {
"acceptance_criteria": "customfield_11083"
}
}claude mcp add jira -- node /path/to/jira-mcp-server/dist/index.jsAdd to your claude_desktop_config.json:
{
"mcpServers": {
"jira": {
"command": "node",
"args": ["/path/to/jira-mcp-server/dist/index.js"]
}
}
}secret-tool for keyring accessMIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.