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 See 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

74actionsin one signed file
44readlook, never change
19writecreate and update
11wait for a yesdestructive, confirmed first

Set up

Connect Jira Service Management in three steps.

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
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_tokenAccess token from one sign-in with your own OAuth app
- refresh_tokenRefresh token from the same sign-in; the access token is renewed from it
- client_idAtlassian OAuth 2.0 (3LO) client id
- client_secretAtlassian 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
```

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 callcheck { 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_tokenrefresh_tokenclient_idclient_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 1api.atlassian.com
Built from: Jira Service Management's documentation, read 15 September 2026developer.atlassian.com
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.

44readlook, never change
19writecreate and update
11destructivewait for a confirmation

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
ITSM
21
13 read · 6 write · 2 destructive
List customer requests · List comments on a request · Raise a customer request · Comment on a request
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
Approvals
3
2 read · 1 write · 0 destructive
List approvals on a request · Get one approval on a request · Approve or decline a request
Knowledge
3
3 read · 0 write · 0 destructive
Search knowledge base articles · Search a service desk's knowledge base · Get a knowledge base article
Queues
3
3 read · 0 write · 0 destructive
List issues in a queue · List queues in a service desk · Get one queue
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
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?

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, 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.

Readread
Which Jira Service Management tickets have been open the longest? Show me the ten oldest with their status.
callsjira_sm.requests.list
Planwrite
Create an organization and add it to a service desk in Jira Service Management. Ask me before anything is sent or changed.
callsjira_sm.servicedesks.getjira_sm.organizations.listjira_sm.organizations.createjira_sm.servicedesk_customers.invitejira_sm.organization_users.create+1 more
Planwrite
Validate and raise a request on behalf of a customer in Jira Service Management.
callsjira_sm.request_types.getjira_sm.requests.validatejira_sm.requests.createjira_sm.request_participants.createjira_sm.request_comments.create+1 more
Writewrite
Raise a customer request in Jira Service Management. Show me exactly what you will send before you save it.
callsjira_sm.requests.create
Across systemsread
Which Jira Service Management companies have invoices in ConnectWise PSA, and how many each?
callsjira_sm.organizations.listconnectwise_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
Which Jira Service Management companies have invoices in NetSuite, and how many each?
jira_sm.organizations.list + netsuite.views.invoices, on crm.company · NetSuite

Also mapped by other connectorscrm.company 227crm.contact 192service.ticket 62knowledge.article 22service.queue 14service.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.

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
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
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 decidesRecord '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
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 decidesCreate 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
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
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 decidesTransition 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 organizationjira_sm.organization_users.delete
Remove customers from a service deskjira_sm.servicedesk_customers.delete
Delete an organizationjira_sm.organizations.delete
Detach an organization from a service deskjira_sm.servicedesk_organizations.delete
Revoke a customer's portal-only accessjira_sm.customers.revoke_portal_access
Delete a request typejira_sm.request_types.delete
Remove participants from a requestjira_sm.request_participants.delete
Unsubscribe from a request's notificationsjira_sm.request_notifications.unsubscribe
Delete customer feedback on a requestjira_sm.request_feedback.delete
Delete an organization propertyjira_sm.organization_properties.delete
Delete a request type propertyjira_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.

dojira_sm.organization_users.deleteconfirm_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: "[email protected]" },    { match: "jira_sm.servicedesk_customers.delete", approver: "[email protected]" },    { match: "jira_sm.organizations.delete", approver: "[email protected]" }  ]}

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.

1upstream call per actionall 74 Jira Service Management actions
46actions pageeach page of a long list is one call
44reads can be cacheda cache hit costs nothing
100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Jira Service Management action.

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

Customers22

jira_sm.customers.createCreate a customerwrite
jira_sm.customers.create_uncheckedCreate a customer, skipping the permission checkwrite
jira_sm.customers.revoke_portal_accessRevoke a customer's portal-only accessdestructive
jira_sm.organization_properties.deleteDelete an organization propertydestructive
jira_sm.organization_properties.getGet an organization propertyread
jira_sm.organization_properties.listList organization property keysread
jira_sm.organization_properties.updateSet an organization propertywrite
jira_sm.organization_users.createAdd users to an organizationwrite
jira_sm.organization_users.deleteRemove users from an organizationdestructive
jira_sm.organization_users.listList users in an organizationread
jira_sm.organizations.createCreate an organizationwrite
jira_sm.organizations.deleteDelete an organizationdestructive
jira_sm.organizations.getGet one organizationread
jira_sm.organizations.listList organizationsread
jira_sm.servicedesk_customers.createAdd customers to a service deskwrite
jira_sm.servicedesk_customers.create_uncheckedAdd customers to a service desk, skipping the permission checkwrite
jira_sm.servicedesk_customers.deleteRemove customers from a service deskdestructive
jira_sm.servicedesk_customers.inviteInvite a customer to a service deskwrite
jira_sm.servicedesk_customers.listList customers on a service deskread
jira_sm.servicedesk_organizations.createAttach an organization to a service deskwrite
jira_sm.servicedesk_organizations.deleteDetach an organization from a service deskdestructive
jira_sm.servicedesk_organizations.listList organizations on a service deskread

ITSM21

jira_sm.comment_attachments.listList attachments on a commentread
jira_sm.request_attachments.createAttach files to a requestwrite
jira_sm.request_attachments.getDownload an attachmentread
jira_sm.request_attachments.get_thumbnailDownload an attachment thumbnailread
jira_sm.request_attachments.listList attachments on a requestread
jira_sm.request_comments.createComment on a requestwrite
jira_sm.request_comments.getGet one comment on a requestread
jira_sm.request_comments.listList comments on a requestread
jira_sm.request_notifications.getGet notification subscription on a requestread
jira_sm.request_notifications.subscribeSubscribe to a request's notificationswrite
jira_sm.request_notifications.unsubscribeUnsubscribe from a request's notificationsdestructive
jira_sm.request_participants.createAdd participants to a requestwrite
jira_sm.request_participants.deleteRemove participants from a requestdestructive
jira_sm.request_participants.listList participants on a requestread
jira_sm.request_status.listList a request's status historyread
jira_sm.request_transitions.createTransition a requestwrite
jira_sm.request_transitions.listList available transitions on a requestread
jira_sm.requests.createRaise a customer requestwrite
jira_sm.requests.getGet one customer requestread
jira_sm.requests.listList customer requestsread
jira_sm.requests.validateValidate a customer request before raising itread

Catalogue12

jira_sm.all_request_types.listList request types across all service desksread
jira_sm.request_type_fields.listList the fields a request type acceptsread
jira_sm.request_type_groups.listList request type groupsread
jira_sm.request_type_permissions.queryCheck request type permissionsread
jira_sm.request_type_properties.deleteDelete a request type propertydestructive
jira_sm.request_type_properties.getGet a request type propertyread
jira_sm.request_type_properties.listList request type property keysread
jira_sm.request_type_properties.updateSet a request type propertywrite
jira_sm.request_types.createCreate a request typewrite
jira_sm.request_types.deleteDelete a request typedestructive
jira_sm.request_types.getGet one request typeread
jira_sm.request_types.listList request types on a service deskread

Approvals3

jira_sm.request_approvals.answerApprove or decline a requestwrite
jira_sm.request_approvals.getGet one approval on a requestread
jira_sm.request_approvals.listList approvals on a requestread

Knowledge3

jira_sm.knowledge_articles.getGet a knowledge base articleread
jira_sm.knowledge_articles.searchSearch knowledge base articlesread
jira_sm.servicedesk_knowledge_articles.searchSearch a service desk's knowledge baseread

Queues3

jira_sm.queue_issues.listList issues in a queueread
jira_sm.queues.getGet one queueread
jira_sm.queues.listList queues in a service deskread

Satisfaction3

jira_sm.request_feedback.createLeave customer feedback on a requestwrite
jira_sm.request_feedback.deleteDelete customer feedback on a requestdestructive
jira_sm.request_feedback.getGet customer feedback on a requestread

Administration2

jira_sm.servicedesks.getGet one service deskread
jira_sm.servicedesks.listList service desksread

Assets2

jira_sm.asset_workspaces.listList Assets workspacesread
jira_sm.insight_workspaces.listList Insight workspacesread

Sla2

jira_sm.request_slas.getGet one SLA metric on a requestread
jira_sm.request_slas.listList SLA metrics on a requestread

Platform1

jira_sm.info.getGet Jira Service Management inforead

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.

Give your agent Jira Service Management today.

Connect Jira Service Management free See pricing

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

Jira Service Management MCP server for AI agents.

Connect Jira Service Management in three steps.

Add actionlake to Claude.

Connect Jira Service Management.

Make the first call. Check before a write.

What an AI agent can do in Jira Service Management.

Customers

ITSM

Catalogue

Approvals

Knowledge

Queues

Satisfaction

Administration

Atlassian's MCP server, or actionlake?

The Jira Service Management API, shaped for agents.

Prompts to paste into Claude.

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

Ready-made plans for Jira Service Management.

Audit the request type catalogue of a service desk

Sweep a queue for SLA risk and comment on the worst

Answer a pending request approval after a human signs off

Create an organization and add it to a service desk

Validate and raise a request on behalf of a customer

Answer a request from the knowledge base and transition it

Destructive actions wait for a yes.

What Jira Service Management costs on actionlake.

Every Jira Service Management action.

The Jira Service Management MCP server, answered.

More connectors like Jira Service Management

Give your agent Jira Service Management today.