Personal JIRA MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_issueC | 获取JIRA问题详情 |
| get_issue_attachmentC | 获取JIRA问题附件 |
| search_issuesC | 搜索JIRA问题列表 |
| create_issueD | 创建JIRA问题 |
| update_issueD | 更新JIRA问题 |
| get_projectsB | 获取JIRA项目列表 |
| get_projectC | 获取JIRA项目详情 |
| debug_issue_fieldsD | 调试JIRA问题字段 |
| get_attachment_by_filenameC | 根据问题ID和文件名获取JIRA附件 |
| getIssuesC | 获取JIRA问题及其附件 |
| download_all_attachmentsC | 下载JIRA问题的所有附件到本地 |
| get_issue_attachmentsC | 获取JIRA问题的所有附件 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
There is significant overlap between attachment-related tools (download_all_attachments, get_attachment_by_filename, get_issue_attachment, get_issue_attachments, getIssues includes attachments) that could cause confusion about which to use. However, core issue operations (create, get, update, search) and project operations are clearly distinct.
The naming is inconsistent with mixed conventions: most tools use snake_case (create_issue, get_issue), but getIssues uses camelCase. There's also redundancy in naming (get_issue_attachment vs get_attachment_by_filename) and unclear verb choices (debug_issue_fields stands out as different from other CRUD-style names).
12 tools is reasonable for a JIRA server covering issues, projects, and attachments. While there are some redundant tools, the count aligns well with the domain scope and doesn't feel excessive or insufficient for basic JIRA operations.
The toolset covers core JIRA workflows well: CRUD for issues (create, get, update, search), project access (get, list), and attachment handling. Minor gaps include no delete operations for issues or attachments, and debug_issue_fields is a niche tool that doesn't fit standard CRUD patterns, but agents can work around these limitations.