---
title: "Jira Service Management MCP server - actionlake"
description: "Give Claude 74 Jira Service Management actions through one MCP server: customers, ITSM. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/jira-service-management
updated: 2026-09-24
---

Connectors · Service desk & support

# Jira Service Management MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Jira Service Management and the rest of your systems. It gives your agent 74 Jira Service Management actions (44 reads, 19 writes and 11 that wait for a confirmation) and holds the Jira Service Management credential itself, so the agent never does. It paces Jira Service Management's limits and records every call. Connecting Jira Service Management needs your own Jira Service Management OAuth app and one admin sign-in.

[Connect Jira Service Management 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_sm.info.get",
  intent: "check which Jira Service Management account is connected"
}
# Get Jira Service Management info · read · 1 upstream call
```

- 74 actions in one signed file
- 44 read look, never change
- 19 write create and update
- 11 wait for a yes destructive, confirmed first

Set up

## Connect Jira Service Management 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 Service Management.
   OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Jira Service Management, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key.
   Before the first sign-in, Jira Service Management needs an OAuth app of your own, registered in its developer portal. actionlake has no Jira Service Management app to lend you.
   - `access_token` Access token from one sign-in with your own OAuth app
   - `refresh_token` Refresh token from the same sign-in; the access token is renewed from it
   - `client_id` Atlassian OAuth 2.0 (3LO) client id
   - `client_secret` Atlassian OAuth 2.0 (3LO) client secret
   Found for you at connect: cloud id, site url and the organisations, sites or workspaces the credential can reach.
   ```
   account { op: "connections.requirements", service: "jira_sm" }
   # 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_sm.info.get" }
   # get jira service management info · read · 1 upstream call
   check { action: "jira_sm.requests.create", input: { … } }
   # free: inputs, permissions, cost and confirmations, nothing sent
   ```

Jira Service Management at a glance

**Sign-in**

OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Jira Service Management, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on.

**You provide**

`access_token` `refresh_token` `client_id` `client_secret`

**Found for you**

cloud id, site url and the organisations, sites or workspaces the credential can reach

**Limits we pace to**

100 calls a second, per connection

**API covered**

Jira Service Management API 1`api.atlassian.com`

**Built from**

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

**Service file**

Version 2.0.0, signed (Ed25519)

**Cached reads**

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

**Ready-made plans**

6 in the store

**Shared entities**

6, so ask can line Jira Service Management 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 Service Management.

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

- **44** read look, never change
- **19** write create and update
- **11** destructive wait for a confirmation

1. ### Customers
   22
   7 read · 9 write · 6 destructive
   List customers on a service desk · List organizations · List users in an organization · List organizations on a service desk
2. ### ITSM
   21
   13 read · 6 write · 2 destructive
   List customer requests · List comments on a request · Raise a customer request · Comment on a request
3. ### Catalogue
   12
   8 read · 2 write · 2 destructive
   List request types across all service desks · List request type groups · List request types on a service desk · Create a request type
4. ### Approvals
   3
   2 read · 1 write · 0 destructive
   List approvals on a request · Get one approval on a request · Approve or decline a request
5. ### Knowledge
   3
   3 read · 0 write · 0 destructive
   Search knowledge base articles · Search a service desk's knowledge base · Get a knowledge base article
6. ### Queues
   3
   3 read · 0 write · 0 destructive
   List issues in a queue · List queues in a service desk · Get one queue
7. ### Satisfaction
   3
   1 read · 1 write · 1 destructive
   Leave customer feedback on a request · Get customer feedback on a request · Delete customer feedback on a request
8. ### Administration
   2
   2 read · 0 write · 0 destructive
   List service desks · Get one service desk

**3 more areas · 5 actions**

- Assets **2**
- Sla **2**
- Platform **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 Service Management from their own AI client. Use actionlake when you also want Jira Service Management 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 Service Management 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 Service Management API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 49 of Jira Service Management's 52 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_sm.requests.list` List customer requests | List customer requests across desks, filtered by desk, status, type, organization or text. | read | `service.ticket.list` 56 connectors |
| `jira_sm.servicedesk_customers.list` List customers on a service desk | List the customer accounts with access to one service desk, optionally filtered by name. | read | `crm.contact.list` 177 connectors |
| `jira_sm.organizations.list` List organizations | List the customer organizations on this site, optionally only those one account belongs to. | read | `crm.company.list` 162 connectors |
| `jira_sm.servicedesks.list` List service desks | List every service desk (JSM project) the caller can see, with its project key and name. | read | `service.queue.list` 21 connectors |
| `jira_sm.request_comments.list` List comments on a request | List the public and internal comments on one customer request. | read | `service.ticket_note.list` 20 connectors |
| `jira_sm.queue_issues.list` List issues in a queue | List the Jira issues currently sitting in one agent queue. | read | `service.ticket.list` 56 connectors |
| `jira_sm.requests.create` Raise a customer request | Create a customer request of a given type on a service desk. | write | `service.ticket.create` 54 connectors |
| `jira_sm.organization_users.list` List users in an organization | List the customer accounts belonging to one organization. | read | `crm.contact.list` 177 connectors |
| `jira_sm.servicedesk_organizations.list` List organizations on a service desk | List the customer organizations attached to one service desk. | read | `crm.company.list` 162 connectors |
| `jira_sm.customers.create` Create a customer | Create an Atlassian customer account for a portal user by email address. | write | `crm.contact.create` 161 connectors |
| `jira_sm.request_comments.create` Comment on a request | Add a public or internal comment to a customer request. | write | `service.ticket_note.create` 24 connectors |
| `jira_sm.organization_users.delete` Remove users from an organization | Remove customer accounts from an organization by Atlassian accountId. | destructive | `crm.contact.delete` 147 connectors |

Try it

## Prompts to paste into Claude.

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

1. Read read
   Which Jira Service Management tickets have been open the longest? Show me the ten oldest with their status.
   calls `jira_sm.requests.list`
2. Plan write
   Create an organization and add it to a service desk in Jira Service Management. Ask me before anything is sent or changed.
   calls `jira_sm.servicedesks.get` `jira_sm.organizations.list` `jira_sm.organizations.create` `jira_sm.servicedesk_customers.invite` `jira_sm.organization_users.create` +1 more
3. Plan write
   Validate and raise a request on behalf of a customer in Jira Service Management.
   calls `jira_sm.request_types.get` `jira_sm.requests.validate` `jira_sm.requests.create` `jira_sm.request_participants.create` `jira_sm.request_comments.create` +1 more
4. Write write
   Raise a customer request in Jira Service Management. Show me exactly what you will send before you save it.
   calls `jira_sm.requests.create`
5. Across systems read
   Which Jira Service Management companies have invoices in ConnectWise PSA, and how many each?
   calls `jira_sm.organizations.list` `connectwise_manage.invoices.list`

Across your systems

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

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

- Which Jira Service Management companies have invoices in ConnectWise PSA, and how many each?
  `jira_sm.organizations.list` + `connectwise_manage.invoices.list`, on `crm.company` · [ConnectWise PSA](https://actionlake.com/connectors/connectwise-psa)
- Which Jira Service Management companies have invoices in NetSuite, and how many each?
  `jira_sm.organizations.list` + `netsuite.views.invoices`, on `crm.company` · [NetSuite](https://actionlake.com/connectors/netsuite)

Also mapped by other connectors `crm.company` **227** `crm.contact` **192** `service.ticket` **62** `knowledge.article` **22** `service.queue` **14** `service.ticket_note` **5**

ask

```
ask {
  intent: "which Jira Service Management companies have invoices in ConnectWise PSA, and how many each",
  steps: [
    { action: "jira_sm.organizations.list", as: "co", input: {}, limit: 100, max_pages: 5 },
    { action: "connectwise_manage.invoices.list", as: "inv", input: {}, limit: 100, max_pages: 5 },
    { join: {
        left: "co",
        right: "inv",
        on: "crm.company",
        group_by: "co.name",
        select: ["co.name", "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 Service Management.

6 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. ### Audit the request type catalogue of a service desk
   Use it when Someone wants a full picture of what customers can raise on a service desk and what each form collects.
   **Effect**
   read
   **Steps**
   5 · loops
   **Needs**
   service desk id
   **Install**
   `jira_sm-request-type-catalogue-audit`
2. ### Sweep a queue for SLA risk and comment on the worst
   Use it when A support lead wants to know which requests in a queue are about to breach SLA and wants the findings recorded on the tickets.
   **Effect**
   write
   **Steps**
   3 · loops
   **Needs**
   service desk id and queue id
   **Install**
   `jira_sm-sla-breach-sweep`
3. ### Answer a pending request approval after a human signs off
   Use it when A request is blocked on a service desk approval and someone needs the decision recorded with an audit trail.
   A person decides Record '_decision_' on approval for _issue id or key_: _requestFieldValues_
   **Effect**
   write
   **Steps**
   6
   **Needs**
   issue id or key and decision
   **Install**
   `jira_sm-approval-decision-run`
4. ### Create an organization and add it to a service desk
   Use it when A new customer company is being onboarded and needs an organization, portal accounts and access to a service desk.
   A person decides Create organization '_organization name_' on service desk _projectName_ and invite _number of emails_ customers.
   **Effect**
   write
   **Steps**
   6 · loops
   **Needs**
   service desk id, organization name and emails
   **Install**
   `jira_sm-onboard-customer-organization`
5. ### Validate and raise a request on behalf of a customer
   Use it when An agent or automation needs to create a service desk request for a customer and wants the form checked before it is submitted.
   **Effect**
   write
   **Steps**
   6
   **Needs**
   service desk id, request type id and request field values
   **Install**
   `jira_sm-raise-request-with-validation`
6. ### Answer a request from the knowledge base and transition it
   Use it when A request looks like a known question and an agent wants to answer it from the knowledge base and move it on.
   A person decides Transition _issue id or key_ using transition _transition id_ after answering from the knowledge base.
   **Effect**
   write
   **Steps**
   7
   **Needs**
   service desk id, issue id or key, query and transition id
   **Install**
   `jira_sm-resolve-with-knowledge-answer`

install a plan

```
account { op: "plans.install", slug: "jira_sm-request-type-catalogue-audit" }
# then ask for it by name; a schedule can run it on a timetable
```

Governance for Jira Service Management

## Destructive actions wait for a yes.

11 Jira Service Management actions are destructive. These are all of them:

- Remove users from an organization `jira_sm.organization_users.delete`
- Remove customers from a service desk `jira_sm.servicedesk_customers.delete`
- Delete an organization `jira_sm.organizations.delete`
- Detach an organization from a service desk `jira_sm.servicedesk_organizations.delete`
- Revoke a customer's portal-only access `jira_sm.customers.revoke_portal_access`
- Delete a request type `jira_sm.request_types.delete`
- Remove participants from a request `jira_sm.request_participants.delete`
- Unsubscribe from a request's notifications `jira_sm.request_notifications.unsubscribe`
- Delete customer feedback on a request `jira_sm.request_feedback.delete`
- Delete an organization property `jira_sm.organization_properties.delete`
- Delete a request type property `jira_sm.request_type_properties.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_sm.organization_users.delete confirm_policy: **human**

Remove users from an organization?

**intent:** the user asked me to remove users from an organization

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

In the console, or from an emailed signed link.

a key for this connector

```
account {
  op: "keys.create", name: "jira-sm-agent",
  allowed_actions: ["jira_sm.*"], cap_calls: 2000,
  confirm_policy: "human_for_writes",
  approval_rules: [
    { match: "jira_sm.organization_users.delete", approver: "lead@example.com" },
    { match: "jira_sm.servicedesk_customers.delete", approver: "lead@example.com" },
    { match: "jira_sm.organizations.delete", approver: "lead@example.com" }
  ]
}
```

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

Cost

## What Jira Service Management costs on actionlake.

Every Jira Service Management action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Jira Service Management 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 74 Jira Service Management actions
- 46 actions page each page of a long list is one call
- 44 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 Service Management action.

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

**Customers 22**

- `jira_sm.customers.create` Create a customer write
- `jira_sm.customers.create_unchecked` Create a customer, skipping the permission check write
- `jira_sm.customers.revoke_portal_access` Revoke a customer's portal-only access destructive
- `jira_sm.organization_properties.delete` Delete an organization property destructive
- `jira_sm.organization_properties.get` Get an organization property read
- `jira_sm.organization_properties.list` List organization property keys read
- `jira_sm.organization_properties.update` Set an organization property write
- `jira_sm.organization_users.create` Add users to an organization write
- `jira_sm.organization_users.delete` Remove users from an organization destructive
- `jira_sm.organization_users.list` List users in an organization read
- `jira_sm.organizations.create` Create an organization write
- `jira_sm.organizations.delete` Delete an organization destructive
- `jira_sm.organizations.get` Get one organization read
- `jira_sm.organizations.list` List organizations read
- `jira_sm.servicedesk_customers.create` Add customers to a service desk write
- `jira_sm.servicedesk_customers.create_unchecked` Add customers to a service desk, skipping the permission check write
- `jira_sm.servicedesk_customers.delete` Remove customers from a service desk destructive
- `jira_sm.servicedesk_customers.invite` Invite a customer to a service desk write
- `jira_sm.servicedesk_customers.list` List customers on a service desk read
- `jira_sm.servicedesk_organizations.create` Attach an organization to a service desk write
- `jira_sm.servicedesk_organizations.delete` Detach an organization from a service desk destructive
- `jira_sm.servicedesk_organizations.list` List organizations on a service desk read

**ITSM 21**

- `jira_sm.comment_attachments.list` List attachments on a comment read
- `jira_sm.request_attachments.create` Attach files to a request write
- `jira_sm.request_attachments.get` Download an attachment read
- `jira_sm.request_attachments.get_thumbnail` Download an attachment thumbnail read
- `jira_sm.request_attachments.list` List attachments on a request read
- `jira_sm.request_comments.create` Comment on a request write
- `jira_sm.request_comments.get` Get one comment on a request read
- `jira_sm.request_comments.list` List comments on a request read
- `jira_sm.request_notifications.get` Get notification subscription on a request read
- `jira_sm.request_notifications.subscribe` Subscribe to a request's notifications write
- `jira_sm.request_notifications.unsubscribe` Unsubscribe from a request's notifications destructive
- `jira_sm.request_participants.create` Add participants to a request write
- `jira_sm.request_participants.delete` Remove participants from a request destructive
- `jira_sm.request_participants.list` List participants on a request read
- `jira_sm.request_status.list` List a request's status history read
- `jira_sm.request_transitions.create` Transition a request write
- `jira_sm.request_transitions.list` List available transitions on a request read
- `jira_sm.requests.create` Raise a customer request write
- `jira_sm.requests.get` Get one customer request read
- `jira_sm.requests.list` List customer requests read
- `jira_sm.requests.validate` Validate a customer request before raising it read

**Catalogue 12**

- `jira_sm.all_request_types.list` List request types across all service desks read
- `jira_sm.request_type_fields.list` List the fields a request type accepts read
- `jira_sm.request_type_groups.list` List request type groups read
- `jira_sm.request_type_permissions.query` Check request type permissions read
- `jira_sm.request_type_properties.delete` Delete a request type property destructive
- `jira_sm.request_type_properties.get` Get a request type property read
- `jira_sm.request_type_properties.list` List request type property keys read
- `jira_sm.request_type_properties.update` Set a request type property write
- `jira_sm.request_types.create` Create a request type write
- `jira_sm.request_types.delete` Delete a request type destructive
- `jira_sm.request_types.get` Get one request type read
- `jira_sm.request_types.list` List request types on a service desk read

**Approvals 3**

- `jira_sm.request_approvals.answer` Approve or decline a request write
- `jira_sm.request_approvals.get` Get one approval on a request read
- `jira_sm.request_approvals.list` List approvals on a request read

**Knowledge 3**

- `jira_sm.knowledge_articles.get` Get a knowledge base article read
- `jira_sm.knowledge_articles.search` Search knowledge base articles read
- `jira_sm.servicedesk_knowledge_articles.search` Search a service desk's knowledge base read

**Queues 3**

- `jira_sm.queue_issues.list` List issues in a queue read
- `jira_sm.queues.get` Get one queue read
- `jira_sm.queues.list` List queues in a service desk read

**Satisfaction 3**

- `jira_sm.request_feedback.create` Leave customer feedback on a request write
- `jira_sm.request_feedback.delete` Delete customer feedback on a request destructive
- `jira_sm.request_feedback.get` Get customer feedback on a request read

**Administration 2**

- `jira_sm.servicedesks.get` Get one service desk read
- `jira_sm.servicedesks.list` List service desks read

**Assets 2**

- `jira_sm.asset_workspaces.list` List Assets workspaces read
- `jira_sm.insight_workspaces.list` List Insight workspaces read

**Sla 2**

- `jira_sm.request_slas.get` Get one SLA metric on a request read
- `jira_sm.request_slas.list` List SLA metrics on a request read

**Platform 1**

- `jira_sm.info.get` Get Jira Service Management info read

Questions

## The Jira Service Management MCP server, answered.

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

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 74 Jira Service Management actions across customers, ITSM, catalogue and approvals, 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 Service Management from their own AI client. Use actionlake when you also want Jira Service Management 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 Service Management and another system.

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

Your own Jira Service Management OAuth app, registered with Jira Service Management (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Jira Service Management app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. actionlake finds cloud id, site url and the organisations, sites or workspaces the credential can reach for you when you connect. The free call account { op: "connections.requirements", service: "jira_sm" } lists exactly what to paste.

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

Only if its key allows it, and only with an explicit confirmation. 11 Jira Service Management actions are destructive, including remove users from an organization, remove customers from a service desk and delete an organization. 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 Service Management API limit?**

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

**What does a Jira Service Management action cost?**

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (46 Jira Service Management actions page). Cache hits, searches, dry runs and calls Jira Service Management 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 Service Management API does it cover?**

The Jira Service Management API 1 at api.atlassian.com/ex/jira, under your cloud id. It is built from Jira Service Management's documentation as read on 15 September 2026. 74 actions in 11 areas, each one in the signed service file (version 2.0.0).

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

Yes. ask joins Jira Service Management to ConnectWise PSA or NetSuite on the same customer and returns the answer rather than every row. Jira Service Management maps crm.company, which 227 other connectors also map.

**Does actionlake keep my Jira Service Management 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 Service Management 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 Service Management

Shares the most action names with

- [Freshdesk 24](https://actionlake.com/connectors/freshdesk)
- [Trengo 14](https://actionlake.com/connectors/trengo)
- [SysAid 12](https://actionlake.com/connectors/sysaid)
- [Zoho Desk 10](https://actionlake.com/connectors/zoho-desk)
- [Plain 9](https://actionlake.com/connectors/plain)
- [Tidio 6](https://actionlake.com/connectors/tidio)

Joins with, on shared entities

- [HaloPSA 5](https://actionlake.com/connectors/halopsa)
- [Odoo 4](https://actionlake.com/connectors/odoo)
- [Microsoft Dynamics 365 4](https://actionlake.com/connectors/microsoft-dynamics-365)
- [Insightly CRM 4](https://actionlake.com/connectors/insightly-crm)
- [Intercom 4](https://actionlake.com/connectors/intercom)
- [Zoho CRM 4](https://actionlake.com/connectors/zoho-crm)

Browse

- [All Service desk & support connectors](https://actionlake.com/connectors/category/service-desk-and-support)
- [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 Management service file, version 2.0.0.

## Give your agent Jira Service Management today.

[Connect Jira Service Management 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-service-management
More: https://actionlake.com/llms.txt