What is jira-mcp-server AGENTS.md?

Project instructions for a Jira MCP server that connects an AI agent to Jira Server or Data Center, Jira's self-hosted editions. They describe the project structure, commands, authentication, and its eight Jira operations.

Use them when developing or operating the server, including finding the current user, listing or viewing issues, creating and updating issues, logging work, and managing worklogs.

They give an agent the context needed to build, run, inspect, and modify this specific server correctly. They also clarify that it targets Jira Server or Data Center, not Jira Cloud.

How hieutv-dng/jira-mcp-server configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to hieutv-dng/jira-mcp-server. 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/hieutv-dng/jira-mcp-server/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/hieutv-dng/jira-mcp-server

Made for: Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/hieutv-dng/jira-mcp-server/agents-md/github.svg)](https://agentmods.dev/instructions/hieutv-dng/jira-mcp-server/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/hieutv-dng/jira-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/hieutv-dng/jira-mcp-server/agents-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/hieutv-dng/jira-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/hieutv-dng/jira-mcp-server/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 584 This file is loaded in full into every session.

When invoked 584 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.

Model	Per session	Once invoked
Fable 5.1	$0.00584	$0.00584
Opus 5	$0.00292	$0.00292
Sonnet 5	$0.00117	$0.00117
Haiku 4.5	$0.00058	$0.00058

Measured 8d ago against content hash 6f1b47e88bbe, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

jira-mcp-server AGENTS.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 8d 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.

AGENTS.md · 58 lines

How it starts

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

AGENTS.md

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

Project Overview

MCP Server providing Jira integration for Codex AI. Targets Jira Server/Data Center (not Cloud) with PAT authentication. 8 tools: get_current_user, list_issues, get_issue_detail, log_work, list_worklogs, delete_worklog, update_issue, create_issue.

Build & Run Commands

npm run build      # TypeScript → dist/
npm run dev        # Watch mode (tsx)
npm start          # Run server (stdio transport)
npm run inspect    # MCP Inspector for testing tools

Architecture

Entry: src/index.ts → McpServer + StdioServerTransport

Core modules:

src/jira/tools/ — Tool registration split theo concern: index.ts barrel, user-tools.ts, issue-tools.ts (+ issue-drift-warning.ts helper), create-issue-tool.ts, worklog-tools.ts
src/jira/client.ts — JiraClient class wrapping Axios for REST API
src/jira/formatter.ts — Markdown output formatting for AI consumption
src/shared/utils.ts — Error handling wrapper, tool chaining hints

Data flow: Codex → MCP stdio → tools/* handler → JiraClient API call → formatter → Markdown response

Key Patterns

Error handling: All tool handlers wrapped with withErrorHandler() from utils.ts
Input validation: Zod schemas for every tool input
Tool chaining: TOOL_CHAINING map in utils.ts suggests next action
Write safety: log_work, update_issue, create_issue, delete_worklog require user confirmation; delete_worklog further requires dryRun preview before real delete

Environment

Requires .env.local with:

JIRA_BASE_URL=https://jira.company.com
JIRA_PAT=<your-token>
JIRA_DEFAULT_PROJECT=XYZ  # Optional

Adding New Tools

Add API method in src/jira/client.ts
Create Zod schema in src/jira/tools/{group}-tools.ts (user/issue/worklog) hoặc tạo file riêng nếu schema lớn (xem create-issue-tool.ts)
Register handler — export register{Group}Tools() và gọi từ src/jira/tools/index.ts
Add formatter in src/jira/formatter.ts if needed
Update TOOL_CHAINING in src/shared/utils.ts
Test with npm run inspect

Read the full file on GitHub · 58 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.

8d ago First seen · 58 lines · 584 tokens per session scan A 6f1b47e88bbe

Subscribe to this mod's changes

jira-mcp-server AGENTS.md is an instructions file published in the GitHub repository hieutv-dng/jira-mcp-server (1 stars, last pushed 18d ago), licensed MIT. It adds 584 tokens to every session, about $0.0029 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-31.

Project management

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

jira-mcp-server: Instructions file for Codex