Jira MCP Server

Created By
InfinitIQ-Techa year ago
MCP Server for handling Jira issues
Overview

what is Jira MCP Server?

Jira MCP Server is a Model Context Protocol (MCP) server designed for interacting with Jira's REST API using the jira-python library. It allows users to manage Jira issues through natural language commands.

how to use Jira MCP Server?

To use the Jira MCP Server, install it via pip or Docker, configure the necessary environment variables, and run the server. You can then interact with Jira using commands in Claude Desktop or through the command line.

key features of Jira MCP Server?

  • Retrieve all accessible Jira projects
  • Get details for specific Jira issues
  • Search issues using JQL (Jira Query Language)
  • Create new Jira issues
  • Add comments to existing issues
  • Get available transitions for issues
  • Transition issues to new statuses

use cases of Jira MCP Server?

  1. Managing Jira projects and issues through natural language.
  2. Automating issue creation and updates.
  3. Integrating Jira with other applications using the MCP protocol.

FAQ from Jira MCP Server?

  • What is the minimum Python version required?

Python 3.9 or higher is required to run the server.

  • Can I use this server with Jira Cloud?

Yes, the server supports Jira Cloud, Server, and Data Center instances.

  • How do I authenticate with Jira?

You can authenticate using basic auth, API tokens, or personal access tokens depending on your Jira setup.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
InfinitIQ-Tech
Star
1
Language
Python
License
MIT license

Recommend Servers

View All
Crevio

a day ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

19 hours ago