Jira MCP Server

Created By
NoxFra year ago
Overview

What is Jira MCP Server?

Jira MCP Server is a bridge server that connects Jira with the Model Context Protocol (MCP), allowing synchronization and interaction with Jira data through an MCP interface.

How to use Jira MCP Server?

To use the Jira MCP Server, set up the required environment variables, build the Docker image, and run the service using Docker Compose. Access the server via the specified port.

Key features of Jira MCP Server?

  • Synchronization of Jira data via MCP
  • Support for multiple MCP modes: SSE and stdio
  • Exposes various tools for JIRA issue management

Use cases of Jira MCP Server?

  1. Automating ticket management in Jira.
  2. Integrating Jira with AI assistants for enhanced productivity.
  3. Facilitating real-time updates and interactions with Jira data.

FAQ from Jira MCP Server?

  • What technologies are used in Jira MCP Server?

The server is built using Kotlin, Ktor, and Docker.

  • How do I configure the server?

You need to set environment variables for JIRA_URL, JIRA_EMAIL, and JIRA_API_TOKEN.

  • Can I run this server locally?

Yes, you can run it locally using Docker Compose.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
NoxFr
Star
1
Language
Kotlin
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.

5 hours ago