JIRA MCP Server (Async)

Created By
judexzhua year ago
A high-performance, asynchronous Model Context Protocol (MCP) server that integrates with JIRA using stdio transport
Overview

what is JIRA MCP Server (Async)?

JIRA MCP Server (Async) is a high-performance, asynchronous Model Context Protocol (MCP) server that integrates with JIRA using stdio transport, enabling AI assistants to interact with JIRA efficiently.

how to use JIRA MCP Server (Async)?

To use the server, clone the repository, install dependencies, set up your JIRA credentials in a .env file, and run the server with an MCP client like Claude Desktop.

key features of JIRA MCP Server (Async)?

  • Asynchronous operations for improved performance
  • Concurrent API calls for simultaneous processing
  • Detailed issue tracking including comments and relationships
  • Ability to create and update JIRA issues
  • Clean architecture focused on essential tools

use cases of JIRA MCP Server (Async)?

  1. Integrating AI assistants with JIRA for issue management
  2. Automating JIRA issue tracking and updates
  3. Enhancing performance of JIRA queries with async operations

FAQ from JIRA MCP Server (Async)?

  • What is the required Python version?

Python 3.13 or higher is required.

  • How do I set up my JIRA credentials?

Create a .env file with your JIRA server URL and API token.

  • Can I use this server with other MCP clients?

Yes, it is designed to work with any MCP client that supports stdio transport.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
judexzhu
Star
0
Language
Python
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

19 hours ago