Introduction

What is jtk?

jtk (Jira Toolkit) is a developer-focused command-line interface and MCP server for Jira Cloud, written in Go. It follows the Unix philosophy: do one thing well. jtk handles Jira — not Confluence, not Bitbucket, not the entire Atlassian suite.

It ships as a single binary with two modes:

CLI mode — run jtk issues get PROJ-123 from your terminal
MCP mode — run jtk mcp to expose 10 multiplexed tools to AI agents

Why jtk?

Most Jira integrations are either bloated (trying to cover all Atlassian products), poorly optimized for AI consumption (returning raw 50KB JSON blobs), or missing write operations.

jtk is purpose-built for developers who:

Want fast terminal access to Jira without opening a browser
Use AI coding agents (Claude, Cursor, etc.) and need them to interact with Jira
Need a single, portable binary with no runtime dependencies

Comparison

Feature	jtk	sooperset/mcp-server-jira	aashari/jira	Official Atlassian
Language	Go	TypeScript	TypeScript	TypeScript
Single binary	Yes	No (Node.js)	No (Node.js)	No (Node.js)
CLI mode	Yes	No	Yes	No
MCP mode	Yes	Yes	Yes	Yes
Permission introspection	Yes	No	No	No
Response flattening	Yes	No	No	No
Git branch detection	Yes	No	No	No
Dev info (branches/PRs)	Yes	No	No	No
Tool count	10 multiplexed	13 flat	8	20+
Write operations	Yes	Limited	Yes	Yes
Jira only (focused)	Yes	Yes	Yes	No (all Atlassian)

Architecture

┌─────────────┐     ┌──────────────┐
│  Terminal    │────▶│   CLI Mode   │
│  (human)    │     │  cobra cmds  │
└─────────────┘     └──────┬───────┘
                           │
                    ┌──────▼───────┐
                    │  jira.Client │
                    │  (HTTP API)  │
                    └──────▲───────┘
                           │
┌─────────────┐     ┌──────┴───────┐
│  AI Agent   │────▶│   MCP Mode   │
│  (Claude)   │     │  11 tools    │
└─────────────┘     └──────────────┘

Both modes share the same jira.Client underneath. The MCP tools use a multiplexed pattern — each tool handles multiple actions via an action parameter, reducing tool count while maintaining full coverage.