mcp-server-jira
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | JIRA アカウントのメールアドレス | |
| JIRA_BASE_URL | Yes | JIRA Cloud の URL (例: https://your-domain.atlassian.net) | |
| JIRA_API_TOKEN | Yes | Atlassian API トークン |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_issuesC | JQL クエリで JIRA の課題を検索します |
| get_issueC | JIRA 課題の詳細を取得します |
| create_issueA | JIRA に新しい課題を作成します |
| update_issueB | JIRA 課題のフィールドを更新します |
| add_commentB | JIRA 課題にコメントを追加します |
| get_transitionsB | JIRA 課題で利用可能なステータス遷移を取得します |
| transition_issueB | JIRA 課題のステータスを変更します |
| assign_issueB | JIRA 課題の担当者を変更します |
| list_projectsA | 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 9 tools
Each tool targets a distinct action and resource: search, get, create, update, comment, transitions, transition, assign, and list projects. There is no overlap between their purposes.
All tool names consistently use the snake_case verb_noun pattern (e.g., search_issues, get_issue, create_issue). The only minor deviation is 'get_transitions' which is a noun-adjective form, but it still fits the pattern well.
9 tools is a reasonable count for a JIRA MCP server covering core operations. It covers search, CRUD, comments, transitions, assignment, and project listing without being excessive.
The tool surface covers the most common JIRA workflows: search, CRUD, commenting, status transitions, and assignment. Missing capabilities like deleting issues or managing attachments are minor gaps for a typical agent use case.