jira-mcp
JIRA MCP 服务器
一个 MCP 服务器,支持大型语言模型 (LLM) 通过标准化工具和上下文与 JIRA 交互。此服务器提供使用 JQL 搜索问题以及检索问题详细信息的功能。
特征
JQL 搜索:执行复杂的 JQL 查询并支持分页
问题详情:检索有关特定 JIRA 问题的详细信息
Related MCP server: JIRA MCP Server
先决条件
npm安装具有 API 访问权限的 JIRA 实例
JIRA API 令牌或个人访问令牌
与 API 令牌关联的 JIRA 用户电子邮件
获取 JIRA API 凭证
通过https://id.atlassian.com登录您的 Atlassian 帐户
导航至安全设置
在 API 令牌下,选择“创建 API 令牌”
给你的令牌一个有意义的名字(例如,“MCP 服务器”)
复制生成的令牌 - 您将无法再次看到它!
使用此令牌作为您的
JIRA_API_KEY使用与您的 Atlassian 帐户关联的电子邮件地址作为
JIRA_USER_EMAIL
用法
与 Claude Desktop 集成
将服务器配置添加到 Claude Desktop 的配置文件中:
macOS : ~/Library/Application Support/Claude/claude_desktop_config.json Windows : %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"jira": {
"command": "npx",
"args": ["-y", "jira-mcp"],
"env": {
"JIRA_INSTANCE_URL": "https://your-instance.atlassian.net",
"JIRA_USER_EMAIL": "your-email@company.com",
"JIRA_API_KEY": "your-api-token"
}
}
}
}重新启动 Claude Desktop 以加载新配置。
可用工具
1. JQL 搜索( jql_search )
使用可自定义参数执行 JQL 搜索查询。
参数:
jql(必需):JQL 查询字符串nextPageToken:分页令牌maxResults:返回的最大结果数fields:要包含的字段名称数组expand:要包含的附加信息
例子:
{
"jql": "project = 'MyProject' AND status = 'In Progress'",
"maxResults": 10,
"fields": ["summary", "status", "assignee"]
}2. 获取问题( get_issue )
检索有关特定问题的详细信息。
参数:
issueIdOrKey(必需):问题 ID 或密钥fields:要包含的字段名称数组expand:要包含的附加信息properties:要包含的属性数组failFast:是否在发生错误时快速失败
例子:
{
"issueIdOrKey": "PROJ-123",
"fields": ["summary", "description", "status"],
"expand": "renderedFields,names"
}发展
配置
在运行服务器之前设置环境变量。在根目录中创建一个.env文件:
JIRA_INSTANCE_URL=https://your-instance.atlassian.net
JIRA_USER_EMAIL=your-email@company.com
JIRA_API_KEY=your-api-token将值替换为:
您实际的 JIRA 实例 URL
与您的 JIRA 帐户关联的电子邮件地址
您的 JIRA API 令牌(可以在 Atlassian 帐户设置中生成)
安装
通过 Smithery 安装
要通过Smithery自动为 Claude Desktop 安装 JIRA:
npx -y @smithery/cli install jira-mcp --client claude手动安装
克隆此存储库:
git clone <repository-url>
cd jira-mcp安装依赖项:
npm install使用 MCP Inspector 运行
对于测试和开发,您可以使用 MCP Inspector:
npm run inspect添加新工具
要添加新工具,请修改index.js中的ListToolsRequestSchema处理程序:
server.setRequestHandler(ListToolsRequestSchema, async () => {
return {
tools: [
// Existing tools...
{
name: "your_new_tool",
description: "Description of your new tool",
inputSchema: {
// Define input schema...
}
}
]
};
});然后在CallToolRequestSchema处理程序中实现该工具。
执照
麻省理工学院
贡献
欢迎贡献!请随时提交 PR。
Available Tools
2 toolsget_issueC
Retrieve details about an issue by its ID or key.
Inputs: issueIdOrKey (required), fields, expand, properties, +1 more.
jql_searchC
Perform enhanced JQL search in Jira
Inputs: jql (required), nextPageToken, maxResults, fields, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_issue retrieves a single issue by ID/key, while jql_search performs broader queries using JQL. There is no overlap or ambiguity between them, as they serve different use cases (specific lookup vs. flexible search).
Both tools follow a consistent snake_case naming pattern with clear verb_noun structure: get_issue and jql_search. The naming is predictable and readable, with no deviations or mixed conventions.
With only 2 tools, this server feels severely under-scoped for a Jira integration. A typical Jira MCP would need more operations like create_issue, update_issue, or list_projects to cover basic workflows. The current set is too thin for meaningful agent interaction.
The tool surface is significantly incomplete for Jira's domain. While get_issue and jql_search provide read/search capabilities, there are major gaps in CRUD operations (no create, update, or delete) and missing lifecycle management (e.g., transitions, comments). This will cause agent failures in common scenarios.
Related MCP Connectors
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
List, view, create, edit, delete, link, comment on, and see the history of Laraue Boards issues.
Search and read Zammad tickets, customers and organizations; add notes, replies and ticket updates.
Search tickets, people, organizations and KB articles in Deskpro, and create tickets and replies.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI models to search Jira issues using JQL and retrieve issue details through the Jira 9.12.14 API.MIT
- AlicenseAqualityDmaintenanceEnables interaction with Jira issues via JQL search, epic management, comments, attachments, and issue CRUD, with support for both Cloud and Server/Data Center instances.931 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides JIRA issue search, retrieval, and update functionalities via MCP.71 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables querying Jira issues using JQL and creating new issues programmatically via natural language.708 npmMIT