ModelsAtlas
Explore
Atlas / MCP servers / camdenclark / Jira

JiraSAFE

mcp/camdenclark/jira-1
MCP server by camdenclark · Audited 2026-10-08
⚑ Report / re-scanSource ↗
Verdict
SAFE
Grade
B
Trust score
89 /100
Exposed tools
2 2r · 0w · 0d
Transport
stdio
License
MIT
Stars
28
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

[](https://smithery.ai/server/jira-mcp)

An MCP server that enables Large Language Models (LLMs) to interact with JIRA through standardized tools and context. This server provides capabilities for searching issues using JQL and retrieving detailed issue information.

Features

  • JQL Search: Execute complex JQL queries with pagination support
  • Issue Details: Retrieve detailed information about specific JIRA issues

Prerequisites

  • npm installed
  • A JIRA instance with API access
  • JIRA API token or Personal Access Token
  • JIRA user email associated with the API token

Getting JIRA API Credentials

  1. Log in to your Atlassian account at https://id.atlassian.com
  2. Navigate to Security settings
  3. Under API tokens, select "Create API token"
  4. Give your token a meaningful name (e.g., "MCP Server")
  5. Copy the generated token - you won't be able to see it again!
  6. Use this token as your JIRA_API_KEY
  7. Use the email address associated with your Atlassian account as JIRA_USER_EMAIL

Usage

Integration with Claude Desktop

  1. Add the server configuration to Claude Desktop's config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
"mcpServers": {
"jira": {
"command": "npx",
"args": ["-y", "jira-mcp"],
"env": {
"JIRA_INSTANCE_URL": "https://your-instance.atlassian.net",
"JIRA_USER_EMAIL": "[email protected]",
"JIRA_API_KEY": "your-api-token"
}
}
}
}
  1. Restart Claude Desktop to load the new configuration.

Available Tools

1. JQL Search (jql_search)

Executes a JQL search query with customizable parameters.

Parameters:

  • `jq
Read from source at commit cc235fdf9e07OBSERVED · 2026-10-08
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.

claude-code
claude mcp add jira-mcp --env JIRA_API_KEY=${JIRA_API_KEY} -- npx -y [email protected]
claude-desktop
{
  "mcpServers": {
    "jira-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "JIRA_API_KEY": "${JIRA_API_KEY}"
      }
    }
  }
}
03

Exposed tools (2)

2 read · 0 write · 0 destructive.

ToolRiskDescription
get_issuereadRetrieve details about an issue by its ID or key.
jql_searchreadPerform enhanced JQL search in Jira
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
declared (2 observation(s))
Shell
none-observed
Dependencies
not all pinned
Secrets in source
none-found

Findings (1)

LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
@modelcontextprotocol/sdk
Why it matters. 1 dependency range(s) float
Fix. pin exact versions or ship a lockfile

Gates applied: no_behavioural_pass.

Audited 2026-10-08 · audit v0.4.1 · source sha cc235fdf9e07full audit observations/trust-audit/mcp-server/camdenclark__jira-1.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-08cc235fdf9e07SAFEB89first audit
06

Questions

What tools does Jira expose?

2 in total: 2 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is Jira safe to connect to an agent?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.

What credentials does Jira need?

It reads JIRA_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.

How does Jira run?

It speaks stdio, so it runs as a local process your client starts. It is published on npm as jira-mcp at 1.0.1.

How current is this page?

The grade is for one exact copy of the source (cc235fdf9e07), read on 2026-10-08. The repository is watched and re-audited when it changes.

Advertisement