Jira MCP Server

Created By
fkesheha year ago
An MCP server compatible with Jira V2 and V3 api and custom fields
Overview

What is Jira MCP Server?

Jira MCP Server is an Enhanced Model Context Protocol server that allows AI assistants like Claude to interact directly with Jira, enabling a wide range of project management tasks.

How to use Jira MCP Server?

To use the Jira MCP Server, clone the repository, install dependencies, set up environment variables with your Jira credentials, and start the server using npm commands.

Key features of Jira MCP Server?

  • Full Jira API Integration for comprehensive access to Jira functionality.
  • Enhanced Markdown to Atlassian Document Format (ADF) conversion.
  • Robust input validation and improved error handling.
  • Support for custom fields and advanced workflow management.
  • Bulk operations for efficient issue management.

Use cases of Jira MCP Server?

  1. Automating issue creation and updates in Jira.
  2. Managing user assignments and workflows.
  3. Performing bulk operations on multiple issues for efficiency.

FAQ from Jira MCP Server?

  • Can I use this server with any version of Jira?

Yes, it is compatible with both Jira Cloud and Server instances.

  • Is there a limit to the number of issues I can manage?

The server supports bulk operations, but be mindful of Jira's API rate limits.

  • How do I handle errors?

The server provides detailed error messages for various issues, including authentication and invalid parameters.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fkesheh
Star
0
Language
TypeScript
License
MIT 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)

a day ago