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.
curl -O https://raw.githubusercontent.com/freema/mcp-jira-stdio/main/.claude/agents/api-integrator.mdgit clone --depth 1 https://github.com/freema/mcp-jira-stdioWrote 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.
[](https://agentmods.dev/agents/freema/mcp-jira-stdio/api-integrator)<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.
<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>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.00057 | $0.00595 |
| Opus 5.5 | $0.00023 | $0.00238 |
| Sonnet 5.5 | $0.00011 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00060 |
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.
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
- Endpoint Integration: Implement new Jira REST API endpoints with proper authentication
- Type Safety: Create comprehensive TypeScript interfaces for all Jira entities
- Error Resilience: Handle all API error scenarios with user-friendly messages
- Performance Optimization: Implement pagination, caching, and retry logic
- MCP Compatibility: Ensure all tools follow MCP SDK patterns and conventions
Integration Process
- Research endpoint in Atlassian documentation
- Define TypeScript types for request/response
- Implement API helper with error handling
- Create MCP tool wrapper with validation
- 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
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.
- 1mo ago First seen · 71 lines · 57 tokens per session scan A a0d6c5a6a68c
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.
Other agents, from other repositories
FAI IT Ticket Resolution Builder
IT Ticket Resolution builder — event-driven classification pipeline, auto-resolution via knowledge base, ServiceNow/Jira integration, skill-based routing, and SLA monitoring.
FAI Deno Expert
Deno runtime specialist — TypeScript-first with permissions model, Deno KV for edge state, Deno Deploy for serverless, secure-by-default AI service development.
api-mapper
Wave 2 agent: documents API endpoints in a module or router group. Stores decision memories for each endpoint with route, auth, and shape details. Links endpoints with DEPENDSON, LEADSTO, and PARTOF relationships.
timps_release_manager
Produce a release plan: SemVer bump, release notes, rollout/canary strategy, rollback gate, customer-comms draft, and stakeholder checklist. Use the timpsreleasemanager MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
fullstack-developer
Use this agent when you need to build complete features spanning database, API, and frontend layers together as a cohesive unit.
Demonstrate
Agent for demonstrating VS Code features.