What can you do with the Jira integration?

LiveContext exposes 67 operations on Jira, covering issue, component, sprint and version. Common uses include sprint planning, sprint reports and configuration viewing.

Which OAuth scopes does Jira require?

It depends on the operation: each one declares the scopes Jira requires for it. The most common are read:jira-work (28 operations), write:jira-work (19 operations) and read:jira-user (2 operations).

LiveContext

All integrations

Jira integration

Project tracking and issue management API for agile teams. Search issues with JQL, manage projects, track sprints, handle workflows, add comments, log time, and manage team collaboration. Perfect for building project management tools, issue tracking integrations, sprint planning applications, and agile workflow automation.

67 toolsOAuthAPI docs

Connect Jira How integrations work

Common Jira use cases

sprint planning
sprint reports
configuration viewing
project cleanup
release planning
dynamic form generation
type validation
sprint management
reassigning issues
issue creation forms

What you can do with Jira

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Issue, 9 operations

POSTbulk_create_issues
Creates multiple Jira issues in a single bulk request for efficiency.
POSTcreate_issue
Creates a new Jira issue in a project with specified type, summary, description, and fields. Supports all standard and custom fields for comprehensive issue creation.
DELETEdelete_issue
Permanently deletes a Jira issue and optionally its subtasks. Requires delete permission on the issue.
GETget_board_issues
Retrieves all issues visible on a Jira board with optional JQL filtering.
GETget_issue
Retrieves complete details of a Jira issue by key or ID. Returns all fields including summary, description, status, assignee, comments, and custom fields.
GETget_sprint_issues
Lists all issues assigned to a specific sprint.
POSTmove_issues_to_sprint
Moves issues into a sprint with optional ranking.
GETsearch_issues
Searches Jira issues using JQL (Jira Query Language) with powerful filtering, sorting, and field selection. Returns paginated results matching complex query criteria.
PUTupdate_issue
Updates fields on an existing Jira issue. Supports partial updates to modify specific fields without affecting others.

Component, 5 operations

POSTcreate_component
Creates a new component in a Jira project for issue categorization.
DELETEdelete_component
Deletes a component from a Jira project with optional issue migration.
GETget_component
Retrieves details of a specific Jira component by its ID.
GETget_project_components
Lists all components defined in a Jira project for categorizing issues.
PUTupdate_component
Updates an existing Jira component's properties.

Sprint, 5 operations

POSTcreate_sprint
Creates a new sprint on a Jira board with name, dates, and optional goal.
DELETEdelete_sprint
Deletes a sprint and moves its issues to the backlog.
GETget_sprint
Retrieves details of a specific sprint by ID.
GETget_sprints
Lists sprints for a Jira Software board with filtering by sprint state. Returns sprint names, dates, and goals for agile planning.
PUTupdate_sprint
Updates sprint properties including name, dates, state, and goal.

Version, 5 operations

POSTcreate_version
Creates a new release version in a Jira project.
DELETEdelete_version
Deletes a version from a Jira project with optional issue migration.
GETget_project_versions
Lists all release versions defined in a Jira project.
GETget_version
Retrieves details of a specific Jira version by its ID.
PUTupdate_version
Updates an existing Jira version's properties.

Worklog, 4 operations

POSTadd_worklog
Logs time spent working on a Jira issue. Records hours for time tracking, billing, and capacity planning.
DELETEdelete_worklog
Deletes a worklog entry from a Jira issue.
GETget_worklogs
Lists all time tracking worklogs for a Jira issue.
PUTupdate_worklog
Updates an existing worklog entry with new time or comment.

Attachment, 3 operations

POSTadd_attachment
Uploads one or more files as attachments to a Jira issue.
DELETEdelete_attachment
Permanently deletes an attachment from a Jira issue.
GETget_attachment
Retrieves metadata for a Jira attachment including filename, size, and content URL.

Issuetype, 3 operations

GETget_issue_type
Retrieves details of a specific Jira issue type by its ID.
GETget_issue_types
Lists all issue types available in Jira (Bug, Story, Task, Epic, etc.).
GETget_project_issue_types
Lists issue types available in a specific Jira project.

Remotelink, 3 operations

POSTcreate_remote_link
Creates a link from a Jira issue to an external resource.
DELETEdelete_remote_link
Deletes a remote link from a Jira issue.
GETget_remote_links
Lists all remote links associated with a Jira issue.

Vote, 3 operations

POSTadd_vote
Adds a vote to a Jira issue from the authenticated user.
GETget_votes
Retrieves the votes for a Jira issue including vote count and voter details.
DELETEremove_vote
Removes the authenticated user's vote from a Jira issue.

Watcher, 3 operations

POSTadd_watcher
Adds a user as a watcher of a Jira issue. The user will receive notifications for issue updates.
GETget_watchers
Retrieves the list of users watching a Jira issue. Returns watcher count and user details.
DELETEremove_watcher
Removes a user from watching a Jira issue. The user will stop receiving notifications.

Board, 2 operations

GETget_board
Retrieves detailed information about a specific Jira board including its configuration.
GETlist_boards
Lists all Jira boards visible to the user with optional filtering by type, name, or project.

Comment, 2 operations

POSTadd_comment
Adds a comment to a Jira issue with rich text formatting support. Comments appear in issue activity feed and can notify watchers.
GETget_comments
Retrieves all comments on a Jira issue with pagination support. Returns comment content, author, and timestamps for activity history.

Filter, 2 operations

GETget_filter
Retrieves a specific saved filter including its JQL query.
GETlist_filters
Lists saved JQL filters accessible to the authenticated user.

Issuelinktype, 2 operations

GETget_issue_link_type
Retrieves details of a specific issue link type by ID.
GETget_issue_link_types
Lists all issue link types available in Jira (Blocks, Clones, Duplicates, etc.).

Priority, 2 operations

GETget_priorities
Lists all issue priorities available in Jira with their details.
GETget_priority
Retrieves details of a specific Jira priority by its ID.

Project, 2 operations

GETget_project
Retrieves detailed information about a specific Jira project including configuration, components, versions, and issue types.
GETget_projects
Lists all Jira projects visible to the authenticated user. Returns project keys, names, and types for project navigation and selection.

Transition, 2 operations

GETget_transitions
Lists available workflow transitions for a Jira issue based on current status and user permissions. Returns transition IDs needed for status changes.
POSTtransition_issue
Moves a Jira issue through workflow states by executing a transition. Changes issue status according to project workflow configuration.

User, 2 operations

GETget_user
Retrieves Jira user details by their account ID. Returns display name, email, avatar, and account status for user displays.
GETsearch_users
Searches for Jira users by name, email, or account ID.

Assignee, 1 operation

PUTassign_issue
Assigns a Jira issue to a user by their account ID. Sets the responsible person for issue completion.

Changelog, 1 operation

GETget_changelog
Returns the history of changes made to a Jira issue.

Createmeta, 1 operation

GETget_createmeta
Returns metadata for creating issues: required fields, allowed values, and field schemas.

Editmeta, 1 operation

GETget_editmeta
Returns metadata for editing an issue: editable fields and allowed values.

Field, 1 operation

GETlist_fields
Lists all Jira fields including system and custom fields.

Issuelink, 1 operation

POSTlink_issues
Creates a link between two Jira issues with a specified relationship type.

Label, 1 operation

GETget_labels
Lists all labels used across Jira issues for categorization.

Status, 1 operation

GETget_statuses
Lists all workflow statuses in Jira with optional filtering.

OAuth scopes Jira requires

Each operation declares the scopes Jira requires for it.

read:jira-workneeded by get_attachment, get_changelog, get_comments and 25 more
write:jira-workneeded by add_attachment, add_comment, add_vote and 16 more
read:jira-userneeded by get_user, search_users

Use Jira from Claude Code, Cursor or Codex

Connect Jira in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Jira operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Jira

Create your workspace
Sign up free. Nothing to install.
Connect Jira once
Add your Jira connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Jira integration FAQ

What can you do with the Jira integration?: LiveContext exposes 67 operations on Jira, covering issue, component, sprint and version. Common uses include sprint planning, sprint reports and configuration viewing.
Which OAuth scopes does Jira require?: It depends on the operation: each one declares the scopes Jira requires for it. The most common are read:jira-work (28 operations), write:jira-work (19 operations) and read:jira-user (2 operations).