Jira Service Management MCP integration
Service desks, customer requests, request comments, transitions, organizations, and customers
Sign in, add Jira Service Management in Apps, then choose the account your AI can use.
Tools
| Name | Description |
|---|---|
validate_connectionValidate Jira Service Management credentials by listing service desks. | Validate Jira Service Management credentials by listing service desks. |
list_service_desksList Jira Service Management service desks. | List Jira Service Management service desks. |
get_service_deskGet a service desk by ID or supported project identifier. | Get a service desk by ID or supported project identifier. |
list_request_typesList request types, optionally scoped to one service desk. | List request types, optionally scoped to one service desk. |
get_request_type_fieldsGet fields required to create a customer request for a request type. | Get fields required to create a customer request for a request type. |
list_customer_requestsList Jira Service Management customer requests with portal filters. | List Jira Service Management customer requests with portal filters. |
create_customer_requestCreate a Jira Service Management customer request using service desk and request type IDs. | Create a Jira Service Management customer request using service desk and request type IDs. |
get_customer_requestGet a customer request by issue key or ID. | Get a customer request by issue key or ID. |
list_request_commentsList comments on a customer request. | List comments on a customer request. |
add_request_commentAdd a public customer-visible or internal/private comment to a customer request. | Add a public customer-visible or internal/private comment to a customer request. |
list_customer_transitionsList customer-visible transitions available for a request. | List customer-visible transitions available for a request. |
perform_customer_transitionPerform a customer-visible request transition by exact transition ID. Requires exact transition ID confirmation. | Perform a customer-visible request transition by exact transition ID. Requires exact transition ID confirmation. |
list_organizationsList Jira Service Management organizations. | List Jira Service Management organizations. |
create_organizationCreate a Jira Service Management organization. | Create a Jira Service Management organization. |
create_customerCreate a Jira Service Management customer. | Create a Jira Service Management customer. |
Triggers
| Name | Description |
|---|---|
new_or_updated_customer_requestPoll Jira Service Management customer requests and emit requests whose created/status timestamps changed since the previous poll. | Poll Jira Service Management customer requests and emit requests whose created/status timestamps changed since the previous poll. |
Quick Start
import { WeavzClient } from '@weavz-io/sdk'
const weavz = new WeavzClient({ apiKey: 'wvz_...' })
const result = await weavz.actions.execute('jira-service-management', 'validate_connection', {
workspaceId: '550e8400-e29b-41d4-a716-446655440000',
integrationAlias: 'jira-service-management',
input: { /* ... */ },
})Related Integrations
Works well with
Frequently Asked Questions
Is there a Jira Service Management MCP server through Weavz?
Yes. Add the Jira Service Management integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 15 Jira Service Management actions.
What can an AI agent do with Jira Service Management?
Available actions include Validate Connection, List Service Desks, Get Service Desk, List Request Types, Get Request Type Fields, and more. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.
How do I connect Jira Service Management to Claude or ChatGPT?
Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add Jira Service Management, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.
Can I use Jira Service Management through an API or SDK?
Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.
What authentication does Jira Service Management require?
The catalog lists custom credentials for Jira Service Management. Use Hosted Connect to authorize the intended account. Required permissions, provider app access and available connection methods depend on the integration.
How do I review sensitive Jira Service Management actions?
Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.
What limits or costs apply to Jira Service Management?
Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.
What Jira Service Management triggers are available?
The catalog lists 1 triggers, including New or Updated Customer Request. Configure the trigger and your event handler before using incoming events to start work.
Connect Jira Service Management in minutes
Get 20,000 free action executions every month. No credit card required.