Install @tocharianou/jira-mcp from npm
Install exact version 1.0.0. No verified executable entrypoint is available, so use the package documentation to launch it.
npm install --save-exact @tocharianou/jira-mcp@1.0.0MCP server intelligence profile
jira-mcp Server
Enables issue search, creation, updates, comments, status transitions, and project listing in Jira, purpose-built for security incident management and SOC workflows
2Distribution channels
9Independently observed tools
0Linked remote endpoints
AvailableVersion intelligence
Detailed security scan evidence is not public for this MCP yet. Public identity, registry metadata, and independently observed protocol inventory remain available.
Install and connect
Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.
Identity
| Canonical slug | jira-mcp-d35e4f68 | Deployment | Local Only |
|---|---|---|---|
| Canonical package | npm:@tocharianou/jira-mcp | Repository | TocharianOU/jira-mcp |
| First published | — | Latest release | — |
| Last security verification | — | Classification confidence | 90% |
| Publication | Draft | Official distribution | Not verified |
Distributions
| Channel | Identifier | Current version | Versions | Source |
|---|---|---|---|---|
| npm | @tocharianou/jira-mcp | 1.0.0 | 1 | Repository |
| source_git | tocharianou/jira-mcp | f31aefc38f79ca44959a92a476f580bb97e99429 | 1 | Repository |
Current release
| Package | Version | Published / observed | Inventory | Security scan |
|---|---|---|---|---|
| npm@tocharianou/jira-mcp | 1.0.0Current | Sep 5, 2026 | 9 toolsSucceeded · 0 resources · 0 prompts | Evidence restricted |
| source_gittocharianou/jira-mcp | f31aefc38f79ca44959a92a476f580bb97e99429Current | Aug 25, 2026 | 9 toolsSucceeded · 0 resources · 0 prompts | Evidence restricted |
Enterprise protection
Continuously monitor this MCP for security risk
Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.
- Independent exact-version security scans
- Continuous release and vulnerability monitoring
- Risk-change alerts with capability context
- Historical evidence and API exports
Custom pricingContact salesTailored to your organization, integrations, data needs, and support requirements.
Current version evidence
No public current-version evidence is available yet.
Current protocol inventory
2025-06-18Negotiated protocol
jira-mcpServer-reported name
1Capability groups
Aug 30, 2026Observed
Tools 9
| Tool | Category | Annotations | Risk |
|---|---|---|---|
add_commentAdd a comment to a Jira issue. Use to record investigation steps, evidence, findings, or remediation actions directly on the ticket. Preserves the full audit trail of the security response.Input schema{
"type": "object",
"properties": {
"issue_key": {
"type": "string",
"description": "Jira issue key to comment on (e.g. SEC-123)."
},
"comment": {
"type": "string",
"description": "Comment text. Markdown-like formatting is supported (bold, lists, code blocks will render in Jira)."
}
},
"required": [
"issue_key",
"comment"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
create_issueCreate a new Jira issue. Use to file security incidents, vulnerabilities, or remediation tasks. Returns the new issue key and URL. Common issue types: Task, Bug, Story, Incident, Security Incident (depends on project configuration).Input schema{
"type": "object",
"properties": {
"project_key": {
"type": "string",
"description": "Jira project key where the issue will be created (e.g. SEC, INFRA, OPS)."
},
"summary": {
"type": "string",
"description": "Issue summary/title (one-line description of the incident or task)."
},
"issue_type": {
"type": "string",
"description": "Issue type name (default: Task). Examples: Task, Bug, Story, Incident. Must match a type available in the project."
},
"description": {
"type": "string",
"description": "Full description of the issue. Plain text; will be formatted for Jira API version automatically."
},
"priority": {
"type": "string",
"description": "Priority name. Examples: Critical, High, Medium, Low."
},
"assignee": {
"type": "string",
"description": "Assignee Jira accountId (use search_issues to find accountIds or check with jira_health_check for your own)."
},
"labels": {
"type": "array",
"items": {
"type": "string"
},
"description": "Labels to attach. Examples: [\"security-incident\", \"ransomware\", \"P1\"]."
},
"components": {
"type": "array",
"items": {
"type": "string"
},
"description": "Component names to associate. Must match existing components in the project."
}
},
"required": [
"project_key",
"summary"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
get_issueGet full details of a single Jira issue by key (e.g. SEC-123). Returns description, all comments, status, priority, assignee, reporter, labels, and timestamps. Use after search_issues to inspect a specific issue in depth.Input schema{
"type": "object",
"properties": {
"issue_key": {
"type": "string",
"description": "Jira issue key (e.g. SEC-123, INFRA-456, PROJ-789)."
},
"fields": {
"type": "array",
"items": {
"type": "string"
},
"description": "Specific fields to fetch. Default includes description and all comments."
},
"max_tokens": {
"type": "number",
"description": "Max output tokens. Default: 20000."
},
"break_token_rule": {
"type": "boolean",
"description": "Bypass token limit check."
}
},
"required": [
"issue_key"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
jira_health_checkTest the Jira connection. Returns authenticated account info (display name, email, account ID) and Jira server version/deployment type. Run first to verify credentials and connectivity.Input schema{
"type": "object",
"properties": {
"max_tokens": {
"type": "number",
"description": "Max output tokens. Default: 20000."
},
"break_token_rule": {
"type": "boolean",
"description": "Bypass token limit check."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
list_projectsList all accessible Jira projects with their keys, names, and types. Use to find the correct project key before creating issues or running JQL queries scoped to a specific project.Input schema{
"type": "object",
"properties": {
"max_results": {
"type": "number",
"description": "Maximum projects to return (default: 50, max: 100)."
},
"max_tokens": {
"type": "number",
"description": "Max output tokens. Default: 20000."
},
"break_token_rule": {
"type": "boolean",
"description": "Bypass token limit check."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
list_transitionsList all available status transitions for a Jira issue. Returns transition IDs and target status names. Use before transition_issue to find the correct transition ID (e.g. "In Progress", "Resolved", "Closed").Input schema{
"type": "object",
"properties": {
"issue_key": {
"type": "string",
"description": "Jira issue key (e.g. SEC-123)."
},
"max_tokens": {
"type": "number",
"description": "Max output tokens. Default: 20000."
},
"break_token_rule": {
"type": "boolean",
"description": "Bypass token limit check."
}
},
"required": [
"issue_key"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
search_issuesSearch Jira issues using JQL (Jira Query Language). Returns key, summary, status, type, priority, assignee, reporter, created/updated dates and labels. Use for finding security incidents, open vulnerabilities, or tracking remediation tasks. Examples: `project = SEC AND status != Done`, `assignee = currentUser() AND priority = High`, `labels = security-incident ORDER BY created DESC`.Input schema{
"type": "object",
"properties": {
"jql": {
"type": "string",
"description": "JQL query string. Examples: \"project=SEC AND status=Open\", \"priority=Critical AND labels=security-incident ORDER BY created DESC\""
},
"max_results": {
"type": "number",
"description": "Maximum issues to return (default: 50, max: 100). Reduce if token limit hit."
},
"fields": {
"type": "array",
"items": {
"type": "string"
},
"description": "Specific fields to return. Default: summary,status,issuetype,priority,assignee,reporter,created,updated,labels. Add \"description\" for full text."
},
"start_at": {
"type": "number",
"description": "Pagination offset (default: 0). Use with max_results to paginate large result sets."
},
"max_tokens": {
"type": "number",
"description": "Max output tokens. Default: 20000."
},
"break_token_rule": {
"type": "boolean",
"description": "Bypass token limit check."
}
},
"required": [
"jql"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
transition_issueMove a Jira issue to a new status using a transition ID. Use list_transitions first to discover available transition IDs. Optionally attach a comment explaining the status change (e.g. "Closed: investigation complete, no compromise confirmed").Input schema{
"type": "object",
"properties": {
"issue_key": {
"type": "string",
"description": "Jira issue key to transition (e.g. SEC-123)."
},
"transition_id": {
"type": "string",
"description": "Transition ID from list_transitions (e.g. \"31\" for \"In Progress\", \"41\" for \"Done\")."
},
"comment": {
"type": "string",
"description": "Optional comment to attach when transitioning (e.g. rationale for closing or escalating)."
}
},
"required": [
"issue_key",
"transition_id"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — | |
update_issueUpdate fields of an existing Jira issue (summary, description, priority, labels). Use to enrich a security incident with investigation findings. To change status, use transition_issue instead.Input schema{
"type": "object",
"properties": {
"issue_key": {
"type": "string",
"description": "Jira issue key to update (e.g. SEC-123)."
},
"summary": {
"type": "string",
"description": "New summary/title."
},
"description": {
"type": "string",
"description": "New description text. Overwrites existing description."
},
"priority": {
"type": "string",
"description": "New priority. Examples: Critical, High, Medium, Low."
},
"labels": {
"type": "array",
"items": {
"type": "string"
},
"description": "New labels array. Replaces existing labels entirely."
}
},
"required": [
"issue_key"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
} | — | — |
Resources 0
- None observed.
Resource templates 0
- None observed.
Prompts 0
- None observed.
Remote endpoints
| Endpoint | Transport | Authentication | Health | Observed |
|---|---|---|---|---|
| No verified remote endpoint is linked. | ||||
jira-mcp Server questions
How do I install jira-mcp Server?
Install the selected package version with: npm install --save-exact @tocharianou/jira-mcp@1.0.0
What tools does jira-mcp Server provide?
jira-mcp Server exposed 9 tools during independent protocol observation, including add_comment, create_issue, get_issue, jira_health_check, list_projects, list_transitions, search_issues, transition_issue, and others.
Is jira-mcp Server secure?
The selected current version does not yet have completed public verification. Unknown does not mean clean or vulnerable.
Company and product intelligence
These internal links are derived from strong identity fields such as the implementation name, package, repository, vendor, and listing name—not generic description prose.
Associated company landscape
Atlassian intelligence →
Association is based on retained identity fields; it does not by itself prove first-party publication.
Explore related MCP server guides
Curated product and capability guides containing this catalog record.