MCP Server for Jira

Created By
rihofujinoa year ago
Overview

what is MCP Server for Jira?

MCP Server for Jira is a server application that integrates with the Jira API to manage and manipulate Jira issues effectively.

how to use MCP Server for Jira?

To use MCP Server for Jira, install the necessary dependencies, configure the environment variables with your Jira API credentials, and start the server in development or production mode.

key features of MCP Server for Jira?

  • Search for Jira issues using JQL queries.
  • Retrieve detailed information about specific issues.
  • Create new issues in Jira.
  • Update existing issues.
  • Add comments to issues.
  • Transition issues through different workflow statuses.

use cases of MCP Server for Jira?

  1. Automating issue management in software development projects.
  2. Integrating Jira with other tools for enhanced project tracking.
  3. Streamlining communication and updates within teams using Jira.

FAQ from MCP Server for Jira?

  • What programming language is MCP Server for Jira built with?

MCP Server for Jira is built using JavaScript.

  • How do I set up the environment variables?

You need to copy the .env.example file to .env and edit it to include your Jira API credentials.

  • Is there any logging feature?

Yes, logs are saved in logs/combined.log and logs/error.log for monitoring and debugging.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rihofujino
Star
0
Language
JavaScript
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