Jira MCP Server B443375f

MCP开发工具

提供方 janbaer

开发工具 未标注 Token 社区 / 第三方 ClaudeCursor

一个通过REST API创建和获取Jira问题的MCP服务器,支持标准问题字段和灵活的ADF格式描述输入。

一句话选型结论

按资料字段整理

Jira MCP Server B443375f 属于开发工具类 MCP 服务器,传输方式未标注,Token,可直接接入 Claude、Cursor,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权Token 部署方式未标注
GitHub 星标 2 仓库热度,无公开仓库时显示未标注
工具数 3 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量3暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

Jira集成TypeScript本地部署问题管理RESTAPIADF格式开发工具

安装与配置

未标注 Token
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 3 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 3 个工具,职责相对集中,接入后不容易误操作。
  • 已适配 Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Jira MCP Server B443375f当前 3 未标注 未标注 无 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方janbaer上游标注的维护方 janbaer
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

11.0 KB
来自项目仓库与上游目录的原文,未做删改

Jira MCP Server

An MCP (Model Context Protocol) server for creating and fetching Jira issues via the REST API. Built with Bun.

Features

  • Fetch and update existing Jira issues
  • Create Jira issues with a single tool call
  • Support for all standard issue fields (summary, description, type, priority, labels)
  • Flexible description input:
  • Plain text → automatic conversion to basic ADF paragraphs
  • Pre-formatted ADF objects → full control over formatting (panels, headings, lists, etc.)
  • Runtime ADF validation with Zod schemas
  • Standalone executable (no runtime dependencies)
  • --help flag for quick setup reference

Prerequisites

  • Bun v1.0+ — install with curl -fsSL https://bun.sh/install | bash
  • Or use devbox for an isolated environment without a permanent Bun installation (see below)
  • A Jira Cloud instance
  • Jira API token (see Atlassian API tokens)

Installation```bash

git clone <your-repo-url>
cd jira-mcp-server
bun install


### Using devbox (no permanent Bun installation)

If you prefer not to install Bun globally, devbox provides an isolated shell with Bun available:```bash
# Install devbox (one-time)
curl -fsSL https://get.jetify.com/devbox | bash

# Enter the devbox shell (installs Bun automatically)
devbox shell

# Now use bun as normal
bun install
bun run build

Run exit to leave the devbox shell. Bun is not added to your system outside of it.

Configuration

The server requires these environment variables:

Variable Description Example
JIRA_URL Your Jira instance URL https://your-domain.atlassian.net
JIRA_EMAIL Your Jira account email user@example.com
JIRA_API_TOKEN Your Jira API token your-api-token
JIRA_PROJECT Default project key for issue creation PROJ

Usage```bash

Build standalone executable

bun run build

Build and deploy to ~/bin

bun run deploy

Build, deploy, and sign (required on macOS — see note below)

bun run deploy-and-sign

Run from source (development)

bun run dev

Inspect with MCP Inspector

bun run mcp-inspect

Display setup instructions

./dist/jira-mcp-server --help


### macOS: use `deploy-and-sign`

On macOS, use `bun run deploy-and-sign` instead of `bun run deploy`. When `bun build --compile` produces a binary, it embeds a code signature. Copying the file with `cp` invalidates that signature because macOS recalculates file hashes on copy. Gatekeeper then kills the binary with `SIGKILL` when you try to run it from the new location.

`deploy-and-sign` adds an ad-hoc re-signing step (`codesign -s -`) after the copy, which satisfies macOS without requiring an Apple Developer certificate.

## Integration with MCP Clients

### Claude Desktop

Add to your config file:
- **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`
- **Windows:** `%APPDATA%\Claude\claude_desktop_config.json````json
{
  &quot;mcpServers&quot;: {
    &quot;jira&quot;: {
      &quot;command&quot;: &quot;/absolute/path/to/jira-mcp-server/dist/jira-mcp-server&quot;,
      &quot;env&quot;: {
        &quot;JIRA_URL&quot;: &quot;https://your-domain.atlassian.net&quot;,
        &quot;JIRA_EMAIL&quot;: &quot;user@example.com&quot;,
        &quot;JIRA_API_TOKEN&quot;: &quot;your-token&quot;,
        &quot;JIRA_PROJECT&quot;: &quot;PROJ&quot;
      }
    }
  }
}

For development (running from source), replace command with &quot;bun&quot; and add &quot;args&quot;: [&quot;run&quot;, &quot;/absolute/path/to/jira-mcp-server/src/index.ts&quot;].

Cursor

  1. Open Cursor Settings → Features → MCP
  2. Add a new MCP server:
    - Transport type: stdio
    - Command: /absolute/path/to/jira-mcp-server/dist/jira-mcp-server
  3. Set the environment variables in Cursor's settings

Claude Code```bash

claude mcp add jira /absolute/path/to/jira-mcp-server/dist/jira-mcp-server


## Tool Reference

### `jira-search-issues`

Searches for Jira issues using a JQL query. Returns a list of matching issues with key fields.

| Parameter    | Type     | Required | Description                                         |
| ------------ | -------- | -------- | --------------------------------------------------- |
| `jql`        | `string` | Yes      | JQL query string                                    |
| `maxResults` | `number` | No       | Maximum results to return (1–100, default 20)       |

**JQL examples:**```
project = MYPROJ AND status = &quot;In Progress&quot;
assignee = currentUser() AND sprint in openSprints()
project = MYPROJ AND labels = &quot;backend&quot; ORDER BY created DESC

Example response:```json
{
"success": true,
"total": 42,
"returned": 20,
"issues": [
{
"key": "PROJ-123",
"summary": "Fix login button on mobile",
"status": "In Progress",
"priority": "High",
"issueType": "Bug",
"assignee": "Jane Doe",
"reporter": "John Smith",
"labels": ["mobile", "frontend"],
"created": "2026-02-19T10:00:00.000+0000",
"updated": "2026-02-19T12:30:00.000+0000",
"url": "https://your-domain.atlassian.net/browse/PROJ-123"
}
]
}


### `jira-get-issue`

Fetches an existing Jira issue by its key.

| Parameter  | Type     | Required | Description                     |
| ---------- | -------- | -------- | ------------------------------- |
| `issueKey` | `string` | Yes      | The issue key (e.g. &quot;PROJ-123&quot;) |

**Example response:**```json
{
  &quot;success&quot;: true,
  &quot;issue&quot;: {
    &quot;key&quot;: &quot;PROJ-123&quot;,
    &quot;summary&quot;: &quot;Fix login button on mobile&quot;,
    &quot;status&quot;: &quot;In Progress&quot;,
    &quot;priority&quot;: &quot;High&quot;,
    &quot;issueType&quot;: &quot;Bug&quot;,
    &quot;assignee&quot;: &quot;Jane Doe&quot;,
    &quot;reporter&quot;: &quot;John Smith&quot;,
    &quot;labels&quot;: [&quot;mobile&quot;, &quot;frontend&quot;],
    &quot;description&quot;: { &quot;type&quot;: &quot;doc&quot;, &quot;version&quot;: 1, &quot;content&quot;: [] },
    &quot;created&quot;: &quot;2026-02-19T10:00:00.000+0000&quot;,
    &quot;updated&quot;: &quot;2026-02-19T12:30:00.000+0000&quot;,
    &quot;url&quot;: &quot;https://your-domain.atlassian.net/browse/PROJ-123&quot;
  }
}

jira-update-issue

Updates an existing Jira issue's summary and/or description. At least one field must be provided.

Parameter Type Required Description
issueKey string Yes The issue key (e.g. "PROJ-123")
summary string No New summary/title for the issue
description string or ADF No Plain text or pre-formatted ADF

Example response:```json
{
"success": true,
"issue": {
"key": "PROJ-123",
"url": "https://your-domain.atlassian.net/browse/PROJ-123"
},
"message": "Successfully updated issue PROJ-123"
}


### `jira-create-issue`

Creates a new issue in Jira.

| Parameter     | Type              | Required | Description                                                   |
| ------------- | ----------------- | -------- | ------------------------------------------------------------- |
| `summary`     | `string`          | Yes      | Summary/title of the issue                                    |
| `description` | `string` or `ADF` | No       | Plain text or pre-formatted ADF object                        |
| `issueType`   | `string`          | No       | Issue type (default: &quot;Task&quot;)                                  |
| `priority`    | `string`          | No       | Priority level (&quot;Highest&quot;, &quot;High&quot;, &quot;Medium&quot;, &quot;Low&quot;, &quot;Lowest&quot;) |
| `labels`      | `string[]`        | No       | Labels to add to the issue                                    |
| `projectKey`  | `string`          | No       | Override the default project key                              |
| `parentKey`   | `string`          | No       | Parent issue key (e.g. &quot;PROJ-10&quot;) — creates as a child issue  |

**Description formatting:**

Plain text is converted to ADF paragraphs automatically:```
&quot;description&quot;: &quot;Main description.\n\nAnother paragraph.&quot;

For full formatting control, pass a pre-formatted ADF object:```json
"description": {
"type": "doc",
"version": 1,
"content": [
{ "type": "paragraph", "content": [{ "type": "text", "text": "Main description" }] },
{ "type": "heading", "attrs": { "level": 3 }, "content": [{ "type": "text", "text": "TODO" }] },
{ "type": "panel", "attrs": { "panelType": "error" }, "content": [
{ "type": "paragraph", "content": [{ "type": "text", "text": "First task" }] }
]}
]
}


Panel types: `error` (red), `info` (blue), `warning` (yellow), `success` (green), `note` (purple).

**Example response:**```json
{
  &quot;success&quot;: true,
  &quot;issue&quot;: {
    &quot;id&quot;: &quot;10001&quot;,
    &quot;key&quot;: &quot;PROJ-123&quot;,
    &quot;url&quot;: &quot;https://your-domain.atlassian.net/browse/PROJ-123&quot;
  },
  &quot;message&quot;: &quot;Successfully created issue PROJ-123&quot;
}

Example Commands

jira-ticket

An interactive command for drafting and creating Jira tickets with proper ADF formatting. Supports Stories, Bugs, and Maintenance tasks with a smart question flow and automatic ADF construction.

Location: `command/jira-ticket.md````bash
/jira-ticket [optional summary]


## Project Structure```
jira-mcp-server/
├── src/
│   ├── index.ts           # Entry point, orchestrates startup
│   ├── config.ts          # Environment variable validation
│   ├── server.ts          # MCP server setup and tool registration
│   ├── jira-client.ts     # Jira REST API client
│   ├── adf-schema.ts      # Zod schema for ADF validation
│   ├── adf-schema.test.ts # ADF validation tests
│   ├── types.ts           # TypeScript type definitions
│   ├── help.ts            # Help text display
│   └── version.ts         # Version from package.json
├── dist/
│   └── jira-mcp-server    # Standalone executable (after build)
├── command/
│   └── jira-ticket.md     # Interactive ticket creation command
├── biome.json             # Linter/formatter configuration
└── package.json

Available Scripts

Script Description
build Build standalone executable with Bun runtime included
deploy Build and copy executable to ~/bin directory
deploy-and-sign Build, copy, and ad-hoc sign (required on macOS)
dev Run source directly with Bun (for development)
test Run tests with Bun
lint Check code with Biome (lint + format)
lint:fix Auto-fix lint and format issues
mcp-inspect Build and launch MCP Inspector for manual testing

Future Improvements

  • [ ] Add more Jira operations (delete, search, comment, transitions)
  • [ ] Support for custom fields
  • [ ] Support for attachments
  • [ ] Caching of project/issue type metadata
  • [ ] Support for Jira Server/Data Center (different auth method)
  • [ ] Add assignee field support
  • [ ] Add component support

License

MIT

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Jira MCP Server B443375f 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Jira MCP Server B443375f 怎么在 Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Jira MCP Server B443375f 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Jira MCP Server B443375f 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Jira MCP Server B443375f 支持哪些客户端?

资料标注支持 Claude、Cursor;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Jira MCP Server B443375f 能提供哪些能力?

资料显示约 3 个工具;能力标签包括 Jira集成、开发工具、TypeScript、Claude、问题管理。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。