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 Coding Agents

Use the Jira CLI for coding agents with headless JSON commands, schema discovery, credentials, and permission controls.

20 functions 12 read 8 write API token auth

Submit Jira feedback View package source

Jira CLI for Coding Agents

Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

Use this pattern when another coding agent needs exact commands and schema discovery. The Jira CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Jira CLI for Coding Agents
kosmokrator integrations:configure jira --set api_token="$JIRA_API_TOKEN" --set base_url="$JIRA_BASE_URL" --enable --read allow --write ask --json
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

Discovery Before Execution

Agents and scripts can inspect Jira docs and schemas 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

Useful Jira CLI Functions

Function	Type	Parameters	Description
`jira.jira_create_issue`	Write	project_key, summary, description, issue_type, priority, assignee, labels	Create a new issue in a Jira project. Requires project_key, summary, and issue_type. Optionally set description, priority, assignee, and labels.
`jira.jira_get_issue`	Read	key	Get details for a specific Jira issue by its key (e.g. PROJ-123). Returns summary, status, assignee, description, and all fields.
`jira.jira_update_issue`	Write	key, summary, description, priority, assignee	Update an existing Jira issue. Provide the issue key and any fields to update (summary, description, priority, assignee).
`jira.jira_search_issues`	Read	jql, start_at, max_results, fields	Search for Jira issues using JQL (Jira Query Language). Examples: "project = PROJ AND status = Open", "assignee = currentUser() ORDER BY created DESC".
`jira.jira_add_comment`	Write	issue_key, body	Add a comment to a Jira issue. Provide the issue key and the comment body text.
`jira.jira_list_comments`	Read	issue_key	List all comments on a Jira issue. Returns comment body, author, and creation date.
`jira.jira_get_transitions`	Read	issue_key	Get the available status transitions for a Jira issue. Returns transition IDs and target status names needed to change the issue status.
`jira.jira_transition_issue`	Write	issue_key, transition_id	Transition a Jira issue to a new status. Use jira_get_transitions first to find the available transition IDs for the issue.
`jira.jira_assign_issue`	Write	issue_key, account_id	Assign a Jira issue to a user by their Atlassian account ID. Use jira_search_users to find account IDs.
`jira.jira_delete_issue`	Write	key	Delete a Jira issue by its key. This action is irreversible.
`jira.jira_list_projects`	Read	start_at, max_results	List Jira projects accessible to the authenticated user. Supports pagination with start_at and max_results.
`jira.jira_get_issue_types`	Read	none	Get all available issue types in Jira. Returns issue type names and IDs needed when creating issues.
`jira.jira_get_user`	Read	account_id	Get details for a specific Jira user by their Atlassian account ID.
`jira.jira_search_users`	Read	query, max_results	Search for Jira users by name or email. Returns account IDs needed for assigning issues.
`jira.jira_list_priorities`	Read	none	List all available issue priorities in Jira. Returns priority names and IDs needed when creating or updating issues.
`jira.jira_list_boards`	Read	start_at, max_results	List agile boards accessible to the authenticated user. Supports pagination with start_at and max_results.
`jira.jira_list_sprints`	Read	board_id, state	List sprints for a specific Jira board. Optionally filter by sprint state (active, closed, future).
`jira.jira_list_sprint_issues`	Read	sprint_id, start_at, max_results	List issues in a specific Jira sprint. Supports pagination with start_at and max_results.
`jira.jira_create_version`	Write	project_key, name, description, start_date, release_date	Create a new version (release) in a Jira project. Requires project_key and name. Optionally set description, start_date, and release_date.
`jira.jira_add_attachment`	Write	issue_key, filename, content	Add a file attachment to a Jira issue. Provide the issue key, filename, and file content.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Jira CLI Pages

CI Jira CLI for CI. Cron Jobs Jira CLI for cron jobs. Shell Scripts Jira CLI for shell scripts. Headless Automation Jira CLI for headless automation.