Jira AI CLI

An AI-friendly CLI for Jira that prioritizes efficiency and security.

Core Benefits

1. Context Efficiency: Eliminates redundant context data, consuming significantly fewer tokens than Jira MCP or similar tools.
2. Bullet-proof Security: Restrict AI to only the actions you permit, ensuring your environment remains secure.

Start

- Human: Quick walk through video
- AI Agent: Project overview and commands

Installation

If you know how to install npm then after installation run this instuction. in your CLI agent.

If you don't know what npm is but want to use Jira "the haker way" this instruction is for you. copy it and run in any AI agent like chat GPT, Gemini e.t.c.

``bash
npm install -g jira-ai
`

$3


#### Step 1: Add the Marketplace
Add this marketplace to your Claude instance:
`bash
claude plugin marketplace add festoinc/management-plugins
`

#### Step 2: Install the Plugin
`bash
claude plugin install jira-ai-connector@management-plugins
`

Will be avalibale automatically as skill




$3


#### Step 1: Add the Extension
Add this extension to your Gemini CLI:
`bash
gemini extension install https://github.com/festoinc/management-plugins
`

Will be avalible as slash command
`bash
/work-with-jira
`

Quick Start

Run interactive authorization:
`bash
jira-ai auth
`

See all available commands:
`bash
jira-ai --help
`

Service Account Authentication

Atlassian service accounts use scoped API tokens that must authenticate through the api.atlassian.com gateway rather than direct site URLs.

$3

Create a .env file with your service account credentials:

`env
JIRA_HOST=your-domain.atlassian.net
JIRA_USER_EMAIL=your-bot@serviceaccount.atlassian.com
JIRA_API_TOKEN=your-service-account-api-token
JIRA_AUTH_TYPE=service_account
`

Then authenticate:

`bash
jira-ai auth --from-file path/to/.env
`

The Cloud ID will be auto-discovered from your site URL. To provide it explicitly:

`env
JIRA_CLOUD_ID=your-cloud-id
`

$3

`bash
jira-ai auth --service-account
`

Or with an explicit Cloud ID:

`bash
jira-ai auth --service-account --cloud-id your-cloud-id
`

$3

Standard Jira API tokens authenticate directly against your-domain.atlassian.net. Service account tokens are scoped and must route through the Atlassian API gateway at api.atlassian.com/ex/jira/{cloudId}/....

When authType is set to service_account, jira-ai automatically:

1. Discovers your Cloud ID from https://your-domain.atlassian.net/_edge/tenant_info (if not provided)
2. Routes all API requests through https://api.atlassian.com/ex/jira/{cloudId} instead of the direct site URL
3. Uses the same basic auth (email + API token) — just through the gateway

Existing configurations using standard API tokens are unaffected.

Configuration & Restrictions

Tool allows you to have very complex configutations of what Projects/Jira commands/Issue types you would have acess to thought the tool.
Use this command to start setup:

`bash
jira-ai settings --help
``

All avalible commands: https://github.com/festoinc/jira-ai/blob/main/all_avaliable_commands.md

Links

- Repository: https://github.com/festoinc/jira-ai
- Issues: https://github.com/festoinc/jira-ai/issues
- NPM: https://www.npmjs.com/package/jira-ai

License

Apache License 2.0