JIRA MCP Server

Created By
boukeversteegha year ago
Overview

what is JIRA MCP Server?

JIRA MCP Server is a Model Context Protocol (MCP) server designed to facilitate interaction with JIRA, allowing users to manage and retrieve ticket information from active sprints.

how to use JIRA MCP Server?

To use the JIRA MCP Server, you need to configure it with your JIRA credentials and then utilize the provided tools through the MCP interface in your application.

key features of JIRA MCP Server?

  • Fetch tickets from active sprints using list-sprint-tickets.
  • Retrieve detailed information about specific tickets with get-ticket-details.
  • Add comments to tickets using add-comment.
  • Link tickets with a 'relates to' relationship using link-tickets.
  • Update ticket descriptions with update-description.
  • Manage child issues with list-child-issues and create-sub-ticket.

use cases of JIRA MCP Server?

  1. Managing project tasks by fetching and updating tickets in real-time.
  2. Collaborating with team members by adding comments and linking related tickets.
  3. Organizing work by creating sub-tickets for larger tasks.

FAQ from JIRA MCP Server?

  • How do I set up the JIRA MCP Server?

Follow the setup instructions to install dependencies, build the code, and configure your JIRA settings.

  • What parameters do I need to provide for each tool?

Each tool requires specific parameters such as projectKey for listing tickets and issueKey for getting ticket details.

  • Is there error handling in the server?

Yes, the server includes error handling for invalid credentials, missing sprints, and network errors.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
boukeversteegh
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Gpt Scrambler

2 days ago
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.

2 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago