Jira MCP Server

Created By
uddeshya-23a year ago
Mcp server in typescript to connect with Jira Analyze the issues
Overview

what is Jira MCP Server?

Jira MCP Server is a Model Context Protocol server implementation designed for seamless integration with Jira, allowing AI models to interact with Jira through a standardized interface.

how to use Jira MCP Server?

To use the Jira MCP Server, install it via npm, configure the necessary environment variables, and start the server in either development or production mode.

key features of Jira MCP Server?

  • Full Jira REST API integration
  • Connection pooling for optimal performance
  • Comprehensive error handling
  • Type-safe implementation
  • Built-in rate limiting
  • Request logging and monitoring

use cases of Jira MCP Server?

  1. Integrating AI models with Jira for automated issue analysis.
  2. Monitoring workload analytics for better project management.
  3. Enhancing Jira functionalities with custom AI solutions.

FAQ from Jira MCP Server?

  • What are the prerequisites for running the server?

You need Node.js 14 or higher and npm 6 or higher.

  • How do I start the server?

You can start the server in development mode using npm run dev or in production mode using npm start.

  • Is there a health check endpoint?

Yes, you can use the GET /health endpoint to check the server's health.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
uddeshya-23
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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.

16 hours ago
Voyei

6 hours ago