io.github.edrich13/mcp-jira-server

MCPcommunity
v1.0.1io.github.edrich13UnknownUpdated 11mo agonpm

MCP server for self-hosted Jira instance with Personal Access Token authentication

A Model Context Protocol (MCP) server for interacting with self-hosted Jira instances using Personal Access Token (PAT) authentication. ✅ Personal Access Token authentication for self-hosted Jira ✅ Create, read, update, and delete Jira issues ✅ Search issues using JQL (Jira Query Language) ✅ Add and view comments ✅ Manage issue assignments ✅ List projects and issue types ✅ Transition issues…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
11mo agoLast update
Package
Authorio.github.edrich13
LicenseUnknown
Version1.0.1
Sourcemcp-registry
npmmcp-jira-server
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface12 tools · 1 privileged
Security scan✓ Cleanv1.0.3 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

12 tools · 1 privileged
Statically extracted from the published packagev1.0.3 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

jira_get_issueNo description published

This tool published no description. Forge does not invent one.

jira_search_issuesNo description published

This tool published no description. Forge does not invent one.

jira_create_issueNo description published

This tool published no description. Forge does not invent one.

jira_update_issueNo description published

This tool published no description. Forge does not invent one.

jira_add_commentNo description published

This tool published no description. Forge does not invent one.

jira_get_commentsNo description published

This tool published no description. Forge does not invent one.

jira_get_projectsNo description published

This tool published no description. Forge does not invent one.

jira_get_projectNo description published

This tool published no description. Forge does not invent one.

jira_get_issue_typesNo description published

This tool published no description. Forge does not invent one.

jira_assign_issueNo description published

This tool published no description. Forge does not invent one.

jira_delete_issueprivilegedNo description published

This tool published no description. Forge does not invent one.

jira_get_current_userNo description published

This tool published no description. Forge does not invent one.

0 of 12 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

A Model Context Protocol (MCP) server for interacting with self-hosted Jira instances using Personal Access Token (PAT) authentication. ✅ Personal Access Token authentication for self-hosted Jira ✅ Create, read, update, and delete Jira issues ✅ Search issues using JQL (Jira Query Language) ✅ Add and view comments ✅ Manage issue assignments ✅ List projects and issue types ✅ Transition issues between statuses ✅ Get current user information A self-hosted Jira instance (e.g., A Jira Personal Access…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

12 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in project management