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 MCP Integration for CrewAI

Connect Jira to CrewAI through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

20 functions 12 read 8 write API token auth

Submit Jira feedback View package source

Connect Jira to CrewAI

Expose KosmoKrator integrations to CrewAI workers as scoped local tools.

Wrap kosmo integrations:call for specific tasks or connect workers to a local MCP gateway. The gateway is local, scoped to this integration, and starts with --write=deny so CrewAI can inspect read-capable tools without receiving write access by default.

Jira MCP Config for CrewAI

Use per-worker integration scopes to avoid giving every worker every tool.

{
  "mcpServers": {
    "kosmokrator-jira": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=jira",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=jira --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Jira instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Jira Tools Visible to CrewAI

CrewAI sees stable MCP tool names generated from the Jira integration catalog.

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

Related Jira Pages

Jira CLIUse direct JSON commands instead of MCP discovery. Jira MCPFull gateway reference and MCP tool names. KosmoKrator for CrewAIClient-level gateway setup.