MCP.so
ログイン

Jira Requester MCP Server

@scho-to

リポジトリ

Jira Requester MCP Server について

MCP Server using Jira Client v2 to handle Jira Issues

基本情報

カテゴリ

バージョン管理

ランタイム

node

トランスポート

stdio

公開者

scho-to

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "jira-requester": {
      "command": "node",
      "args": [
        "/path/to/mcp-jira-cloud-v2/build/index.js"
      ],
      "env": {
        "JIRA_URL": "",
        "JIRA_USER_EMAIL": "",
        "JIRA_API_TOKEN": ""
      }
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Jira Requester MCP Server?

A Message Communication Protocol (MCP) server that interacts with the Jira API (v2) to fetch ticket information. It is intended for developers and teams who need to retrieve Jira issue details programmatically via MCP-compatible clients.

How to use Jira Requester MCP Server?

Clone the repository, install dependencies (npm install or yarn install), and create a .env file with JIRA_BASE_URL, JIRA_USER_EMAIL, and JIRA_API_TOKEN. Start the server with npm start or yarn start, then clients call the get_jira_ticket tool with the required ticket_id parameter.

Key features of Jira Requester MCP Server

  • Fetch details for a specific Jira ticket using its ID.
  • Optionally specify which fields to include in the response.
  • Optionally expand Jira fields such as changelog or renderedFields.
  • Built with TypeScript and compiled to JavaScript.

Use cases of Jira Requester MCP Server

  • Retrieve the summary, status, and assignee of a Jira ticket.
  • Integrate Jira data into an MCP‑based automation or dashboard.
  • Quickly inspect ticket details during development or debugging.

FAQ from Jira Requester MCP Server

What does Jira Requester MCP Server do?

It is an MCP server that exposes a single tool (get_jira_ticket) to fetch Jira ticket information from a Jira Cloud instance.

What are the dependencies / runtime requirements?

Requires Node.js (version >= 18.x), npm or yarn, and a Jira Cloud instance with a valid API token.

Where does the data live?

All data is fetched live from the Jira instance specified in JIRA_BASE_URL. The server does not store or cache ticket data locally.

What transport does the server use?

The server communicates via the MCP protocol (stdin/stdout by default, as is standard for MCP servers).

How is authentication handled?

Authentication uses Jira API tokens. You must provide JIRA_USER_EMAIL and JIRA_API_TOKEN as environment variables.

コメント

「バージョン管理」の他のコンテンツ

GitHub MCP Server Extension for Zed

LoamStudios

A GitHub MCP Server extension for Zed

91

mcp-github-trending MCP Server

hetaoBackend

MCP server for getting github trending repos & developers

53

Linear MCP Server

cline

a private MCP server for accessing Linear

133

Atlassian Bitbucket MCP Server

aashari

Node.js/TypeScript MCP server for Atlassian Bitbucket. Enables AI systems (LLMs) to interact with workspaces, repositories, and pull requests via tools (list, get, comment, search). Connects AI directly to version control workflows through the standard MCP interface.

157

Git MCP Server

cyanheads

A Git MCP server for AI agents. STDIO & Streamable HTTP.

225