Jira Service Management

Live

OAUTH 2.0

SERVICE DESK

Customer Support

Jira Service Management gives agents authenticated access to your service desk: triage requests, answer approvals, and keep queues moving with per-user OAuth.

  • Per-user credentials: each call uses the actual user's token, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
Jira Service Management
agent · Acme Q3
Run
What is sitting in the Unassigned queue on the IT service desk right now?
S
jiraservicemanagement_queue_issues_list
88ms
Service desk agent
12 requests in Unassigned. Oldest is HELP-231, a VPN outage opened 9:04 UTC. 3 are hardware, 7 access, 2 how-to. 2 approvals pending on ITSM-88.
Sources: 12 requests, queue Unassigned, IT service desk
jiraservicemanagement
12 requests
18:29
Message Claude...

Tools your support agent reaches for on Jira Service Management, scoped per user.

CALL ANY TOOL
Run the service desk end to end: list and create customer requests, comment, watch queues, and answer approvals.
jiraservicemanagement_approval_answer
Approval answer
Approve or decline an approval on a customer request. The approval is assumed to be owned by the user making the call. Requires the user to be assigned to the approval request.
Parameters
Name
Type
Required
Description
approvalId
integer
Required
The ID of the approval to be updated.
decision
string
Required
Response to the approval request. Must be either 'approve' or 'decline'.
issueIdOrKey
string
Required
The ID or key of the customer request to be updated.
jiraservicemanagement_approval_get
Get approval
jiraservicemanagement_approvals_list
List approvals
jiraservicemanagement_assets_workspaces_list
List assets workspaces
jiraservicemanagement_attachment_thumbnail_get
Get attachment thumbnail
jiraservicemanagement_comment_with_attachment_create
Create comment with attachment
jiraservicemanagement_customer_portal_access_revoke
Customer portal access revoke
jiraservicemanagement_customer_request_create
Create customer request
jiraservicemanagement_customer_requests_list
List customer requests
jiraservicemanagement_feedback_delete
Delete feedback
jiraservicemanagement_feedback_get
Get feedback
jiraservicemanagement_insight_workspaces_list
List insight workspaces
jiraservicemanagement_organization_get
Get organization
jiraservicemanagement_organization_property_delete
Delete organization property
jiraservicemanagement_organization_property_set
Set organization property
jiraservicemanagement_organization_users_add
Add organization users
jiraservicemanagement_organization_users_remove
Remove organization users
jiraservicemanagement_organizations_list
List organizations
jiraservicemanagement_request_attachment_content_get
Get request attachment content
jiraservicemanagement_request_attachments_list
List request attachments
jiraservicemanagement_request_comment_create
Create request comment
jiraservicemanagement_request_participants_add
Add request participants
jiraservicemanagement_request_participants_list
List request participants
jiraservicemanagement_request_subscribe
Request subscribe
jiraservicemanagement_request_subscription_status_get
Get request subscription status
jiraservicemanagement_request_type_property_get
Get request type property
jiraservicemanagement_request_type_property_keys_list
List request type property keys
jiraservicemanagement_service_desk_articles_list
List service desk articles
jiraservicemanagement_service_desk_customers_remove
Remove service desk customers
jiraservicemanagement_service_desk_request_types_list
List service desk request types

For more tools, view docs.

Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Jira Service Management tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["jiraservicemanagement"], toolNames: [
    "jiraservicemanagement_customer_requests_list",
    "jiraservicemanagement_customer_request_get",
    "jiraservicemanagement_request_comment_create"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "What is sitting in the Unassigned queue?" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["jiraservicemanagement"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "List my open customer requests." }],
  tools,
});

// Execute the tool call with the user's vaulted Jira Service Management credential
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["jiraservicemanagement"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Which requests are pending my approval?" }],
  tools,
});

// Tool call runs with the user's vaulted Jira Service Management credential
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["jiraservicemanagement"] }, pageSize: 100,
});

const agent = new Agent({
  name: "jsm_service_desk_agent",
  model: "gemini-2.5-pro",
  instruction: "Triage service desk requests for the signed-in user.",
  tools,
});

await agent.run("Which queues have the most open requests?");
Try these prompts
Copy any prompt into your agent. Each maps directly to a Jira Service Management tool. Click to copy, paste into your agent, done.
Triage and queues
Copy the prompt
Copied
Which queues in the IT service desk have the most open requests?
Copy the prompt
Copied
Show the requests sitting in the Unassigned queue right now.
Copy the prompt
Copied
Get HELP-231 with its SLA and status history.
Requests and comments
Copy the prompt
Copied
Create a request for a broken laptop in the IT service desk.
Copy the prompt
Copied
Add a public comment to HELP-231 telling the customer a fix ships today.
Copy the prompt
Copied
List my open requests, latest activity first.
Approvals
Copy the prompt
Copied
Which requests are pending my approval?
Copy the prompt
Copied
List the approvals on ITSM-88 and who still needs to sign off.
Copy the prompt
Copied
Approve the software license request on ITSM-88.
SEE HOW AUTH WORKS
Your users connect once. Their Jira Service Management credentials stay vaulted, every call is scope-checked, and every action is logged.
1
Authorize
Your user connects
Jira Service Management
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Jira Service Management
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Jira Service Management
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Jira Service Management
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other support connectors.
Support and Ops Teams
Support triage agent
Fetches new Zendesk tickets, classifies them by type and urgency, searches the Notion knowledge base for an answer, and routes what it cannot resolve to Slack. Every call runs on the support agent's own delegated OAuth.
Support and Ops Teams
Support ticket automation agent
Fetches new Zendesk tickets, drafts a reply from Notion knowledge base articles, digests what it cannot answer to Slack, and archives the rest, acting as the support agent rather than a shared API key.
Support and Ops Teams
Freshdesk CSAT agent
Watches Freshdesk for resolved tickets, emails each requester a CSAT survey from Gmail, and writes the score and the verbatim back onto the ticket, every call on the support rep's own delegated OAuth.
Engineering Teams
Slack triage
Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.
Test other agents
See the same per-user auth pattern across other support connectors.
SUPPORT
Support triage agent
Classify new Zendesk tickets, search the Notion knowledge base for an answer, and route what it cannot resolve to Slack.
SUPPORT
Support ticket automation (Google ADK)
Fetch, annotate, and archive Zendesk tickets with Notion context, digesting anything it cannot answer to Slack.
SUPPORT
Freshdesk CSAT follow-up agent
Spot resolved Freshdesk tickets, email the CSAT survey from Gmail, and write the score back onto the ticket.
ENGINEERING
Slack triage agent
Classify new Slack messages as bugs or support requests, file the GitHub issue or Zendesk ticket, and reply in the thread.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared Jira Service Management token looks fine in a demo. In production every comment and approval looks like one service account, and you cannot tell who resolved a request or signed off a change. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Jira Service Management today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Jira Service Management as the user or through a shared key?
As the user. Scalekit resolves the credential of the person who triggered the agent at request time, so every comment, request, and approval decision in your audit trail is attributed to a real user, not a shared service account.
Where is the Jira Service Management token stored?
In an AES-256 encrypted vault with per-tenant namespacing. Tokens are resolved at request time, never enter LLM context, refresh automatically, and can be revoked from one dashboard.
Can I limit what the agent does in Jira Service Management?
Yes. Filter by tool name in listScopedTools to expose only what you want, for example read-only triage with queues and requests but no approval_answer or request creation. Scalekit also enforces scope checks before every API call.
What happens when a user revokes access?
The credential is invalidated at the next tool call. The call fails closed, other users' connections are unaffected, and the revocation is logged in the audit chain.
Can the agent post internal notes that customers should not see?
Only if the acting user can. request_comment_create takes a public flag, and Jira Service Management enforces that customers can only post public comments. Because Scalekit resolves the caller's own credential, an agent acting for a customer can never write internal notes.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""jiraservicemanagement"": {
""url"": ""https://mcp.scalekit.com/jiraservicemanagement"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.jiraservicemanagement]
url = ""https://mcp.scalekit.com/jiraservicemanagement""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""jiraservicemanagement"": {
""url"": ""https://mcp.scalekit.com/jiraservicemanagement"",
""type"": ""http""
}
}
}