List Jira agile boards (scrum or kanban), optionally filtered by type, name, or one project key/ID.

Get a single Jira board by ID, including its projects, location, and settings.

List sprints on a board, optionally filtered by state (active, closed, future).

Get a single sprint by ID (name, state, start/end dates, goal).

Create a new sprint on a board. Dates are ISO-8601 strings, e.g. 2026-09-01T09:00:00.000+0000.

Update a sprint's name, goal, dates, or state (active/closed/future). Only provided fields are changed.

Close a sprint (sets its state to closed).

List the issues in a sprint. Cloud uses the current Software API enhanced endpoint with cursor paging; Data Center uses Agile 1.0 with startAt/total.

Full sprint view like the Jira UI: board details, the sprint, and its issues, in one call. Cloud issue results use Software API cursor paging; Data Center uses Agile 1.0 offset paging.

List a board's backlog issues (in the board's filter, not in a sprint), ordered by rank. On Cloud this uses the current Software API enhanced backlog endpoint and cursor paging; on Data Center it uses Agile 1.0 with startAt/total.

List the epics on a board, including whether each one is done.

Get a single epic by key (e.g. PROJ-1) or numeric issue ID. Falls back to the issue API for team-managed projects, where epics are ordinary issues.

List the issues belonging to an epic. Cloud uses the current Software API enhanced endpoint; Data Center uses Agile 1.0. Falls back to a JQL 'parent = ' search on team-managed projects, where the epic API does not apply.

Create an epic in a project. Company-managed projects usually also require the 'Epic Name' custom field — call get_epic_meta or get_issue_create_meta first and pass it via customFields.

Add issues to an epic. On team-managed projects this sets the issue's parent instead. To remove an issue from an epic, use update_issue with fields { "parent": null } (team-managed) or { "epic": null } (company-managed).

List the epic-level issue types available in a project (hierarchy level above Story/Task). Use get_issue_create_meta for the fields required to create one.

Get a single Jira issue by key (e.g. PROJ-123).

Create a new issue. Use get_issue_create_meta to discover valid projects, issue types, and required fields. Extra custom fields can be passed via customFields (e.g. { 'customfield_10010': 'value' }).

Update an issue. Pass absolute values in fields (e.g. { summary: 'new' }) and/or relative changes in update (e.g. { labels: [{ add: 'x' }, { remove: 'y' }] }).

Delete an issue. This is destructive.

Search issues with JQL, e.g. 'project = PROJ AND sprint = 42 ORDER BY rank' or 'project = PROJ AND sprint IS NONE'. On Jira Cloud this uses enhanced search (/search/jql): the JQL must be bounded (include a restriction such as project, assignee, or key — a bare 'ORDER BY created DESC' is rejected), the response has no total, and paging is by cursor — pass the returned nextPageToken back in for the next page and stop when isLast is true. On Jira Data Center this uses the legacy /search endpoint, which pages with startAt and returns total.

Discover valid projects, issue types, and their fields (with required flags) before creating an issue. Uses the current per-project metadata endpoints instead of the deprecated /issue/createmeta query form. Pass projectKeys when fields are expanded (the default) to bound requests; omit it only with expand=projects.issuetypes for issue-type summaries.

List the workflow transitions available for an issue.

Move an issue through its workflow. Use get_issue_transitions first to find the transition ID and required fields.

Assign (or unassign, with an empty value) an issue to a user. Uses PUT /issue/{key}/assignee with accountId on v3 and name on v2.

Add a comment to an issue.

List comments on an issue.

Delete a comment by its ID (from list_comments).

List time-tracking worklogs on an issue.

Add a worklog (time spent) to an issue. started is optional and defaults to now when omitted; timeSpent uses Jira format, e.g. '2h 30m' or '1d'.

List all Jira projects visible to the current user. Cloud uses paginated /project/search; Data Center uses /project.

Get a single project by key or ID.

List components of a project.

Create a component in a project.

List the issue types available in a project, with their hierarchy levels (epic = 1, story/task = 0, sub-task = -1).

List roles (and their actors) of a project.

List versions (releases) of a project.

Get the profile of the user whose credentials are configured (also verifies auth works).

Search for users by name/email (Cloud) or username (Data Center). Returns account IDs / usernames usable for assignment.

Get a user by account ID (Jira Cloud / API v3) or username (Data Center / API v2).

List all issue fields (including custom field IDs) in the Jira instance.

List all issue types (Story, Task, Bug, Epic, ...) in the Jira instance.

Call any Jira REST API endpoint not covered by a dedicated tool. Path must start with /rest/ and stay under it (e.g. '/rest/api/3/issue/PROJ-1/names' or '/rest/agile/1.0/board/1'). Query params go in query, JSON payload in body. Returns the raw JSON response.