jira-mcp: Instructions file for Claude Code

CLAUDE.md

jira-mcp CLAUDE.md is an instructions file for Claude Code from nguyenvanduocit/jira-mcp. It costs 1,330 tokens per session, scanned A, original, MIT.

A repository instruction file for a Go connector that lets AI assistants work with Atlassian Jira, a system for tracking issues, sprints, comments, and work logs.

In plain words
What is it for?
Use it when changing Jira tools or services, building the Go program, running its HTTP server, installing it, or running tests.
Why use it?
It documents the project layout and development commands so agents can build, test, run, and extend the connector correctly.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is nguyenvanduocit/jira-mcp's own configuration. It tells Claude Code how to work on jira-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything jira-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nguyenvanduocit/jira-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nguyenvanduocit/jira-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/nguyenvanduocit/jira-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for jira-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/nguyenvanduocit/jira-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/nguyenvanduocit/jira-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/nguyenvanduocit/jira-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/nguyenvanduocit/jira-mcp/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for jira-mcp CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/nguyenvanduocit/jira-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/nguyenvanduocit/jira-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,330 This file is loaded in full into every session.
When invoked 1,330 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.01330 $0.01330
Opus 5 $0.00665 $0.00665
Sonnet 5 $0.00266 $0.00266
Haiku 4.5 $0.00133 $0.00133

Measured 10d ago against content hash 9b29a117a10b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

jira-mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 154 lines

How it starts

The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

This is a Jira MCP (Model Control Protocol) connector written in Go that enables AI assistants like Claude to interact with Atlassian Jira. The project provides a comprehensive set of tools for managing Jira issues, sprints, comments, worklogs, and more through structured MCP tool calls.

Development Commands

# Build the project
go build -o jira-mcp .

# Run in development mode with HTTP server (requires .env file)
go run . --env .env --http_port 3002

# Run tests
go test ./...

# Install locally
go install

# Use go doc to understand packages and types
go doc <pkg>
go doc <sym>[.<methodOrField>]

Architecture Overview

Core Structure

  • main.go - Entry point that initializes the MCP server, validates environment variables, and registers all tools
  • services/ - Service layer containing Jira client setup and authentication
  • tools/ - Tool implementations organized by functionality (issues, sprints, comments, etc.)
  • util/ - Utility functions for error handling and response formatting

Key Dependencies

  • github.com/ctreminiom/go-atlassian - Go client library for Atlassian APIs
  • github.com/mark3labs/mcp-go - Go implementation of Model Control Protocol
  • github.com/joho/godotenv - Environment variable loading

Tool Implementation Pattern

Each Jira operation follows this consistent pattern using typed handlers:

  1. Input Struct - Define typed input with validation tags
  2. Registration Function (RegisterJira<Category>Tool) - Creates tool definitions and registers them with the MCP server
  3. Typed Handler Function - Processes tool calls with compile-time type safety

Example tool structure:

// 1. Define input struct with validation
type GetIssueInput struct {
    IssueKey string `json:"issue_key" validate:"required"`
    Fields   string `json:"fields,omitempty"`
    Expand   string `json:"expand,omitempty"`
}

// 2. Registration function
func RegisterJiraIssueTool(s *server.MCPServer) {
    tool := mcp.NewTool("jira_get_issue",
        mcp.WithDescription("..."),
        mcp.WithString("issue_key", mcp.Required(), mcp.Description("...")),
        mcp.WithString("fields", mcp.Description("...")),
    )
    s.AddTool(tool, mcp.NewTypedToolHandler(jiraGetIssueHandler))
}

// 3. Typed handler with automatic validation
func jiraGetIssueHandler(ctx context.Context, request mcp.CallToolRequest, input GetIssueInput) (*mcp.CallToolResult, error) {
    client := services.JiraClient()
    // Direct access to validated parameters - no type assertions needed
    issue, response, err := client.Issue.Get(ctx, input.IssueKey, fields, expand)
    if err != nil {
        return nil, fmt.Errorf("failed to get issue: %v", err)
    }
    return mcp.NewToolResultText(util.FormatIssue(issue)), nil
}

Read the full file on GitHub · 154 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 154 lines · 1,330 tokens per session scan A 9b29a117a10b

Subscribe to this mod's changes

jira-mcp CLAUDE.md is an instructions file published in the GitHub repository nguyenvanduocit/jira-mcp (97 stars, last pushed 4mo ago), licensed MIT. It adds 1,330 tokens to every session, about $0.0066 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens