Jira MCP Server 80c64dae

MCPAI代理

提供方 pdogra1299

AI代理 未标注 Token 社区 / 第三方 Claude DesktopClaude

一个用于Jira API集成的模型上下文协议(MCP)服务器,支持问题管理、搜索、评论、工作流转换和附件处理。

一句话选型结论

按资料字段整理

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

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

工具与能力

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

能力标签

支持客户端

适用场景

问题管理TypeScript本地部署Jira集成工作流自动化AI助手API服务

安装与配置

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

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

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

值得选的地方

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

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Jira MCP Server 80c64dae当前 5 未标注 支持远程部署 无 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

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

详细介绍

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

Jira MCP Server

A Model Context Protocol (MCP) server for Jira API integration. This server enables AI assistants like Claude to interact with Jira Cloud instances for issue management, search, comments, workflow transitions, and attachment handling.

Features

  • Issue Management: Get, create, update, and assign Jira issues with custom field support
  • JQL Search: Search issues using Jira Query Language
  • Comments: Add and retrieve comments on issues
  • Workflow: Get available transitions and change issue status
  • Metadata Discovery: Get field requirements and allowed values for projects
  • User Search: Find users by email or name for assignments
  • Projects: List all accessible projects
  • Attachments: List, upload, delete attachments and retrieve their content — text files returned as text, images rendered inline via Claude vision
  • Issue Links: Add, remove, and list relationships between issues (relates, blocks, duplicates) without touching the constrained parent hierarchy field
  • Token Efficient: 6 compound tools instead of 17+ flat tools — ~50% fewer tokens per session

Installation

Using npm (Recommended)```bash

npm install -g @nexus2520/jira-mcp-server


### From Source

1. **Clone the repository**:```bash
   git clone https://github.com/pdogra1299/jira-mcp-server.git
   cd jira-mcp-server
   ```

2. **Install dependencies**:```bash
   pnpm install
   ```

3. **Build the project**:```bash
   pnpm run build
   ```

### Prerequisites

- Node.js >= 16.0.0
- A Jira Cloud account with API access
- Jira API token (generate from Atlassian Account Settings)

## Configuration

### Environment Variables

- `JIRA_EMAIL`: Your Atlassian account email
- `JIRA_API_TOKEN`: Your Jira API token
- `JIRA_BASE_URL`: Your Jira instance URL (e.g., `https://yourcompany.atlassian.net`)

### Claude Desktop Configuration

Add the following to your Claude Desktop MCP settings file:

**Location**:
- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
- Windows: `%APPDATA%\Claude\claude_desktop_config.json`
- Linux: `~/.config/Claude/claude_desktop_config.json`

**Configuration (if installed via npm)**:```json
{
  "mcpServers": {
    "jira": {
      "command": "npx",
      "args": [
        "-y",
        "@nexus2520/jira-mcp-server"
      ],
      "env": {
        "JIRA_EMAIL": "your-email@company.com",
        "JIRA_API_TOKEN": "your-api-token-here",
        "JIRA_BASE_URL": "https://yourcompany.atlassian.net"
      }
    }
  }
}

Configuration (if built from source):```json
{
"mcpServers": {
"jira": {
"command": "node",
"args": [
"/absolute/path/to/jira-mcp-server/build/index.js"
],
"env": {
"JIRA_EMAIL": "your-email@company.com",
"JIRA_API_TOKEN": "your-api-token-here",
"JIRA_BASE_URL": "https://yourcompany.atlassian.net"
}
}
}
}


### Getting Your Jira API Token

1. Go to Atlassian Account Settings
2. Click "Create API token"
3. Give it a label (e.g., "Claude MCP")
4. Copy the generated token
5. Use it in your configuration

## Tool Architecture

This server exposes **6 compound tools** — each with an `action` parameter that selects the operation. This design reduces the token overhead of tool definitions by ~50% compared to 17+ flat tools, leaving more context for actual work.

| Tool | Actions | Description |
|------|---------|-------------|
| `jira_issues` | `get` `create` `update` `assign` | Full issue lifecycle management |
| `jira_search` | `issues` `projects` `users` `create_metadata` | Search and discovery |
| `jira_comments` | `get` `add` | Read and write comments |
| `jira_workflow` | `get_transitions` `transition` | Status transitions |
| `jira_attachments` | `list` `get_content` `upload` `delete` | File attachments |
| `jira_links` | `list` `add` `remove` `get_link_types` | Issue link relationships |

---

## Available Tools

### `jira_issues`

Manage the full lifecycle of Jira issues.

**Required**: `action`

| Action | Description | Required params | Optional params |
|--------|-------------|-----------------|-----------------|
| `get` | Fetch full issue details | `issueKey` | — |
| `create` | Create a new issue | `projectKey`, `summary`, `issueType` | `description`, `priority`, `assignee`, `labels`, `customFields` |
| `update` | Edit fields on an existing issue | `issueKey` | `summary`, `description`, `priority`, `assignee`, `labels`, `customFields` |
| `assign` | Set or clear the assignee | `issueKey`, `assignee` | — |

**Tips**:
- Always call `jira_search` with `action=create_metadata` before creating issues to discover required custom fields and allowed values.
- Pass `assignee: "-1"` to unassign an issue.
- `description` accepts plain text or an Atlassian Document Format (ADF) object.
- `customFields` is a key-value map: `{"customfield_10000": "value"}`.

**Examples**:```
Get details for PROJ-123
Create a Bug in project PROJ with summary "Login button broken"
Update PROJ-123 priority to High
Assign PROJ-123 to john.doe@company.com

jira_search

Search and discover Jira resources.

Required: action

Action Description Required params Optional params
issues Search issues via JQL jql maxResults, fields
projects List all accessible projects — maxResults
users Find users by name or email query maxResults
create_metadata Get field requirements for creating issues projectKey issueType

Common JQL examples:```
project = PROJ AND status = Open
assignee = currentUser() AND status != Done
priority = High AND created >= -7d


**Tips**:
- Use `create_metadata` before `jira_issues` `create` to understand what fields are required for a project/issue type.
- Use `users` to look up account IDs for assignments — pass the returned account ID or email to `jira_issues` `assign`.
- `fields` (for `issues`) controls which JIRA fields are fetched per result — e.g. `["summary","status","priority","duedate","assignee"]`. Defaults to `["summary"]`.

**Structured output**: the `issues` action and `jira_issues` `get` return a `structuredContent` JSON payload alongside the markdown, so programmatic consumers can read fields directly without parsing markdown. For `issues` it is `{ jql, count, isLast, nextPageToken, issues: [{ key, id, self, fields }] }`.

---

### `jira_comments`

Read and write comments on a Jira issue.

**Required**: `action`, `issueKey`

| Action | Description | Required params |
|--------|-------------|-----------------|
| `get` | Fetch all comments on an issue | — |
| `add` | Post a new comment | `comment` |

`comment` accepts plain text or an ADF object.

**Examples**:```
Get all comments on PROJ-123
Add a comment to PROJ-123: "Fixed in PR #456"

jira_workflow

Manage issue status transitions.

Required: action, issueKey

Action Description Required params Optional params
get_transitions List available status transitions — —
transition Move issue to a new status transitionId comment

Tip: Always call get_transitions first — transition IDs vary per project and issue type. The transitionId from the response is what you pass to transition.

Examples:```
Get available transitions for PROJ-123
Move PROJ-123 to "In Progress" (use get_transitions first to find the ID)


---

### `jira_attachments`

Manage file attachments on Jira issues.

**Required**: `action`

| Action | Description | Required params | Optional params |
|--------|-------------|-----------------|-----------------|
| `list` | List all attachments with metadata | `issueKey` | — |
| `get_content` | Download and return file content | `attachmentId` | `mimeType` |
| `upload` | Attach a local file to an issue | `issueKey`, `filePath` | `fileName` |
| `delete` | Remove an attachment by ID | `attachmentId` | — |

**Content types returned by `get_content`**:
- **Text files** (`text/*`, `application/json`, `application/xml`): returned as readable text
- **Images** (`image/*`): returned as base64 — Claude will render them inline
- **Other types** (PDF, zip, etc.): returns file metadata with a descriptive message

**Tips**:
- Use `list` first to get attachment IDs before calling `get_content` or `delete`.
- `fileName` in `upload` overrides the filename shown in Jira (defaults to the file's basename).

**Examples**:```
List attachments on PROJ-123
Get the content of attachment 136904
Upload /tmp/report.pdf to PROJ-123
Delete attachment 136904

jira_links

Manage relationships between issues independently of Jira's project hierarchy config — useful when you need to associate a Bug with a Story but the project doesn't allow Bug → Story as a parent-child relationship.

Required: action

Action Description Required params Optional params
get_link_types List available link type names for this Jira instance — —
add Create a link between two issues issueKey, linkedIssueKey, linkType direction
list List all links on an issue, with link IDs issueKey —
remove Delete a link by ID linkId —

Link direction:
- Symmetric types (Relates, Duplicate): direction doesn't matter.
- Directional types (Blocks, Cloners, Causes): direction: outward means issueKey is the outward side (e.g. issueKey blocks linkedIssueKey); direction: inward means issueKey is the inward side (e.g. issueKey is blocked by linkedIssueKey). Defaults to outward.

Tips:
- Run get_link_types first — link type names vary per Jira instance config.
- Use list to find a linkId before calling remove.

Examples:List the link types available in Jira Link PROJ-1 to PROJ-2 as Relates Mark PROJ-1 as blocking PROJ-2 List all links on PROJ-1 Remove link 10042


API Reference

This server uses the Jira REST API v3.

Troubleshooting

"Error: JIRA_EMAIL and JIRA_API_TOKEN are required"

Make sure you've set the environment variables in your MCP configuration.

Authentication errors

  • Verify your API token is correct
  • Ensure your email matches your Atlassian account
  • Check that your JIRA_BASE_URL doesn't have a trailing slash

Permission errors

The API token uses the permissions of the user who created it. Make sure your account has the necessary permissions for the actions you're trying to perform.

License

MIT

Author

Parth Dogra

Contributing

Feel free to open issues or submit pull requests for improvements!

常见问题

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

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

Jira MCP Server 80c64dae 怎么在 Claude Desktop、Claude 里配置?

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

Jira MCP Server 80c64dae 收费吗?

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

Jira MCP Server 80c64dae 需要 API Key 吗?

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

Jira MCP Server 80c64dae 支持哪些客户端?

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

Jira MCP Server 80c64dae 能提供哪些能力?

资料显示约 5 个工具;能力标签包括 问题管理、工作流自动化、TypeScript、Claude、API集成。具体工具清单以官方文档为准。

Jira MCP Server 80c64dae 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

Jira MCP Server 80c64dae 是本地还是远程?

它是远程端点,连服务地址即可。

热门专题

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

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