Atlassian Jira MCP (aashari)

70/100

Capped at 70: no passing tool call yet; the tests add up to 80. Why scores are capped

Last tested 2026-11-13 UTC (Fresh: tested within 30 days) Connects · tools listedNo tool call tested yet Connects without a key; tool calls need one

Advisories: not yet checked

Security review: not tested

Test points add up to 80; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology

Test points before the cap (80/100)

  • Install20/20
  • Handshake30/30
  • Maintenance5/25
  • Docs15/15
  • License10/10

Tested npm @aashari/mcp-server-atlassian-jira 3.3.0 (ISC; repo aashari/mcp-server-atlassian-jira). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 5 tools (no tool annotations). Real calls: 0 of 1 real function calls passed. Calls need Atlassian credentials (ATLASSIAN_* env). Core tools not tested: 70 cap.
Tool-call test (2026-11-13 UTC, direct MCP stdio client, no LLM): fail. 0 of 1 real function calls passed. Calls need Atlassian credentials (ATLASSIAN_* env). Evidence: local test run, Nov 13, 2026 UTC.

Transport (tested 2026-11-13 UTC): stdio

Token cost (estimate): approx. 3378 tokens, cl100k estimate (5 tools, measured 2026-11-13 UTC, version 3.3.0). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 1 read, 4 write (state-changing), 0 unclassified · Auth: API key · Rate limit: unknown · Pricing unit: unknown

Auth: API key. Rate limit: unknown. Pricing unit: unknown.

  • jira_delete — write (state-changing)
  • jira_get — read
  • jira_patch — write (state-changing)
  • jira_post — write (state-changing)
  • jira_put — write (state-changing)

listing-flags calls_need_key or auth_kind

Score 70/100 · Tools 5 · Token cost approx. 3,378 tokens · Compare · Last tested 2026-11-13 UTC · Version tested 3.3.0 · Package @aashari/mcp-server-atlassian-jira · Repo aashari/mcp-server-atlassian-jira

Summary: Atlassian Jira MCP (aashari) completed an MCP handshake without credentials and exposed 5 tools.

Evidence summary

Handshake
pass
Tools listed
5
Context cost
approx. 3378 tokens, cl100k estimate (5 tools, measured 2026-11-13 UTC, version 3.3.0; an estimate) ranking · add up your servers' context cost
API key
Connects without a key; tool calls need one
Tested
2026-11-13 UTC

Test results

TestResultPointsEvidence
installpass20npm install @aashari/mcp-server-atlassian-jira (Node 20, Linux) succeeded in 1s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 5 tools listed in 12.9s.
maintenancepartial5Repo pushed 251 days before test.
docspass15README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package).
licensepass10ISC (OSI-approved).

Local-model readiness

Token cost (estimate): approx. 3378 tokens, cl100k estimate for 5 tools · about 41% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

Not tested

Small-model task runs: Not yet tested.

What we tested and what we didn't

Tested on 2026-11-13 UTC

  • Install from the registry
  • We connected with no credentials and asked for its tool list: it listed 5 tools (Method details: MCP initialize then tools/list)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Not yet checked.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Baseline recorded from the 2026-11-13 UTC test run; changes appear after the next test.

Snapshot hash (fingerprint of the tool list)

52e037ce62b0: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "@aashari/mcp-server-atlassian-jira",
  "version": "3.3.0",
  "registry": "npm",
  "status": "working",
  "tested": "2026-11-13",
  "tools_count": 5,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`npm install @aashari/mcp-server-atlassian-jira` (Node 20, Linux) succeeded in 1s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 5 tools listed in 12.9s."
    ],
    "maintenance": [
      "partial",
      5,
      "Repo pushed 251 days before test."
    ],
    "docs": [
      "pass",
      15,
      "README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
    ],
    "license": [
      "pass",
      10,
      "ISC (OSI-approved)."
    ]
  }
}

Install

npx -y @aashari/mcp-server-atlassian-jira

Pin the version we tested

npx -y @aashari/mcp-server-atlassian-jira@3.3.0

tested 2026-11-13 UTC. Newer versions may differ and were not tested by us.

{
  "mcpServers": {
    "atlassian-jira-mcp-aashari": {
      "command": "npx",
      "args": [
        "-y",
        "@aashari/mcp-server-atlassian-jira@3.3.0"
      ]
    }
  }
}

Tools listed

jira_get, jira_post, jira_put, jira_patch, jira_delete

Quick config

{
  "mcpServers": {
    "atlassian-jira-mcp-aashari": {
      "command": "npx",
      "args": [
        "-y",
        "@aashari/mcp-server-atlassian-jira"
      ]
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

  1. Install. Run npm install @aashari/mcp-server-atlassian-jira (Node 20). This is the exact command we ran on 2026-11-13 UTC.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (5 in our test).
{
  "mcpServers": {
    "atlassian-jira-mcp-aashari": {
      "command": "npx",
      "args": [
        "-y",
        "@aashari/mcp-server-atlassian-jira"
      ]
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

Related: Best productivity MCP servers

FAQ

Is Atlassian Jira MCP (aashari) deprecated?

No. @aashari/mcp-server-atlassian-jira was not deprecated or archived when we last tested it on 2026-11-13 UTC.

What replaces Atlassian Jira MCP (aashari)?

Nothing; Atlassian Jira MCP (aashari) is not deprecated as of 2026-11-13 UTC.

Does Atlassian Jira MCP (aashari) need an API key?

It connects and lists 5 tools without a key, but its tool calls need one.

Embed the badge

TestedMCP: 70/100, tested 2026-11-13 UTC

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue