Skip to main content
Glama
CzSadykov

jira-service-desk-mcp

by CzSadykov

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JIRA_URLYesJira instance URL
JIRA_IS_CLOUDNoAuto-detected from URL; set explicitly to override
JIRA_PASSWORDNoBasic auth password (not recommended)
JIRA_USERNAMENoEmail for Atlassian Cloud
JIRA_API_TOKENNoAPI token for Cloud auth
READ_ONLY_MODENotrue to disable all write operations
JIRA_SSL_VERIFYNotrue or falsetrue
JIRA_PERSONAL_TOKENNoRaw PAT or base64-encoded username:token
JIRA_PERSONAL_TOKEN_MODENoOverride for JIRA_PERSONAL_TOKEN: auto, pat, or basicauto

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_service_desk_infoA

Get information about the Jira Service Management application.

Returns version and other runtime details of the JSM instance. Use this to verify connectivity and check the installed JSM version.

list_service_desksA

List all service desks accessible to the current user.

Returns IDs, project keys and names of every service desk the authenticated user can see. Use this as a starting point to discover available service desks before querying request types, queues, etc.

get_service_deskA

Get details of a specific service desk by its numeric ID.

Use list_service_desks first to find the ID.

Args: service_desk_id: The numeric ID of the service desk (e.g. "1").

list_request_typesA

List all request types available in a service desk.

Each request type defines a form that customers fill in when raising a request (e.g. "Report a bug", "Request access"). Use this to discover which request types are available before creating a customer request.

Args: service_desk_id: The numeric ID of the service desk (e.g. "1").

get_request_typeA

Get details of a specific request type (name, description, help text).

Args: service_desk_id: The numeric ID of the service desk (e.g. "1"). request_type_id: The numeric ID of the request type (e.g. "10").

get_request_type_fieldsA

Get the fields required to create a request of this type.

Always call this before create_customer_request to learn which fields are required, their IDs, and valid values.

Args: service_desk_id: The numeric ID of the service desk (e.g. "1"). request_type_id: The numeric ID of the request type (e.g. "10").

create_customer_requestA

Create a new customer request (ticket) in a service desk.

Tip: call get_request_type_fields first to discover required field IDs and valid values for the chosen request type.

Args: service_desk_id: The numeric ID of the service desk (e.g. "1"). request_type_id: The numeric ID of the request type (e.g. "10"). values_json: JSON object with field values. Example: {"summary": "VPN not working", "description": "Cannot connect since morning"} raise_on_behalf_of: (Optional) Account ID (Cloud) or username (Server/DC) to raise the request on behalf of another user. request_participants: (Optional) Comma-separated account IDs or usernames to add as request participants.

get_customer_requestA

Get full details of a customer request including status, reporter, and field values.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID.

list_my_customer_requestsA

List customer requests raised by or involving the current user.

Returns requests where the authenticated user is the reporter or a participant. Useful to see "my open tickets" at a glance.

get_customer_request_statusA

Get the current status and status category of a customer request.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID.

add_request_commentA

Add a comment to a customer request.

Set public=true for customer-visible replies or public=false for internal agent notes that the customer cannot see.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID. body: The comment text (plain text or Jira wiki markup). public: true — visible to customer; false — internal agent note.

list_request_commentsA

List comments on a customer request with filtering by visibility.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID. public: Include public (customer-visible) comments. internal: Include internal (agent-only) comments. start: Pagination offset (0-based). limit: Maximum number of comments to return (default 50).

get_request_commentA

Get a single comment by its ID.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID. comment_id: The numeric comment ID.

create_customerA

Create a new customer account in the JSM instance (experimental API).

The customer will be able to raise requests through the customer portal.

Args: full_name: The customer's display name (e.g. "Jane Doe"). email: The customer's email address.

list_customersA

List customers who have access to a service desk.

Optionally filter by name or email substring.

Args: service_desk_id: The numeric ID of the service desk (e.g. "1"). query: (Optional) Filter string — matches against display name and email address. start: Pagination offset (0-based). limit: Maximum number of results (default 50).

add_customers_to_service_deskA

Grant one or more users access to a service desk as customers.

Provide usernames for Server/Data Center or account_ids for Cloud.

Args: service_desk_id: The numeric ID of the service desk. usernames: (Optional) Comma-separated usernames (Server/DC). account_ids: (Optional) Comma-separated Atlassian account IDs (Cloud).

remove_customers_from_service_deskA

Revoke customer access from a service desk.

Provide usernames for Server/Data Center or account_ids for Cloud.

Args: service_desk_id: The numeric ID of the service desk. usernames: (Optional) Comma-separated usernames (Server/DC). account_ids: (Optional) Comma-separated Atlassian account IDs (Cloud).

list_request_participantsA

List users who participate in (watch) a customer request.

Participants receive notifications about request updates.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID. start: Pagination offset (0-based). limit: Maximum number of results (default 50).

add_request_participantsB

Add participants to a customer request so they receive updates.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID. usernames: (Optional) Comma-separated usernames (Server/DC). account_ids: (Optional) Comma-separated Atlassian account IDs (Cloud).

remove_request_participantsA

Remove participants from a customer request.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID. usernames: (Optional) Comma-separated usernames (Server/DC). account_ids: (Optional) Comma-separated Atlassian account IDs (Cloud).

list_customer_transitionsA

List transitions available for a customer request in its current status.

Use the returned transition IDs with perform_transition.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID.

perform_transitionA

Perform a workflow transition on a customer request (e.g. resolve, close).

Call list_customer_transitions first to discover available transition IDs.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID. transition_id: The numeric transition ID. comment: (Optional) Comment to add along with the transition.

list_organizationsA

List organizations, optionally scoped to a specific service desk.

Organizations group customers for easier access management.

Args: service_desk_id: (Optional) Limit results to organizations linked to this service desk. start: Pagination offset (0-based). limit: Maximum number of results (default 50).

get_organizationB

Get details of a specific organization by its ID.

Args: organization_id: The numeric organization ID.

create_organizationB

Create a new customer organization.

Args: name: The display name for the new organization.

delete_organizationB

Permanently delete an organization and remove all its member associations.

Args: organization_id: The numeric organization ID.

add_organization_to_service_deskB

Link an organization to a service desk so its members can raise requests.

Args: service_desk_id: The numeric ID of the service desk. organization_id: The numeric organization ID.

remove_organization_from_service_deskB

Unlink an organization from a service desk.

Args: service_desk_id: The numeric ID of the service desk. organization_id: The numeric organization ID.

list_users_in_organizationA

List users who belong to an organization.

Args: organization_id: The numeric organization ID. start: Pagination offset (0-based). limit: Maximum number of results (default 50).

add_users_to_organizationA

Add users to an organization.

Provide usernames for Server/Data Center or account_ids for Cloud.

Args: organization_id: The numeric organization ID. usernames: (Optional) Comma-separated usernames (Server/DC). account_ids: (Optional) Comma-separated Atlassian account IDs (Cloud).

remove_users_from_organizationA

Remove users from an organization.

Provide usernames for Server/Data Center or account_ids for Cloud.

Args: organization_id: The numeric organization ID. usernames: (Optional) Comma-separated usernames (Server/DC). account_ids: (Optional) Comma-separated Atlassian account IDs (Cloud).

list_queuesA

List agent queues defined in a service desk.

Queues are saved JQL filters that agents use to triage requests (e.g. "All open", "Unassigned", "SLA breached").

Args: service_desk_id: The numeric ID of the service desk (e.g. "1"). include_count: Set true to include the number of issues per queue. start: Pagination offset (0-based). limit: Maximum number of results (default 50).

list_issues_in_queueA

List customer requests currently sitting in a specific queue.

Use list_queues first to discover queue IDs.

Args: service_desk_id: The numeric ID of the service desk. queue_id: The numeric queue ID. start: Pagination offset (0-based). limit: Maximum number of results (default 50).

get_request_slaA

Get SLA (Service Level Agreement) metrics for a customer request.

Returns remaining time, breach status, and goal durations for every SLA metric configured on the request.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID. start: Pagination offset (0-based). limit: Maximum number of results (default 50).

get_request_sla_by_idA

Get a specific SLA metric by its ID for a customer request.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID. sla_id: The SLA metric ID.

list_approvalsA

List pending and completed approvals for a customer request.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID. start: Pagination offset (0-based). limit: Maximum number of results (default 50).

get_approvalA

Get details of a specific approval including approver decisions.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID. approval_id: The numeric approval ID.

answer_approvalA

Approve or decline an approval request.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID. approval_id: The numeric approval ID. decision: "approve" or "decline".

upload_temporary_attachmentA

Upload a file as a temporary attachment.

The returned temporary attachment ID must then be passed to attach_file_to_request to permanently attach it to a request.

Args: service_desk_id: The numeric ID of the service desk. filename: Absolute path to the file on the server filesystem.

attach_file_to_requestA

Attach a previously uploaded temporary file to a customer request.

Call upload_temporary_attachment first to obtain the temporary ID.

Args: issue_id_or_key: The issue key (e.g. "X000") or numeric issue ID. temp_attachment_id: The temporary attachment ID returned by upload_temporary_attachment. public: true — visible to customers; false — internal only. comment: (Optional) Comment to accompany the attachment.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CzSadykov/jira-service-desk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server