Jira connector for AI agents

Tools your Jira agent reaches for, scoped per user.

CALL ANY TOOL

Search issues with JQL, manage sprints, update status, and log work. Same toolkit, every framework, no auth plumbing.

jira_issues_search

Search issues

Search Jira issues using JQL (Jira Query Language) with pagination.

Parameters

Name

Type

Required

Description

jql

string

Required

JQL query string (e.g. project=PLAT AND status=Open AND type=Bug)

max_results

integer

Optional

Max results to return (default 50)

start_at

integer

Optional

Pagination offset

fields

array

Optional

Fields to include in response

jira_issue_get

Get issue

jira_issue_create

Create issue

jira_issue_update

Update issue

jira_issue_transition

Transition issue

jira_projects_list

List projects

Build your Agent

Drop the toolkit in, point it at the user, and your agent can search Jira issues with JQL, create tickets, and transition status from the first run.

Copied

import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["jira"], toolNames: ["jira_issues_search", "jira_issue_get", "jira_issue_create"] },
  pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  schema: t.tool.definition.input_schema,
  func: async (args) => sk.tools.executeTool({
    toolName: t.tool.definition.name, identifier: "user_123", toolInput: args,
  }),
}));

const agent = createReactAgent({ llm, tools: lcTools });

Copied

import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["jira"], toolNames: ["jira_issues_search", "jira_issue_get", "jira_issue_create"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  type: "function",
  function: {
    name: t.tool.definition.name,
    description: t.tool.definition.description,
    parameters: t.tool.definition.input_schema,
  },
}));

const resp = await openai.responses.create({
  model: "gpt-4o", input: prompt, tools: llmTools,
});

import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["jira"], toolNames: ["jira_issues_search", "jira_issue_get", "jira_issue_create"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
  model: "claude-sonnet-4-6", max_tokens: 1024,
  tools: llmTools,
  messages: [{ role: "user", content: prompt }],
});

Copied

import { Agent } from "@google/adk/agents";
import {
  MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
  connectionParams: new StreamableHTTPConnectionParams({
    url: "https://mcp.scalekit.com/jira",
    headers: { Authorization: `Bearer ${userScopedToken}` },
  }),
});

const agent = new Agent({
  name: "agent", model: "gemini-2.0-flash",
  tools: await toolset.getTools(),
});

Try these prompts

Paste any prompt into your agent to start managing Jira workflows.

Search & recall

Copy the prompt

Copied

List all open bugs in [project] assigned to me.

Copy the prompt

Copied

Run a JQL query: project=PLAT AND sprint in openSprints() AND type=Bug.

Copy the prompt

Copied

What issues are blocking the current sprint?

Copy the prompt

Copied

Find all stories in epic [epic name] with status In Progress.

Action & creation

Copy the prompt

Copied

Create a bug in [project]: [title] — [description], priority High.

Copy the prompt

Copied

Move issue [PROJ-123] to status In Progress.

Copy the prompt

Copied

Assign [PROJ-456] to [person name].

Copy the prompt

Copied

Create a story in [project] for [epic name]: [details].

Sprints & reporting

Copy the prompt

Copied

What is in the current sprint for [project]?

Copy the prompt

Copied

How many open issues are there by priority in [project]?

Copy the prompt

Copied

List all issues closed this week in [project].

Copy the prompt

Copied

Which epics have the most open issues?

SEE HOW AUTH WORKS

Users authorize Jira once. Their Atlassian credentials stay vaulted, every call is checked, and every action is logged.

Authorize

Your user connects

Jira

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

A’s meetings only

Store

Their

Jira

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Jira

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Jira

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across GitHub, Linear, and other project management connectors.

ENGINEERING

Engineering standup agent

Aggregate GitHub and GitLab activity, link to Jira tickets, and post a daily standup digest to Slack. No async updates to chase.

ENGINEERING

DevOps assistant agent

Triage GitHub incidents, open Linear tickets, and notify the on-call channel in Slack with context already attached.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.

// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Jira today. Others tomorrow.

Capability

DIY

Scalekit AgentKit

Token storage

Build + maintain yourself

AES-256 vault, managed

Per-user isolation

Custom credential map

Per-tenant namespace, default

Scope enforcement

Manual checks or none

Per-request, pre-API call

Token refresh

Cron job you maintain

Automatic

Audit trail

Build your own logging

90-day, SIEM-exportable

New connector

New OAuth implementation

Same pattern, one config

Multi-framework

Per-framework adapter code

8 adapters included

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit

Start in your coding agent

Up and running in one command

Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up

Claude Code REPL

Copy Copied

/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack

Cursor Code REPL

Copy Copied

# ~/.cursor/mcp.json
{
""mcpServers"": {
""jira"": {
""url"": ""https://mcp.scalekit.com/jira"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}

Codex Code REPL

Copy Copied

# ~/.codex/config.toml
[mcp_servers.jira]
url = ""https://mcp.scalekit.com/jira""
auth_env = ""SCALEKIT_TOKEN""

Copilot Code REPL

Copy Copied

# .vscode/mcp.json
{
""servers"": {
""jira"": {
""url"": ""https://mcp.scalekit.com/jira"",
""type"": ""http""
}
}
}