jira-mcp-scoped
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP transport (default: 3456) | |
| JIRA_BASE_URL | Yes | Your Jira instance URL, e.g. https://yourcompany.atlassian.net | |
| JIRA_BOARD_ID | No | Board ID used when placing issues in the current sprint | |
| JIRA_API_TOKEN | Yes | Jira API token — generate one at id.atlassian.com/manage-profile/security/api-tokens | |
| JIRA_LOG_LEVEL | No | Log verbosity: error, info (default), or debug. See Logging. | info |
| JIRA_USER_EMAIL | Yes | The email address of your Jira account | |
| JIRA_PROJECT_KEY | Yes | The project key, e.g. PROJ | |
| JIRA_ATTACHMENTS_DIR | No | Directory to save downloaded attachments (default: ./jira-attachments) | ./jira-attachments |
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 |
|---|---|
| jira_fetch_issueA | Fetch a Jira issue by ID and return its key, summary, description, status, assignee, parent (with its summary and status), subtasks (each with key, summary, and status), labels, and attachments. |
| jira_update_issueA | Update the summary, description, and/or labels of a Jira issue. Labels are modified incrementally: addLabels/removeLabels leave the issue's other labels untouched. |
| jira_create_issueA | Create a new Jira issue (Task, Bug, Story, or Subtask). For subtasks, provide a parentId pointing to the parent Story or Bug — placement is ignored for subtasks. |
| jira_add_commentA | Add a comment to a Jira issue. |
| jira_fetch_commentsA | Fetch all comments for a Jira issue. Returns a list of comments ordered by most recent first, or an empty list if no comments exist. |
| jira_get_settingsA | Return the current Jira MCP configuration (environment variables), with the API token redacted. |
| jira_transition_issueA | Transition a Jira issue to a new status. Use jira_fetch_issue first to get the available transition IDs. |
| jira_search_assignable_usersA | Search for users that can be assigned to issues in the project. |
| jira_assign_issueA | Assign a Jira issue to a user, or unassign it. Use jira_search_assignable_users first to find the user's accountId. |
| jira_download_attachmentA | Download a single Jira attachment by its ID. Use jira_fetch_issue first to get attachment IDs and filenames. |
| jira_list_sprint_issuesA | List all issues in the current active sprint for the project, regardless of assignee. |
| jira_list_my_sprint_issuesA | List all issues in the current active sprint assigned to the current user. |
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
Each tool has a clear, distinct purpose: fetching, creating, updating, transitioning, assigning, commenting, downloading attachments, listing sprints, and searching users. Even the two sprint-listing tools are clearly differentiated by assignee filter.
All tools use a consistent jira_verb_noun pattern in snake_case. Minor verb variations exist (fetch vs get vs list vs search) but each verb is appropriate for its action and the pattern remains predictable.
12 tools is a well-scoped number for a Jira MCP server. Each tool covers a distinct Jira operation without bloat, and the set feels comprehensive for the intended scope.
The tool set covers the core issue lifecycle (create, fetch, update, transition), assignment, comments, attachments (download only), sprint views, and user search. Missing issue search and attachment upload are notable gaps but not critical for a scoped server.