Skip to main content
Jira

Overview

Tool catalogue

Jira tools are surfaced through the MCP runtime (POST /api/v1/mcp/:serverId) and the HTTP chat endpoint (POST /api/v1/mcp/:serverId/chat). In router mode the model uses SEARCH_TOOLS to discover the right slug at runtime. The catalogue covers: Discover the full list at runtime:
The model will call SEARCH_TOOLS({query: "transition assign issue"}) and stream the matched slugs back.

Connect setup

Jira uses Atlassian OAuth 2.0 (3LO) with PKCE against an app registered in the Atlassian developer console.
1

Register an Atlassian OAuth 2.0 (3LO) app

Go to developer.atlassian.com/console/myappsCreateOAuth 2.0 integration. Under Authorization, add the callback URL:
Copy the Client ID and Secret shown under Settings.
2

Enable Jira API permissions

On the app’s Permissions tab, add the Jira platform REST API and the Jira Software API, then grant these scopes:
  • read:jira-work
  • write:jira-work
  • read:jira-user
  • manage:jira-project
  • manage:jira-configuration
  • manage:jira-webhook
  • offline_access — required to receive refresh tokens
3

Connect via the widget

The end user opens the Connect widget, picks Jira, and is sent through Atlassian’s consent screen.

Usage

The agent loop picks JIRA_CREATE_ISSUE, executes it against the connected user’s site, and streams the result back as SSE.

Direct MCP JSON-RPC (Claude Desktop / Cursor / custom MCP clients)

Once connected, MCP clients can invoke any of the 97 tools by slug via the standard tools/call JSON-RPC method.