Skip to content
Custom Connectors

Connect Jira Service Management to Claude Code

Let Claude triage, comment, and transition tickets in Jira Service Management. From the terminal, inside the sessions where you already work.

How do you connect Jira Service Management to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Jira Service Management, you add a Jira Service Management MCP server: a small hosted service that exposes Jira Service Management's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Jira Service Management account. No API keys pasted into config files.

claude mcp add --transport http jira-service-management https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Jira Service Management once connected?

Full read-write Jira Service Management access lets Claude create and update requests, post internal or customer-facing comments, transition tickets through the workflow, set priority and assignee, and add work to the right queue once you approve. The triage that used to mean clicking through the portal happens where the ticket already lives.

  • Create a service request or incident from an email or chat summary
  • Post an internal note or a customer-facing reply on a ticket
  • Transition a request through its workflow, such as moving it to in progress or resolved
  • Set priority, assignee, and request type to triage an incoming queue
  • Link related issues or attach a problem to an incident
  • Search the queue for matching requests and propose batched updates

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Jira Service Management access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Jira Service Management API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Jira Service Management changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Jira Service Management connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Jira Service Management connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Jira Service Management account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Jira Service Management's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Jira Service Management?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Jira Service Management account it signs in with. Revoking access is one click in Jira Service Management.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.