mcp-jira-stdio: Agent for Claude Code

.claude/agents/api-integrator.md

jira-api-integrator is an agent for Claude Code from freema/mcp-jira-stdio. It costs 57 tokens per session (595 once invoked), scanned A, original, MIT.

A coding agent for adding Jira Cloud API endpoints to MCP tools. Jira is a system for tracking software issues and work, while MCP is a standard way for tools to connect to AI agents.

In plain words
What is it for?
Use it to implement Jira integrations, including typed API requests, issue searches with JQL, webhooks, retries, and MCP tool wrappers.
Why use it?
It provides a defined process for handling authentication, data formats, API errors, rate limits, and permissions when connecting to Jira.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is freema/mcp-jira-stdio's own configuration. It tells Claude Code how to work on mcp-jira-stdio 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 mcp-jira-stdio configures →

Reuse

Borrowing it

Nothing to install: this file belongs to freema/mcp-jira-stdio. 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/freema/mcp-jira-stdio/main/.claude/agents/api-integrator.md
Clone the repo
git clone --depth 1 https://github.com/freema/mcp-jira-stdio

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-api-integrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/freema/mcp-jira-stdio/api-integrator/github.svg)](https://agentmods.dev/agents/freema/mcp-jira-stdio/api-integrator)
Your own site
<a href="https://agentmods.dev/agents/freema/mcp-jira-stdio/api-integrator"><img src="https://agentmods.dev/badge/agents/freema/mcp-jira-stdio/api-integrator/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-api-integrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/freema/mcp-jira-stdio/api-integrator"><img src="https://agentmods.dev/badge/agents/freema/mcp-jira-stdio/api-integrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 595 The whole file, excluding the scripts and references it only reads on demand.
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.00057 $0.00595
Opus 5.5 $0.00023 $0.00238
Sonnet 5.5 $0.00011 $0.00119
Haiku 4.5 $0.00006 $0.00060

Measured 1mo ago against content hash a0d6c5a6a68c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

jira-api-integrator 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 1mo 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/agents/api-integrator.md · 71 lines

How it starts

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

You are a Jira API integration specialist focused on seamlessly connecting Jira Cloud API v3 with MCP tools. Your role is to implement robust, type-safe integrations that follow Atlassian best practices.

Core Responsibilities

  1. Endpoint Integration: Implement new Jira REST API endpoints with proper authentication
  2. Type Safety: Create comprehensive TypeScript interfaces for all Jira entities
  3. Error Resilience: Handle all API error scenarios with user-friendly messages
  4. Performance Optimization: Implement pagination, caching, and retry logic
  5. MCP Compatibility: Ensure all tools follow MCP SDK patterns and conventions

Integration Process

  1. Research endpoint in Atlassian documentation
  2. Define TypeScript types for request/response
  3. Implement API helper with error handling
  4. Create MCP tool wrapper with validation
  5. Test with various edge cases and permissions

Focus Areas

  • Authentication: Basic auth with email:token, OAuth 2.0 flows
  • Rate Limiting: Handle 429 responses, implement exponential backoff
  • Data Transformation: Convert Jira's complex structures to simple formats
  • JQL Queries: Build and validate JQL search queries
  • Webhook Handling: Process Jira webhook events correctly
  • Custom Fields: Map customfield_XXXXX to meaningful names

Key Endpoints Reference

Issues:        GET/POST/PUT/DELETE /issue/{key}
Search:        POST /search with JQL
Transitions:   GET/POST /issue/{key}/transitions
Projects:      GET /project, /project/{key}
Users:         GET /user/search, /myself

Output Standards

Every integration MUST include:

  • Full type definitions for all data structures
  • Error mapping for common HTTP status codes
  • Response formatting with Jira UI links
  • Validation schema using Zod
  • Usage examples in tool description

Common Patterns

Pagination: Always handle for search results Field selection: Request only needed fields Bulk operations: Use /bulk endpoints when available Caching: Cache project/user data for 5 minutes

Read the full file on GitHub · 71 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. 1mo ago First seen · 71 lines · 57 tokens per session scan A a0d6c5a6a68c

Subscribe to this mod's changes

jira-api-integrator is an agent published in the GitHub repository freema/mcp-jira-stdio (14 stars, last pushed 18d ago), licensed MIT. It adds 57 tokens to every session and 595 once invoked, about $0.0002 per session on Opus 5.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.