MCPoppinsLive chat ↗
← Marketplace
JI
@mcp-platform/jira

Jira MCP Connector

Search issues, view sprints, manage work items with 17 tools and approval controls.

Read-only by defaultInstall options
Read tools · 11

Useful from the first safe connection.

health_check

Validate connection

R0 Read
get_issue

Issue details with links and comments

R0 Read
search_issues

JQL search

R0 Read
my_issues

Your open issues

R0 Read
get_board_issues

Board issues

R0 Read
get_sprint_issues

Agile sprint view

R0 Read
get_attachments

Attachments

R0 Read
get_worklogs

Work logs

R0 Read
get_comments

Comments

R0 Read
get_links

Linked issues

R0 Read
whoami

Current user

R0 Read
Write tools · 6

Visible, but never silently enabled.

create_issue

Create issue

Requires approval
update_issue

Update fields

Requires approval
transition_issue

Change status

Requires approval
add_comment

Add comment

Requires approval
assign_issue

Assign user

Requires approval
log_work

Log time

Requires approval
npm · ZIP · Docker

Choose an install method.

npm install @mcp-platform/jira

Use placeholder credentials only in copied examples. Secrets belong in environment variables.

Quick start from package README

Validate before the first tool call.

Terminal
npm install
cp .env.example .env   # Edit with your URL and token
npm run doctor         # Verify connection
npm start              # Run the MCP server
IDE config

Copy placeholders, then supply your own values.

mcp.local.example.json
{
  "mcpServers": {
    "jira": {
      "command": "node",
      "args": ["PATH/TO/mcp-platform/packages/mcp-jira/src/index.js"],
      "env": {
        "JIRA_BASE_URL": "https://your-domain.atlassian.net",
        "JIRA_PAT": "YOUR_TOKEN_HERE",
        "JIRA_EMAIL": "you@example.com",
        "JIRA_PROJECT_KEY": "",
        "JIRA_ENABLE_WRITES": "false",
        "JIRA_ALLOWED_PROJECTS": "",
        "JIRA_REQUEST_TIMEOUT": "30000",
        "JIRA_MAX_RESULTS": "25"
      },
      "disabled": false
    }
  }
}
Example prompts

Start with a known outcome.

01

“Show my open issues”

02

“High-priority bugs in PROJ”

03

“Status of PROJ-456”

04

“Current sprint”

05

“Attachments on PROJ-123”

Security

Controls from the package source.

✓ Read-only default✓ Project allowlist✓ No TLS bypass✓ Correlation IDs✓ Timeouts

Security Policy — @mcp-platform/jira

Security Model

This connector follows a read-only by default security posture. Write operations (create, update, transition, comment, assign, log work) are only available when explicitly enabled via JIRA_ENABLE_WRITES=true.

Authentication

  • Jira Cloud: API token with email-based Basic Auth
  • Jira Data Center/Server: Personal Access Token with Bearer auth
  • Tokens are read from environment variables — never embedded in code or config files
  • Each user must generate and manage their own credentials

Access Controls

  • Project allowlist: Set JIRA_ALLOWED_PROJECTS to restrict which projects the connector can access
  • Read-only default: Write tools are not registered unless explicitly enabled
  • Per-user identity: Each installation uses individual credentials, not shared tokens

TLS / Certificate Handling

This package does NOT disable TLS certificate verification. For environments with corporate or self-signed certificates:

  • Set NODE_EXTRA_CA_CERTS=/path/to/ca-bundle.pem in your environment
  • Or set JIRA_CA_CERT_PATH to point to your certificate file

Never set NODE_TLS_REJECT_UNAUTHORIZED=0 in production.

Vulnerability Reporting

If you discover a security vulnerability, please report it responsibly:

  1. Do NOT create a public issue
  2. Contact the maintainers directly
  3. Allow reasonable time for a fix before disclosure

Supported Versions

VersionSupported
1.0.xYes