Skip to main content
The Jira Service Management MCP server lets you govern access to Jira Service Management — service desks, requests, queues, customers, organizations, knowledge base content, and SLAs — as tools your AI clients can call through C1. Jira Service Management supports two ways to authenticate, and you choose one when you register the server:
  • Per-user OAuth (recommended). Each person authorizes with their own Atlassian account, so every tool call runs under that user’s identity and permissions.
  • Atlassian API token (scoped). A single API token, created for a person or a service account, authenticates everyone as one shared identity. C1 sends it as a Bearer token.
For a deeper comparison of shared versus per-user credentials, see Configure authentication.

How C1 connects to Jira Service Management

C1 hosts the Jira Service Management MCP server, so your users’ AI clients only ever see MCP tools — they never call Jira Service Management directly. When an AI client calls one of these tools, C1 makes the matching request to the Jira Service Management API using the credentials you configure here, then returns the result to the AI client. The credentials you set up below are what C1 uses to call Jira Service Management on your users’ behalf.

Before you begin

  • AI access management must be enabled for your tenant. See Enable AI access management.
  • For per-user OAuth, an Atlassian account that can create an OAuth 2.0 integration. See Atlassian’s OAuth 2.0 (3LO) apps guide.
  • For an API token, an Atlassian account or service account that can create API tokens with scopes, with access to Jira Service Management.
  • Your Atlassian site’s Cloud ID. To find it, open https://your-site.atlassian.net/_edge/tenant_info in a browser, replacing your-site with your site’s name, and copy the cloudId value.
If you don’t see Jira Service Management in your MCP server catalog, contact the C1 support team to enable it for your tenant.

Option 1: Create an Atlassian OAuth 2.0 integration

With per-user OAuth, you register one Atlassian OAuth 2.0 (3LO) integration and each user authorizes individually. This keeps every action attributable to the user who took it, with only the access that user already has in Jira Service Management.
1
Sign in to the Atlassian Developer Console with your Atlassian account. For the full walkthrough, see Atlassian’s OAuth 2.0 (3LO) apps guide.
2
Select Create > OAuth 2.0 integration, enter a recognizable name such as C1, and if prompted for an Access type, choose Resource-level. Then select Create.
3
Open the Permissions tab. Add and configure both Jira API and Jira Service Management API, then add the scopes from Jira Service Management scopes below — the default scopes, plus any optional write or admin scopes you need. Each scope lives under the API shown in the table.
4
Open the Authorization tab. Next to OAuth 2.0 (3LO), select Configure and set the Callback URL exactly to whichever matches your C1 tenant’s domain:
  • Default instance: https://accounts.conductor.one/auth/callback
  • EU data residency instance: https://accounts.c1eu.ai/auth/callback
Select Save changes.
5
Open the Settings tab. Under Authentication details, copy the Client ID and the Secret. Reveal the secret to copy it, and treat it as a high-value credential.

Jira Service Management scopes

C1 requests the default scopes automatically. To enable write or admin tools, add the optional scopes below in the Developer Console (Permissions > the API listed for each scope > Configure) and in C1’s scopes field when configuring authentication. Grant only what you need. The scopes span two APIs in the Developer Console, so add both Jira API and Jira Service Management API. Default scopes (enable all of them) read requests, customers, knowledge base content, and user profiles, plus offline_access for token refresh. manage:servicedesk-customer is the only scope Atlassian offers for customer and organization access, so it also authorizes the customer and organization write tools:
Every default scope must be enabled on your integration. If C1 requests a scope the integration doesn’t have, authorization fails and Atlassian shows only “Something went wrong.”
Optional scopes enable the write and admin tools. Add only the ones you need:
Atlassian recommends keeping an app under 50 scopes. Scope changes take effect the next time a user connects — adding an optional scope after users have connected requires each user to reconnect their Atlassian account.

Register the Jira Service Management MCP server with OAuth

With your integration ready, register the server and provide your credentials.
1
Follow Register an MCP server and select Jira Service Management from the catalog.
2
Enter your Atlassian site’s Cloud ID.
3
When you configure authentication, choose per-user OAuth and enter your integration’s client ID and client secret.
4
Save your changes. The first time a user calls a Jira Service Management tool from their AI client, they’re prompted to connect their Atlassian account.

Option 2: Set up an Atlassian API token

An Atlassian API token authenticates every user as one shared identity: the Atlassian account that owns the token. Use it when per-user attribution in Jira Service Management isn’t required, or when you want a service account to own the connection. C1 sends the token as a Bearer token.

Create an API token

Create an API token with scopes, either for a person or for a service account, so C1 can authenticate to the Jira Service Management API. The token’s scopes are fixed when you create it, so select every scope below. To change them later, create a new token.
1
Open Atlassian API tokens and select Create API token with scopes. For details, see Atlassian’s Manage API tokens for your Atlassian account documentation.
2
Enter a name such as C1.
3
Choose an expiration between 1 and 365 days, then select Next.
4
Select Jira as the app, then select Next. Atlassian lists the Jira Service Management scopes under the Jira app, so there is no separate app to choose.
5
Select these scopes, then select Next:
  • read:servicedesk-request
  • manage:servicedesk-customer
  • read:jira-user
  • read:jira-work
  • read:knowledgebase:jira-service-management
  • read:requesttype:jira-service-management
  • read:request.attachment:jira-service-management
  • read:request.comment:jira-service-management
  • read:user:jira
To enable write or admin tools, also select the matching optional scopes from Jira Service Management scopes.
6
Review the token and select Create.
7
Copy the token. Atlassian shows it only once.
To own the token with a service account instead of a person, create it from the service account in Atlassian Administration under Directory > Service accounts > Create credentials > API token, and select the same scopes. Give the service account access to Jira Service Management and to the service desks C1 should read. For the full procedure, see Atlassian’s Manage API tokens for service accounts documentation. A dedicated service account keeps activity attributable to C1 rather than a person. The token expires on the date you chose, so rotate it before then.

Register the Jira Service Management MCP server with an API token

With your API token ready, register the server and provide it.
1
Follow Register an MCP server and select Jira Service Management from the catalog.
2
Enter your Atlassian site’s Cloud ID.
3
When you configure authentication, choose Bearer token and paste your API token.
4
Save your changes. C1 runs tool discovery against Jira Service Management.

How Jira Service Management credentials are shared

With per-user OAuth, each user authorizes with their own Atlassian account, so tool calls run under that user’s Jira Service Management identity and inherit only the access they already have. Atlassian attributes each action to the individual user. With an API token, every user’s tool calls use the one credential you provided, so Jira Service Management sees a single shared identity: the account that owns the token. C1 still attributes each call to the individual user in the AI tool usage audit log. For how shared and per-user credentials work across MCP servers, see Configure authentication.

Discover and govern tools

After you register the server, C1 runs tool discovery against Jira Service Management. Discovered tools appear on the server’s Tools tab. Each tool starts as either Pending review or automatically Approved, depending on the option chosen when the server was set up or your tenant’s default tool settings in AI > MCPs > Settings. See Require tool approval and Default tool classification. Before anyone can call a Jira Service Management tool, it must be approved, added to a toolset, and bound to an access profile. Continue to Govern tools and toolsets to set this up.
Tool discovery runs even if your credentials are incorrect, so seeing discovered tools doesn’t confirm that authentication is working. You confirm your Jira Service Management credentials when an approved user successfully calls a Jira Service Management tool from their AI client.

Manage your Jira Service Management credentials

  • Rotate the OAuth client secret in the Atlassian Developer Console under your integration’s Settings tab, then update the secret on the server’s authentication settings in C1.
  • Rotate an API token by creating a new token in Atlassian with the same scopes and updating it in C1, then revoking the old one. Create the new token before the current one expires.
  • Adjust access by editing the integration’s scopes on the Permissions tab in the Atlassian Developer Console. For an API token, create a replacement token with different scopes.