jira-mcp-server-python

Created By
mbala2304a year ago
MCP Server to fetch the information about issues in JIRA
Overview

what is jira-mcp-server-python?

jira-mcp-server-python is a server application designed to fetch information about issues in JIRA, allowing users to interact with JIRA's issue tracking system programmatically.

how to use jira-mcp-server-python?

To use this project, clone the repository from GitHub, set up the server environment, and configure it to connect to your JIRA instance. You can then make API calls to retrieve issue data.

key features of jira-mcp-server-python?

  • Fetches detailed information about JIRA issues.
  • Supports integration with various JIRA projects.
  • Provides a simple API for developers to access JIRA data.

use cases of jira-mcp-server-python?

  1. Automating the retrieval of issue data for reporting purposes.
  2. Integrating JIRA issue tracking with other applications.
  3. Building custom dashboards that display JIRA issue statistics.

FAQ from jira-mcp-server-python?

  • Can this server work with any version of JIRA?

Yes, as long as the JIRA API is accessible, this server can work with various versions of JIRA.

  • Is there any authentication required?

Yes, you will need to provide valid JIRA credentials to access the issue data.

  • Is this project actively maintained?

The latest commit was made on June 4, 2025, indicating ongoing maintenance.

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

Recommend Servers

View All
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)

21 hours ago