---
title: "Jira MCP server for AI agents - actionlake"
description: "Give Claude 604 Jira actions through one MCP server: fields, workflows, projects, screens. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/jira
updated: 2026-10-11
---

Connectors · Work & projects

# Jira MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Jira and the rest of your systems. It gives your agent 604 Jira actions (303 reads, 198 writes and 103 that wait for a confirmation) and holds the Jira credential itself, so the agent never does. It paces Jira's limits and records every call.

[Connect Jira free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

`claude mcp add --transport http actionlake https://connect.actionlake.com/mcp`

the first call

```
do {
  action: "jira.server_info.get",
  intent: "check which Jira account is connected"
}
# Get Jira server information · read · 1 upstream call
```

- 604 actions in one signed file
- 303 read look, never change
- 198 write create and update
- 103 wait for a yes destructive, confirmed first

Set up

## Connect Jira in three steps.

1. 01
   ### Add actionlake to Claude.
   Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
   `https://connect.actionlake.com/mcp`
2. 02
   ### Connect Jira.
   Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
   - `email` Atlassian account email
   - `api_token` Atlassian API token
   - `site_host` Where your Jira lives: your site host
   ```
   account { op: "connections.requirements", service: "jira" }
   # free: exactly what to paste, and what is found for you
   ```
3. 03
   ### Make the first call. Check before a write.
   Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free.
   ```
   do    { action: "jira.server_info.get" }
   # get jira server information · read · 1 upstream call
   check { action: "jira.issues.create", input: { … } }
   # free: inputs, permissions, cost and confirmations, nothing sent
   ```

Jira at a glance

**Sign-in**

Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.

**You provide**

`email` `api_token`

**Setup fields**

`site_host`

**Limits we pace to**

100 calls a second, per connection

**API covered**

Jira API 3, at your Jira instance's API base URL, which you enter when connecting (path /rest/api/3)

**Built from**

Jira's documentation, read 15 September 2026[developer.atlassian.com](https://developer.atlassian.com/cloud/jira/platform/swagger-v3.v3.json)

**Service file**

Version 2.0.0, signed (Ed25519)

**Cached reads**

303 of 303 reads, for up to an hour; a write clears what it affects

**Ready-made plans**

10 in the store

**Shared entities**

6, so ask can line Jira up with your other systems

**Data**

Processed and stored in Sydney, Australia. No US region yet

Capabilities

## What an AI agent can do in Jira.

604 actions in 39 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

- **303** read look, never change
- **198** write create and update
- **103** destructive wait for a confirmation

1. ### Fields
   75
   30 read · 30 write · 15 destructive
   Set an app field's value on issues · Set several app field values · List Jira fields · List fields available to projects
2. ### Workflows
   55
   27 read · 18 write · 10 destructive
   List projects using a workflow scheme · List projects using a workflow · List workflow scheme project associations · List issue types using a workflow in a project
3. ### Projects
   41
   22 read · 13 write · 6 destructive
   List all Jira projects · List recently viewed projects · Create a Jira project · Search Jira projects
4. ### Screens
   32
   11 read · 15 write · 6 destructive
   List fields available to a screen · List fields on a screen tab · List Jira screens · Get the default issue navigator columns
5. ### Users
   30
   22 read · 4 write · 4 destructive
   List all Jira users · Fetch many Jira users by account id · Fetch user migration identifiers · Get several users' email addresses
6. ### Issues
   29
   18 read · 10 write · 1 destructive
   Create a Jira issue · Report issues approaching ADF limits · Report issues approaching field limits · Search Jira issues with JQL
7. ### Apps
   23
   10 read · 9 write · 4 destructive
   List service registry services · Submit a Connect to Forge migration task · Get a Connect to Forge migration task · List dynamic app modules
8. ### Security
   23
   11 read · 8 write · 4 destructive
   List projects using issue security schemes · List issue security level members · List one scheme's security level members · List issue security levels

**31 more areas · 296 actions**

- Issue types **21**
- Filters **18**
- Permissions **17**
- Dashboards **17**
- Priorities **16**
- Plans **16**
- Roles **15**
- Versions **15**
- Links **14**
- Worklogs **14**
- Statuses **13**
- Comments **10**
- Instance **9**
- Groups **9**
- Bulk **9**
- JQL **9**
- Notifications **8**
- Resolutions **8**
- Properties **8**
- Components **8**
- Attachments **7**
- Avatars **6**
- Webhooks **5**
- Time tracking **5**
- Licensing **5**
- Watchers **4**
- Votes **3**
- Expressions **2**
- Redaction **2**
- Tasks **2**
- Audit **1**

Atlassian's own MCP server

## Atlassian's MCP server, or actionlake?

Atlassian runs the Rovo MCP server for Jira, Jira Service Management and Confluence at mcp.atlassian.com, signed in with OAuth 2.1 or an API token. Its calls use Rovo credits from the organisation's pool.

Use Atlassian's server when one person wants to work in Jira from their own AI client. Use actionlake when you also want Jira behind the same endpoint as your other systems: a key per agent with allowed actions and a spending cap, a named person's approval before destructive actions, a sealed record of every call, and one ask across Jira and another system.

Source: [Atlassian's documentation](https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/), checked 22 October 2026.

Top actions

## The Jira API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 230 of Jira's 235 action names are shared with at least one other connector, so an agent learns them once.

| Action | What it does | Effect | Same name in |
| --- | --- | --- | --- |
| `jira.users.list` List all Jira users | Return every user on the site, paged. Personal data depends on each user's privacy settings. | read | `identity.user.list` 474 connectors |
| `jira.groups.bulk_get` List Jira groups | Return groups on the site, filterable by id or name, paged. | read | `identity.group.list` 262 connectors |
| `jira.issue_worklogs.list` List worklogs on a Jira issue | Return the time logged against one issue, optionally within a date window. | read | `work.time_entry.list` 59 connectors |
| `jira.issues.create` Create a Jira issue | Raise an issue in a project by project key and issue type. | write | `work.task.create` 127 connectors |
| `jira.issues.limit_report` Report issues approaching field limits | List issues whose fields are near Jira's per-field size limits. | read | `work.task.list` 122 connectors |
| `jira.users.bulk_get` Fetch many Jira users by account id | Return a page of users named by account id. | read | `identity.user.list` 474 connectors |
| `jira.projects.list` List all Jira projects | Return every project visible to the caller, unpaged. | read | `work.project.list` 109 connectors |
| `jira.projects.recent` List recently viewed projects | Return up to twenty projects the caller viewed most recently. | read | `work.project.list` 109 connectors |
| `jira.projects.create` Create a Jira project | Create a project from a key, name, project type and template. | write | `work.project.create` 102 connectors |
| `jira.issue_comments.list` List comments on a Jira issue | Return the comments on one issue, oldest or newest first. | read | `work.task_comment.list` 27 connectors |
| `jira.issues.delete` Delete a Jira issue | Permanently delete an issue, optionally its subtasks too. | destructive | `work.task.delete` 107 connectors |
| `jira.issue_comments.create` Comment on a Jira issue | Add a comment to an issue. On v3 the body is Atlassian Document Format. | write | `work.task_comment.create` 28 connectors |

Try it

## Prompts to paste into Claude.

Each one names the Jira actions it will call, so you know what it reads and what it changes before you send it.

1. Read read
   Which Jira tasks are overdue, and who owns each one?
   calls `jira.issues.search`
2. Plan write
   Copy a dashboard for a team and point its gadgets at their filter in Jira.
   calls `jira.dashboards.search` `jira.filters.create` `jira.dashboards.copy` `jira.dashboards.gadgets_list` `jira.dashboards.gadget_update` +1 more
3. Plan write
   Raise an incident ticket and link it to the offending work in Jira.
   calls `jira.issues.create` `jira.issue_remote_links.update` `jira.issues.search` `jira.issue_links.create` `jira.issues.get`
4. Write write
   Create a Jira issue in Jira. Show me exactly what you will send before you save it.
   calls `jira.issues.create`
5. Across systems read
   For each customer, how many projects are in Jira and how many invoices in ConnectWise PSA?
   calls `jira.projects.search` `connectwise_manage.invoices.list`

Across your systems

## Jira, joined to the rest of your business.

One `ask` fetches from Jira and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row.

- For each customer, how many projects are in Jira and how many invoices in ConnectWise PSA?
  `jira.projects.search` + `connectwise_manage.invoices.list`, on `crm.company` · [ConnectWise PSA](https://actionlake.com/connectors/connectwise-psa)
- For each customer, how many projects are in Jira and how many invoices in NetSuite?
  `jira.projects.search` + `netsuite.views.invoices`, on `crm.company` · [NetSuite](https://actionlake.com/connectors/netsuite)

Also mapped by other connectors `identity.user` **517** `identity.group` **239** `work.project` **116** `work.task` **105** `work.time_entry` **40** `work.task_comment` **9**

ask

```
ask {
  intent: "for each customer, how many projects are in Jira and how many invoices in ConnectWise PSA",
  steps: [
    { action: "jira.projects.search", as: "proj", input: {}, limit: 100, max_pages: 5 },
    { action: "connectwise_manage.invoices.list", as: "inv", input: {}, limit: 100, max_pages: 5 },
    { join: {
        left: "proj",
        right: "inv",
        on: "crm.company",
        group_by: "proj.company_name",
        select: ["proj.company_name", "count(proj.id) as projects", "count(inv.id) as invoices"]
    } }
  ]
}
```

Example. Run it through check first: it validates the steps and prices them, and it is free.

The plan store

## Ready-made plans for Jira.

10 plans in the store. Install one and your agent runs it by name; the reply says which connections are still missing. A schedule can run a plan on a timetable. There are no triggers or webhooks, by design.

1. ### Report time logged against a sprint's issues
   Use it when Someone wants to see how time was logged across a project for a given period before invoicing or a retro.
   **Effect**
   read
   **Steps**
   4 · loops
   **Needs**
   project key, since and until
   **Install**
   `jira-sprint-worklog-report`
2. ### Snapshot a project's open work, components and versions
   Use it when Someone wants a quick factual read on where a project stands before a planning meeting.
   **Effect**
   read
   **Steps**
   5 · loops
   **Needs**
   project key
   **Install**
   `jira-project-health-snapshot`
3. ### Raise an incident ticket and link it to the offending work
   Use it when An alert has fired and an incident issue needs raising and wiring to the recent changes that could have caused it.
   **Effect**
   write
   **Steps**
   5 · loops
   **Needs**
   alert url, component, detail, project key and summary
   **Install**
   `jira-incident-ticket-with-linkage`
4. ### Move a filtered set of issues through one workflow transition
   Use it when A filter's worth of issues all need pushing through the same workflow transition in one go.
   A person decides Transition _number of issues_ issues from filter _name_ and set resolution _resolution name_.
   **Effect**
   write
   **Steps**
   5 · loops
   **Needs**
   filter id, note, resolution name and transition id
   **Install**
   `jira-move-issues-through-transition`
5. ### Cut a new release version and move open work onto it
   Use it when A release is being cut and unresolved issues need to roll forward onto the next fix version.
   A person decides Move _issuesUnresolvedCount_ unresolved issues from the outgoing version onto _new version name_.
   **Effect**
   write
   **Steps**
   5 · loops
   **Needs**
   new version name, old version id, project id, project key and release date
   **Install**
   `jira-release-version-cutover`
6. ### Sweep stale bugs and flag them for the lead
   Use it when A project's bug backlog has gone stale and someone wants the old ones labelled and put in front of an owner.
   A person decides Label _count_ stale bugs in _project key_ as needs-triage and add the backlog owner as a watcher.
   **Effect**
   write
   **Steps**
   5 · loops
   **Needs**
   days idle, owner account id and project key
   **Install**
   `jira-stale-bug-triage-sweep`
7. ### Archive long-closed issues and wait for the job
   Use it when A project has years of closed issues cluttering search and they should be archived out of the way.
   A person decides Archive _count_ issues in _project key_ that have been closed for over _closed before days_ days.
   **Effect**
   write
   **Steps**
   6
   **Needs**
   closed before days and project key
   **Install**
   `jira-archive-closed-issues`
8. ### Copy a dashboard for a team and point its gadgets at their filter
   Use it when A team wants their own copy of someone else's Jira dashboard scoped to their project.
   **Effect**
   write
   **Steps**
   6 · loops
   **Needs**
   new name, project key and source dashboard name
   **Install**
   `jira-duplicate-dashboard-for-team`
9. ### Delete a batch of issues after a human signs off
   Use it when A batch of junk or migrated-away issues must be permanently deleted and someone must sign off on the count first.
   A person decides Permanently delete _count_ issues matching the supplied JQL. This cannot be undone.
   **Effect**
   destructive
   **Steps**
   5
   **Needs**
   jql
   **Install**
   `jira-bulk-issue-delete-with-signoff`
10. ### Create a user and give them a role on a project
    Use it when A new person is joining a team and needs a Jira account plus access to one project.
    A person decides Grant _display name_ the _role name_ role on project _project key_.
    **Effect**
    destructive
    **Steps**
    6
    **Needs**
    display name, email, project key and role name
    **Install**
    `jira-onboard-user-to-project`

install a plan

```
account { op: "plans.install", slug: "jira-sprint-worklog-report" }
# then ask for it by name; a schedule can run it on a timetable
```

Governance for Jira

## Destructive actions wait for a yes.

103 Jira actions are destructive. The first 10:

- Delete a Jira issue `jira.issues.delete`
- Delete a Jira project `jira.projects.delete`
- Delete a Jira project asynchronously `jira.projects.delete_async`
- Delete a Jira user `jira.users.delete`
- Delete a Jira group `jira.groups.delete`
- Delete a Jira worklog `jira.issue_worklogs.delete`
- Delete many worklogs on an issue `jira.issue_worklogs.delete_bulk`
- Delete a Jira issue comment `jira.issue_comments.delete`
- Bulk delete Jira issues `jira.issue_bulk_operations.delete`
- Delete a plan-only team `jira.plan_teams.planonly_delete`

A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

do jira.issues.delete confirm_policy: **human**

Delete a Jira issue?

**intent:** the user asked me to delete a Jira issue

run suspended · waiting for a named person · key _jira-agent_ cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

```
account {
  op: "keys.create", name: "jira-agent",
  allowed_actions: ["jira.*"], cap_calls: 2000,
  confirm_policy: "human_for_writes",
  approval_rules: [
    { match: "jira.issues.delete", approver: "lead@example.com" },
    { match: "jira.projects.delete", approver: "lead@example.com" },
    { match: "jira.projects.delete_async", approver: "lead@example.com" }
  ]
}
```

Illustrative. Scoped to Jira only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

## What Jira costs on actionlake.

Every Jira action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Jira refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

- 1 upstream call per action all 604 Jira actions
- 93 actions page each page of a long list is one call
- 303 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every Jira action.

604 actions by area: the id your agent calls, what it does, and its effect.

**Fields 75**

- `jira.app_field_options.value_update` Set an app field's value on issues write
- `jira.app_field_options.values_update_many` Set several app field values write
- `jira.issue_fields.list` List Jira fields read
- `jira.issue_fields.project_fields` List fields available to projects read
- `jira.app_field_options.config_get` Get an app field's context configuration read
- `jira.app_field_options.config_update` Update an app field's context configuration write
- and 69 more in this area

**Workflows 55**

- `jira.workflow_scheme_projects.list` List workflow scheme project associations read
- `jira.workflow_schemes.project_usages` List projects using a workflow scheme read
- `jira.workflows.issue_type_usages` List issue types using a workflow in a project read
- `jira.workflows.project_usages` List projects using a workflow read
- `jira.workflow_scheme_drafts.create` Create a workflow scheme draft write
- `jira.workflow_scheme_drafts.default_delete` Reset a draft's default workflow destructive
- and 49 more in this area

**Projects 41**

- `jira.projects.create` Create a Jira project write
- `jira.projects.list` List all Jira projects read
- `jira.projects.recent` List recently viewed projects read
- `jira.projects.search` Search Jira projects read
- `jira.project_avatars.delete` Delete a project avatar destructive
- `jira.project_avatars.list` List a project's avatars read
- and 35 more in this area

**Screens 32**

- `jira.issue_navigator_settings.columns_get` Get the default issue navigator columns read
- `jira.screen_tab_fields.list` List fields on a screen tab read
- `jira.screens.available_fields` List fields available to a screen read
- `jira.screens.list` List Jira screens read
- `jira.issue_type_screen_schemes.append_mappings` Add mappings to an issue type screen scheme write
- `jira.issue_type_screen_schemes.assign_project` Assign an issue type screen scheme to a project write
- and 26 more in this area

**Users 30**

- `jira.users.bulk_get` Fetch many Jira users by account id read
- `jira.users.bulk_migration` Fetch user migration identifiers read
- `jira.users.email_bulk` Get several users' email addresses read
- `jira.users.list` List all Jira users read
- `jira.myself.get` Get the current Jira user read
- `jira.myself.locale_get` Get my locale read
- and 24 more in this area

**Issues 29**

- `jira.issues.adf_limit_report` Report issues approaching ADF limits read
- `jira.issues.create` Create a Jira issue write
- `jira.issues.limit_report` Report issues approaching field limits read
- `jira.issues.search` Search Jira issues with JQL read
- `jira.issues.archive` Archive issues by id or key write
- `jira.issues.archive_export` Export archived issues write
- and 23 more in this area

**Apps 23**

- `jira.app_migration.forge_task_get` Get a Connect to Forge migration task read
- `jira.app_migration.forge_task_submit` Submit a Connect to Forge migration task write
- `jira.app_migration.service_registry` List service registry services read
- `jira.dynamic_modules.list` List dynamic app modules read
- `jira.app_migration.update_fields` Update app field values during migration write
- `jira.app_migration.update_properties` Update entity properties during migration write
- and 17 more in this area

**Security 23**

- `jira.issue_security_schemes.level_members_list` List issue security level members read
- `jira.issue_security_schemes.levels_list` List issue security levels read
- `jira.issue_security_schemes.projects_search` List projects using issue security schemes read
- `jira.issue_security_schemes.scheme_members_list` List one scheme's security level members read
- `jira.issue_security_schemes.associate_projects` Assign an issue security scheme to projects write
- `jira.issue_security_schemes.create` Create an issue security scheme write
- and 17 more in this area

**Issue types 21**

- `jira.issue_types.alternatives` List alternative issue types read
- `jira.issue_types.create` Create a Jira issue type write
- `jira.issue_types.for_project` List issue types for a project read
- `jira.issue_types.list` List Jira issue types read
- `jira.issue_type_properties.delete` Delete an issue type property destructive
- `jira.issue_type_properties.get` Get an issue type property read
- and 15 more in this area

**Filters 18**

- `jira.filters.change_owner` Change a Jira filter's owner write
- `jira.filters.create` Create a Jira filter write
- `jira.filters.my_filters` List my Jira filters read
- `jira.filters.search` Search Jira filters read
- `jira.filter_sharing.add` Share a Jira filter write
- `jira.filter_sharing.default_scope_get` Get the default filter share scope read
- and 12 more in this area

**Permissions 17**

- `jira.permissions.bulk_check` Check permissions in bulk read
- `jira.permissions.list_all` List every Jira permission read
- `jira.permissions.my_permissions` Check my Jira permissions read
- `jira.permissions.permitted_projects` List projects where I hold a permission read
- `jira.permission_schemes.create` Create a permission scheme write
- `jira.permission_schemes.delete` Delete a permission scheme destructive
- and 11 more in this area

**Dashboards 17**

- `jira.dashboards.create` Create a Jira dashboard write
- `jira.dashboards.gadgets_available` List available dashboard gadgets read
- `jira.dashboards.get` Get one Jira dashboard read
- `jira.dashboards.list` List Jira dashboards read
- `jira.dashboards.bulk_edit` Bulk edit Jira dashboards write
- `jira.dashboards.copy` Copy a Jira dashboard write
- and 11 more in this area

**Priorities 16**

- `jira.priorities.create` Create a Jira issue priority write
- `jira.priorities.list` List Jira issue priorities read
- `jira.priorities.search` Search Jira issue priorities read
- `jira.priority_schemes.projects_list` List projects using a priority scheme read
- `jira.priorities.delete` Delete a Jira issue priority destructive
- `jira.priorities.get` Get one Jira issue priority read
- and 10 more in this area

**Plans 16**

- `jira.plan_teams.atlassian_get` Get an Atlassian team in a plan read
- `jira.plan_teams.list` List a plan's teams read
- `jira.plan_teams.planonly_create` Create a plan-only team write
- `jira.plan_teams.planonly_get` Get a plan-only team read
- `jira.plan_teams.atlassian_add` Add an Atlassian team to a plan write
- `jira.plan_teams.atlassian_remove` Remove an Atlassian team from a plan destructive
- and 10 more in this area

**Roles 15**

- `jira.project_roles.create` Create a Jira project role write
- `jira.project_roles.details_for_project` List a project's role details read
- `jira.project_roles.for_project` List a project's roles read
- `jira.project_roles.list_global` List Jira project roles read
- `jira.project_role_actors.add_default` Add default actors to a role destructive
- `jira.project_role_actors.add_to_project` Add actors to a project role destructive
- and 9 more in this area

**Versions 15**

- `jira.project_versions.create` Create a Jira version write
- `jira.project_versions.list` List a project's versions read
- `jira.project_versions.related_issue_counts` Count issues on a version read
- `jira.project_versions.unresolved_count` Count unresolved issues on a version read
- `jira.project_versions.delete` Delete a Jira version destructive
- `jira.project_versions.delete_and_replace` Delete a version and swap references destructive
- and 9 more in this area

**Links 14**

- `jira.issue_links.create` Link two Jira issues write
- `jira.issue_links.delete` Delete a Jira issue link destructive
- `jira.issue_links.get` Get one Jira issue link read
- `jira.issue_remote_links.list` List an issue's remote links read
- `jira.issue_link_types.create` Create a Jira issue link type write
- `jira.issue_link_types.delete` Delete a Jira issue link type destructive
- and 8 more in this area

**Worklogs 14**

- `jira.issue_worklogs.create` Log work on a Jira issue write
- `jira.issue_worklogs.deleted_since` List worklogs deleted since a time read
- `jira.issue_worklogs.list` List worklogs on a Jira issue read
- `jira.issue_worklogs.updated_since` List worklogs changed since a time read
- `jira.issue_worklog_properties.delete` Delete a worklog property destructive
- `jira.issue_worklog_properties.get` Get a worklog property read
- and 8 more in this area

**Statuses 13**

- `jira.statuses.by_names` Fetch statuses by name read
- `jira.statuses.categories_list` List Jira status categories read
- `jira.statuses.get_by_ids` Fetch statuses by id read
- `jira.statuses.project_usages` List projects using a status read
- `jira.statuses.category_get` Get one Jira status category read
- `jira.statuses.create` Create Jira statuses write
- and 7 more in this area

**Comments 10**

- `jira.issue_comments.create` Comment on a Jira issue write
- `jira.issue_comments.get_by_ids` Fetch comments by id read
- `jira.issue_comments.list` List comments on a Jira issue read
- `jira.issue_comments.update` Update a Jira issue comment write
- `jira.issue_comment_properties.delete` Delete a comment property destructive
- `jira.issue_comment_properties.get` Get a comment property read
- and 4 more in this area

**Instance 9**

- `jira.jira_settings.advanced_settings` List advanced Jira settings read
- `jira.jira_settings.application_properties` List Jira application properties read
- `jira.jira_settings.configuration_get` Get the Jira global configuration read
- `jira.server_info.get` Get Jira server information read
- `jira.data_policies.projects_list` List projects' data policies read
- `jira.data_policies.workspace_get` Get the site's data policy read
- and 3 more in this area

**Groups 9**

- `jira.groups.bulk_get` List Jira groups read
- `jira.groups.create` Create a Jira group write
- `jira.groups.delete` Delete a Jira group destructive
- `jira.groups.get` Get a Jira group read
- `jira.groups.find` Search Jira groups read
- `jira.groups.member_add` Add a user to a Jira group write
- and 3 more in this area

**Bulk 9**

- `jira.issue_bulk_operations.delete` Bulk delete Jira issues destructive
- `jira.issue_bulk_operations.edit` Bulk edit Jira issues write
- `jira.issue_bulk_operations.move` Bulk move Jira issues write
- `jira.issue_bulk_operations.transition` Bulk transition Jira issues write
- `jira.issue_bulk_operations.available_transitions` List transitions available across issues read
- `jira.issue_bulk_operations.editable_fields` List bulk-editable fields read
- and 3 more in this area

**JQL 9**

- `jira.jql.autocomplete` Get JQL autocomplete data read
- `jira.jql.autocomplete_post` Get JQL autocomplete data for a context read
- `jira.jql.precomputations_by_id` Fetch JQL precomputations by id read
- `jira.jql.precomputations_list` List JQL function precomputations read
- `jira.jql.migrate` Migrate JQL user identifiers read
- `jira.jql.parse` Parse JQL queries read
- and 3 more in this area

**Notifications 8**

- `jira.notification_schemes.create` Create a notification scheme write
- `jira.notification_schemes.get` Get one notification scheme read
- `jira.notification_schemes.list` List notification schemes read
- `jira.notification_schemes.project_mappings` List notification schemes by project read
- `jira.notification_schemes.delete` Delete a notification scheme destructive
- `jira.notification_schemes.notification_remove` Remove a notification from a scheme destructive
- and 2 more in this area

**Resolutions 8**

- `jira.resolutions.create` Create a Jira issue resolution write
- `jira.resolutions.get` Get one Jira issue resolution read
- `jira.resolutions.list` List Jira issue resolutions read
- `jira.resolutions.search` Search Jira issue resolutions read
- `jira.resolutions.delete` Delete a Jira issue resolution destructive
- `jira.resolutions.reorder` Reorder Jira issue resolutions write
- and 2 more in this area

**Properties 8**

- `jira.issue_properties.keys_list` List an issue's property keys read
- `jira.issue_properties.set` Set an issue property write
- `jira.issue_properties.set_bulk_by_key` Set one property on many issues write
- `jira.issue_properties.set_bulk_list` Set properties on a list of issues write
- `jira.issue_properties.delete` Delete an issue property destructive
- `jira.issue_properties.delete_bulk_by_key` Delete one property from many issues destructive
- and 2 more in this area

**Components 8**

- `jira.project_components.find_for_projects` Find components across projects read
- `jira.project_components.list` List a project's components read
- `jira.project_components.list_all` List all components of a project read
- `jira.project_components.related_issue_counts` Count issues on a component read
- `jira.project_components.create` Create a Jira component write
- `jira.project_components.delete` Delete a Jira component destructive
- and 2 more in this area

**Attachments 7**

- `jira.issue_attachments.delete` Delete a Jira attachment destructive
- `jira.issue_attachments.expand_human` List an archive attachment's contents read
- `jira.issue_attachments.expand_raw` List an archive attachment's raw entries read
- `jira.issue_attachments.get` Get Jira attachment metadata read
- `jira.issue_attachments.content` Download a Jira attachment read
- `jira.issue_attachments.meta` Get attachment settings read
- and 1 more in this area

**Avatars 6**

- `jira.avatars.delete` Delete an avatar destructive
- `jira.avatars.image_by_id` Get an avatar image by id read
- `jira.avatars.owner_list` List an entity's avatars read
- `jira.avatars.system_list` List system avatars read
- `jira.avatars.image_by_owner` Get an entity's avatar image read
- `jira.avatars.image_by_type` Get a default avatar image read

**Webhooks 5**

- `jira.webhooks.failed_list` List failed webhook deliveries read
- `jira.webhooks.list` List registered webhooks read
- `jira.webhooks.refresh` Refresh webhook expiry write
- `jira.webhooks.register` Register webhooks write
- `jira.webhooks.delete` Delete registered webhooks destructive

**Time tracking 5**

- `jira.time_tracking.options_get` Get time tracking settings read
- `jira.time_tracking.options_set` Set time tracking settings write
- `jira.time_tracking.provider_get` Get the time tracking provider read
- `jira.time_tracking.providers_list` List time tracking providers read
- `jira.time_tracking.provider_set` Set the time tracking provider write

**Licensing 5**

- `jira.application_roles.get` Get one Jira application role read
- `jira.application_roles.list` List Jira application roles read
- `jira.license_metrics.approximate_count` Get approximate licensed user count read
- `jira.license_metrics.approximate_count_product` Get approximate licences for a product read
- `jira.license_metrics.instance_license` Get the site licence read

**Watchers 4**

- `jira.issue_watchers.add` Add a watcher to a Jira issue write
- `jira.issue_watchers.is_watching_bulk` Check watching status for many issues read
- `jira.issue_watchers.list` List an issue's watchers read
- `jira.issue_watchers.remove` Remove a watcher from a Jira issue destructive

**Votes 3**

- `jira.issue_votes.add` Vote for a Jira issue write
- `jira.issue_votes.get` Get an issue's votes read
- `jira.issue_votes.remove` Remove a vote from a Jira issue destructive

**Expressions 2**

- `jira.jira_expressions.analyse` Analyse a Jira expression read
- `jira.jira_expressions.evaluate` Evaluate a Jira expression read

**Redaction 2**

- `jira.issue_redaction.redact` Redact issue content write
- `jira.issue_redaction.status` Get a redaction job's status read

**Tasks 2**

- `jira.tasks.cancel` Cancel a long-running task destructive
- `jira.tasks.get` Get a long-running task's status read

**Audit 1**

- `jira.audit_records.list` List Jira audit records read

This index shows a sample of each area. All 604 actions, with their inputs and prices, are in the [catalogue](https://actionlake.com/console/catalogue), which a free sandbox key can search.

Questions

## The Jira MCP server, answered.

**Is there a Jira MCP server for Claude?**

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 604 Jira actions across fields, workflows, projects and screens, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Atlassian.

**Does Atlassian have its own MCP server?**

Atlassian runs the Rovo MCP server for Jira, Jira Service Management and Confluence at mcp.atlassian.com, signed in with OAuth 2.1 or an API token. Its calls use Rovo credits from the organisation's pool. (Atlassian's documentation, checked 22 October 2026.) Use Atlassian's server when one person wants to work in Jira from their own AI client. Use actionlake when you also want Jira behind the same endpoint as your other systems: a key per agent with allowed actions and a spending cap, a named person's approval before destructive actions, a sealed record of every call, and one ask across Jira and another system.

**What do I need to connect Jira?**

Atlassian account email and Atlassian API token. Plus your site host. The free call account { op: "connections.requirements", service: "jira" } lists exactly what to paste.

**Can an AI agent delete or change things in Jira?**

Only if its key allows it, and only with an explicit confirmation. 103 Jira actions are destructive, including delete a Jira issue, delete a Jira project and delete a Jira project asynchronously. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

**Will an AI agent use up my Jira API limit?**

actionlake paces every call to the limits in the Jira service file: 100 calls a second per connection. Repeated reads are answered from cache (303 Jira actions can be), which never reaches Jira.

**What does a Jira action cost?**

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (93 Jira actions page). Cache hits, searches, dry runs and calls Jira refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

**Which Jira API does it cover?**

The Jira API 3 at your Jira instance's API base URL, which you enter when connecting (path /rest/api/3). It is built from Jira's documentation as read on 15 September 2026. 604 actions in 39 areas, each one in the signed service file (version 2.0.0).

**Can I combine Jira with my other systems?**

Yes. ask joins Jira to ConnectWise PSA or NetSuite on the same customer and returns the answer rather than every row. Jira maps work.project, which 116 other connectors also map.

**Does actionlake keep my Jira data, and where?**

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to an hour, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Jira credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

**Which AI clients can use it?**

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

## More connectors like Jira

Shares the most action names with

- [Teamwork 101](https://actionlake.com/connectors/teamwork)
- [Asana 79](https://actionlake.com/connectors/asana)
- [Basecamp 59](https://actionlake.com/connectors/basecamp)
- [Plane 57](https://actionlake.com/connectors/plane)
- [Shortcut 53](https://actionlake.com/connectors/shortcut)
- [JetBrains YouTrack 49](https://actionlake.com/connectors/jetbrains-youtrack)

Joins with, on shared entities

- [Odoo 5](https://actionlake.com/connectors/odoo)
- [Hubstaff 5](https://actionlake.com/connectors/hubstaff)
- [HaloPSA 4](https://actionlake.com/connectors/halopsa)
- [GitLab 4](https://actionlake.com/connectors/gitlab)
- [Zoho Books 4](https://actionlake.com/connectors/zoho-books)
- [Productive.io 4](https://actionlake.com/connectors/productive-io)

Browse

- [All Work & projects connectors](https://actionlake.com/connectors/category/work-and-projects)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by Atlassian; the name is the vendor's own. Counts are from the Jira service file, version 2.0.0.

## Give your agent Jira today.

[Connect Jira free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

---

Source: https://actionlake.com/connectors/jira
More: https://actionlake.com/llms.txt