Can I use Jira as a CLI?

Yes. KosmoKrator exposes a Jira CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Jira through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Jira tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Jira credentials stored?

Jira credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Jira MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Jira CLI for AI Agents

Use the Jira CLI from KosmoKrator to call Jira tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

20 functions 12 read 8 write API token auth

Submit Jira feedback View package source

Jira CLI Setup

Jira can be configured headlessly with `kosmokrator integrations:configure jira`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure jira --set api_token="$JIRA_API_TOKEN" --set base_url="$JIRA_BASE_URL" --enable --read allow --write ask --json
kosmokrator integrations:doctor jira --json
kosmokrator integrations:status --json

Credentials

Authentication type: API token api_token. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

Key	Env var	Type	Required	Label
`api_token`	`JIRA_API_TOKEN`	Secret `secret`	yes	Personal Access Token
`base_url`	`JIRA_BASE_URL`	Text `text`	yes	Jira Domain URL

Call Jira Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call jira.jira_create_issue '{
  "project_key": "example_project_key",
  "summary": "example_summary",
  "description": "example_description",
  "issue_type": "example_issue_type",
  "priority": "example_priority",
  "assignee": "example_assignee",
  "labels": "example_labels"
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:jira jira_create_issue '{
  "project_key": "example_project_key",
  "summary": "example_summary",
  "description": "example_description",
  "issue_type": "example_issue_type",
  "priority": "example_priority",
  "assignee": "example_assignee",
  "labels": "example_labels"
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs jira --json
kosmo integrations:docs jira.jira_create_issue --json
kosmo integrations:schema jira.jira_create_issue --json
kosmo integrations:search "Jira" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Jira.

`jira.jira_create_issue`

Write write

Create a new issue in a Jira project. Requires project_key, summary, and issue_type. Optionally set description, priority, assignee, and labels.

Parameters: project_key, summary, description, issue_type, priority, assignee, labels

Generic CLI call

kosmo integrations:call jira.jira_create_issue '{"project_key":"example_project_key","summary":"example_summary","description":"example_description","issue_type":"example_issue_type","priority":"example_priority","assignee":"example_assignee","labels":"example_labels"}' --json

Provider shortcut

kosmo integrations:jira jira_create_issue '{"project_key":"example_project_key","summary":"example_summary","description":"example_description","issue_type":"example_issue_type","priority":"example_priority","assignee":"example_assignee","labels":"example_labels"}' --json

`jira.jira_get_issue`

Read read

Get details for a specific Jira issue by its key (e.g. PROJ-123). Returns summary, status, assignee, description, and all fields.

Parameters: key

Generic CLI call

kosmo integrations:call jira.jira_get_issue '{"key":"example_key"}' --json

Provider shortcut

kosmo integrations:jira jira_get_issue '{"key":"example_key"}' --json

`jira.jira_update_issue`

Write write

Update an existing Jira issue. Provide the issue key and any fields to update (summary, description, priority, assignee).

Parameters: key, summary, description, priority, assignee

Generic CLI call

kosmo integrations:call jira.jira_update_issue '{"key":"example_key","summary":"example_summary","description":"example_description","priority":"example_priority","assignee":"example_assignee"}' --json

Provider shortcut

kosmo integrations:jira jira_update_issue '{"key":"example_key","summary":"example_summary","description":"example_description","priority":"example_priority","assignee":"example_assignee"}' --json

`jira.jira_search_issues`

Read read

Search for Jira issues using JQL (Jira Query Language). Examples: "project = PROJ AND status = Open", "assignee = currentUser() ORDER BY created DESC".

Parameters: jql, start_at, max_results, fields

Generic CLI call

kosmo integrations:call jira.jira_search_issues '{"jql":"example_jql","start_at":1,"max_results":1,"fields":"example_fields"}' --json

Provider shortcut

kosmo integrations:jira jira_search_issues '{"jql":"example_jql","start_at":1,"max_results":1,"fields":"example_fields"}' --json

`jira.jira_add_comment`

Write write

Add a comment to a Jira issue. Provide the issue key and the comment body text.

Parameters: issue_key, body

Generic CLI call

kosmo integrations:call jira.jira_add_comment '{"issue_key":"example_issue_key","body":"example_body"}' --json

Provider shortcut

kosmo integrations:jira jira_add_comment '{"issue_key":"example_issue_key","body":"example_body"}' --json

`jira.jira_list_comments`

Read read

List all comments on a Jira issue. Returns comment body, author, and creation date.

Parameters: issue_key

Generic CLI call

kosmo integrations:call jira.jira_list_comments '{"issue_key":"example_issue_key"}' --json

Provider shortcut

kosmo integrations:jira jira_list_comments '{"issue_key":"example_issue_key"}' --json

`jira.jira_get_transitions`

Read read

Get the available status transitions for a Jira issue. Returns transition IDs and target status names needed to change the issue status.

Parameters: issue_key

Generic CLI call

kosmo integrations:call jira.jira_get_transitions '{"issue_key":"example_issue_key"}' --json

Provider shortcut

kosmo integrations:jira jira_get_transitions '{"issue_key":"example_issue_key"}' --json

`jira.jira_transition_issue`

Write write

Transition a Jira issue to a new status. Use jira_get_transitions first to find the available transition IDs for the issue.

Parameters: issue_key, transition_id

Generic CLI call

kosmo integrations:call jira.jira_transition_issue '{"issue_key":"example_issue_key","transition_id":"example_transition_id"}' --json

Provider shortcut

kosmo integrations:jira jira_transition_issue '{"issue_key":"example_issue_key","transition_id":"example_transition_id"}' --json

`jira.jira_assign_issue`

Write write

Assign a Jira issue to a user by their Atlassian account ID. Use jira_search_users to find account IDs.

Parameters: issue_key, account_id

Generic CLI call

kosmo integrations:call jira.jira_assign_issue '{"issue_key":"example_issue_key","account_id":"example_account_id"}' --json

Provider shortcut

kosmo integrations:jira jira_assign_issue '{"issue_key":"example_issue_key","account_id":"example_account_id"}' --json

`jira.jira_delete_issue`

Write write

Delete a Jira issue by its key. This action is irreversible.

Parameters: key

Generic CLI call

kosmo integrations:call jira.jira_delete_issue '{"key":"example_key"}' --json

Provider shortcut

kosmo integrations:jira jira_delete_issue '{"key":"example_key"}' --json

`jira.jira_list_projects`

Read read

List Jira projects accessible to the authenticated user. Supports pagination with start_at and max_results.

Parameters: start_at, max_results

Generic CLI call

kosmo integrations:call jira.jira_list_projects '{"start_at":1,"max_results":1}' --json

Provider shortcut

kosmo integrations:jira jira_list_projects '{"start_at":1,"max_results":1}' --json

`jira.jira_get_issue_types`

Read read

Get all available issue types in Jira. Returns issue type names and IDs needed when creating issues.

Parameters: none

Generic CLI call

kosmo integrations:call jira.jira_get_issue_types '{}' --json

Provider shortcut

kosmo integrations:jira jira_get_issue_types '{}' --json

`jira.jira_get_user`

Read read

Get details for a specific Jira user by their Atlassian account ID.

Parameters: account_id

Generic CLI call

kosmo integrations:call jira.jira_get_user '{"account_id":"example_account_id"}' --json

Provider shortcut

kosmo integrations:jira jira_get_user '{"account_id":"example_account_id"}' --json

`jira.jira_search_users`

Read read

Search for Jira users by name or email. Returns account IDs needed for assigning issues.

Parameters: query, max_results

Generic CLI call

kosmo integrations:call jira.jira_search_users '{"query":"example_query","max_results":1}' --json

Provider shortcut

kosmo integrations:jira jira_search_users '{"query":"example_query","max_results":1}' --json

`jira.jira_list_priorities`

Read read

List all available issue priorities in Jira. Returns priority names and IDs needed when creating or updating issues.

Parameters: none

Generic CLI call

kosmo integrations:call jira.jira_list_priorities '{}' --json

Provider shortcut

kosmo integrations:jira jira_list_priorities '{}' --json

`jira.jira_list_boards`

Read read

List agile boards accessible to the authenticated user. Supports pagination with start_at and max_results.

Parameters: start_at, max_results

Generic CLI call

kosmo integrations:call jira.jira_list_boards '{"start_at":1,"max_results":1}' --json

Provider shortcut

kosmo integrations:jira jira_list_boards '{"start_at":1,"max_results":1}' --json

`jira.jira_list_sprints`

Read read

List sprints for a specific Jira board. Optionally filter by sprint state (active, closed, future).

Parameters: board_id, state

Generic CLI call

kosmo integrations:call jira.jira_list_sprints '{"board_id":1,"state":"example_state"}' --json

Provider shortcut

kosmo integrations:jira jira_list_sprints '{"board_id":1,"state":"example_state"}' --json

`jira.jira_list_sprint_issues`

Read read

List issues in a specific Jira sprint. Supports pagination with start_at and max_results.

Parameters: sprint_id, start_at, max_results

Generic CLI call

kosmo integrations:call jira.jira_list_sprint_issues '{"sprint_id":1,"start_at":1,"max_results":1}' --json

Provider shortcut

kosmo integrations:jira jira_list_sprint_issues '{"sprint_id":1,"start_at":1,"max_results":1}' --json

`jira.jira_create_version`

Write write

Create a new version (release) in a Jira project. Requires project_key and name. Optionally set description, start_date, and release_date.

Parameters: project_key, name, description, start_date, release_date

Generic CLI call

kosmo integrations:call jira.jira_create_version '{"project_key":"example_project_key","name":"example_name","description":"example_description","start_date":"example_start_date","release_date":"example_release_date"}' --json

Provider shortcut

kosmo integrations:jira jira_create_version '{"project_key":"example_project_key","name":"example_name","description":"example_description","start_date":"example_start_date","release_date":"example_release_date"}' --json

`jira.jira_add_attachment`

Write write

Add a file attachment to a Jira issue. Provide the issue key, filename, and file content.

Parameters: issue_key, filename, content

Generic CLI call

kosmo integrations:call jira.jira_add_attachment '{"issue_key":"example_issue_key","filename":"example_filename","content":"example_content"}' --json

Provider shortcut

kosmo integrations:jira jira_add_attachment '{"issue_key":"example_issue_key","filename":"example_filename","content":"example_content"}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

`jira.jira_create_issue`

Create a new issue in a Jira project. Requires project_key, summary, and issue_type. Optionally set description, priority, assignee, and labels.

Operation: Write write
Schema command: kosmo integrations:schema jira.jira_create_issue --json

Parameter	Type	Required	Description
`project_key`	string	yes	The project key (e.g. PROJ).
`summary`	string	yes	The summary (title) of the issue.
`description`	string	no	The description of the issue. Supports Jira wiki markup or plain text.
`issue_type`	string	no	The issue type name (e.g. Task, Bug, Story, Epic). Default: Task.
`priority`	string	no	The priority name (e.g. High, Medium, Low).
`assignee`	string	no	The account ID of the user to assign.
`labels`	array	no	Array of label strings to apply. Example: ["backend", "urgent"].

`jira.jira_get_issue`

Get details for a specific Jira issue by its key (e.g. PROJ-123). Returns summary, status, assignee, description, and all fields.

Operation: Read read
Schema command: kosmo integrations:schema jira.jira_get_issue --json

Parameter	Type	Required	Description
`key`	string	yes	The issue key (e.g. PROJ-123).

`jira.jira_update_issue`

Update an existing Jira issue. Provide the issue key and any fields to update (summary, description, priority, assignee).

Operation: Write write
Schema command: kosmo integrations:schema jira.jira_update_issue --json

Parameter	Type	Required	Description
`key`	string	yes	The issue key (e.g. PROJ-123).
`summary`	string	no	The new summary (title) of the issue.
`description`	string	no	The new description of the issue.
`priority`	string	no	The new priority name (e.g. High, Medium, Low).
`assignee`	string	no	The account ID of the new assignee.

`jira.jira_search_issues`

Search for Jira issues using JQL (Jira Query Language). Examples: "project = PROJ AND status = Open", "assignee = currentUser() ORDER BY created DESC".

Operation: Read read
Schema command: kosmo integrations:schema jira.jira_search_issues --json

Parameter	Type	Required	Description
`jql`	string	yes	JQL query string. Example: "project = PROJ AND status = Open".
`start_at`	integer	no	Offset for pagination (0-based). Default: 0.
`max_results`	integer	no	Maximum number of results per page (1-100). Default: 50.
`fields`	string	no	Comma-separated list of field names to return. Example: "summary,status,assignee".

`jira.jira_add_comment`

Add a comment to a Jira issue. Provide the issue key and the comment body text.

Operation: Write write
Schema command: kosmo integrations:schema jira.jira_add_comment --json

Parameter	Type	Required	Description
`issue_key`	string	yes	The issue key (e.g. PROJ-123).
`body`	string	yes	The comment text.

`jira.jira_list_comments`

List all comments on a Jira issue. Returns comment body, author, and creation date.

Operation: Read read
Schema command: kosmo integrations:schema jira.jira_list_comments --json

Parameter	Type	Required	Description
`issue_key`	string	yes	The issue key (e.g. PROJ-123).

`jira.jira_get_transitions`

Get the available status transitions for a Jira issue. Returns transition IDs and target status names needed to change the issue status.

Operation: Read read
Schema command: kosmo integrations:schema jira.jira_get_transitions --json

Parameter	Type	Required	Description
`issue_key`	string	yes	The issue key (e.g. PROJ-123).

`jira.jira_transition_issue`

Transition a Jira issue to a new status. Use jira_get_transitions first to find the available transition IDs for the issue.

Operation: Write write
Schema command: kosmo integrations:schema jira.jira_transition_issue --json

Parameter	Type	Required	Description
`issue_key`	string	yes	The issue key (e.g. PROJ-123).
`transition_id`	string	yes	The transition ID to execute. Use jira_get_transitions to find valid IDs.

`jira.jira_assign_issue`

Assign a Jira issue to a user by their Atlassian account ID. Use jira_search_users to find account IDs.

Operation: Write write
Schema command: kosmo integrations:schema jira.jira_assign_issue --json

Parameter	Type	Required	Description
`issue_key`	string	yes	The issue key (e.g. PROJ-123).
`account_id`	string	yes	The Atlassian account ID of the user to assign.

`jira.jira_delete_issue`

Delete a Jira issue by its key. This action is irreversible.

Operation: Write write
Schema command: kosmo integrations:schema jira.jira_delete_issue --json

Parameter	Type	Required	Description
`key`	string	yes	The issue key to delete (e.g. PROJ-123).

`jira.jira_list_projects`

List Jira projects accessible to the authenticated user. Supports pagination with start_at and max_results.

Operation: Read read
Schema command: kosmo integrations:schema jira.jira_list_projects --json

Parameter	Type	Required	Description
`start_at`	integer	no	Offset for pagination (0-based). Default: 0.
`max_results`	integer	no	Maximum number of results per page (1-100). Default: 50.

`jira.jira_get_issue_types`

Get all available issue types in Jira. Returns issue type names and IDs needed when creating issues.

Operation: Read read
Schema command: kosmo integrations:schema jira.jira_get_issue_types --json

Parameter	Type	Required	Description
No parameters.

`jira.jira_get_user`

Get details for a specific Jira user by their Atlassian account ID.

Operation: Read read
Schema command: kosmo integrations:schema jira.jira_get_user --json

Parameter	Type	Required	Description
`account_id`	string	yes	The Atlassian account ID of the user.

`jira.jira_search_users`

Search for Jira users by name or email. Returns account IDs needed for assigning issues.

Operation: Read read
Schema command: kosmo integrations:schema jira.jira_search_users --json

Parameter	Type	Required	Description
`query`	string	yes	Search query (name or email substring).
`max_results`	integer	no	Maximum number of results to return. Default: 10.

`jira.jira_list_priorities`

List all available issue priorities in Jira. Returns priority names and IDs needed when creating or updating issues.

Operation: Read read
Schema command: kosmo integrations:schema jira.jira_list_priorities --json

Parameter	Type	Required	Description
No parameters.

`jira.jira_list_boards`

List agile boards accessible to the authenticated user. Supports pagination with start_at and max_results.

Operation: Read read
Schema command: kosmo integrations:schema jira.jira_list_boards --json

Parameter	Type	Required	Description
`start_at`	integer	no	Offset for pagination (0-based). Default: 0.
`max_results`	integer	no	Maximum number of results per page (1-100). Default: 50.

`jira.jira_list_sprints`

List sprints for a specific Jira board. Optionally filter by sprint state (active, closed, future).

Operation: Read read
Schema command: kosmo integrations:schema jira.jira_list_sprints --json

Parameter	Type	Required	Description
`board_id`	integer	yes	The board ID. Use jira_list_boards to find board IDs.
`state`	string	no	Filter by sprint state: active, closed, or future.

`jira.jira_list_sprint_issues`

List issues in a specific Jira sprint. Supports pagination with start_at and max_results.

Operation: Read read
Schema command: kosmo integrations:schema jira.jira_list_sprint_issues --json

Parameter	Type	Required	Description
`sprint_id`	integer	yes	The sprint ID. Use jira_list_sprints to find sprint IDs.
`start_at`	integer	no	Offset for pagination (0-based). Default: 0.
`max_results`	integer	no	Maximum number of results per page (1-100). Default: 50.

`jira.jira_create_version`

Create a new version (release) in a Jira project. Requires project_key and name. Optionally set description, start_date, and release_date.

Operation: Write write
Schema command: kosmo integrations:schema jira.jira_create_version --json

Parameter	Type	Required	Description
`project_key`	string	yes	The project key (e.g. PROJ).
`name`	string	yes	The version name (e.g. "v1.0.0").
`description`	string	no	A description of the version.
`start_date`	string	no	The start date in ISO 8601 format (e.g. "2024-01-15").
`release_date`	string	no	The release date in ISO 8601 format (e.g. "2024-03-01").

`jira.jira_add_attachment`

Add a file attachment to a Jira issue. Provide the issue key, filename, and file content.

Operation: Write write
Schema command: kosmo integrations:schema jira.jira_add_attachment --json

Parameter	Type	Required	Description
`issue_key`	string	yes	The issue key (e.g. PROJ-123).
`filename`	string	yes	The name of the file to attach (e.g. "report.pdf").
`content`	string	yes	The file content (raw string or base64-encoded).

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.