Jira Cloud MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | The email address of your Jira account | |
| JIRA_BASE_URL | Yes | Your Jira Cloud URL, e.g. https://yourcompany.atlassian.net | |
| JIRA_API_TOKEN | Yes | An API token generated in your Atlassian account settings | |
| JIRA_MCP_RATE_LIMIT | No | Max tool calls per second (default: 10) |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_attachmentB | Get attachment metadata |
| submit_bulk_deleteC | Bulk delete issues |
| submit_bulk_editC | Bulk edit issues |
| submit_bulk_moveD | Bulk move issues |
| submit_bulk_transitionB | Bulk transition issue statuses |
| create_componentC | Create component |
| get_fieldsC | Get fields |
| create_issueD | Create issue |
| create_issuesB | Bulk create issue |
| bulk_fetch_issuesC | Bulk fetch issues |
| get_create_issue_metaC | Get create issue metadata |
| get_issueD | Get issue |
| edit_issueD | Edit issue |
| delete_issueD | Delete issue |
| assign_issueD | Assign issue |
| add_attachmentD | Add attachment |
| get_change_logsD | Get changelogs |
| get_change_logs_by_idsC | Get changelogs by IDs |
| get_commentsD | Get comments |
| add_commentD | Add comment |
| get_commentC | Get comment |
| update_commentD | Update comment |
| delete_commentC | Delete comment |
| get_edit_issue_metaC | Get edit issue metadata |
| get_issue_propertyC | Get issue property |
| set_issue_propertyC | Set issue property |
| delete_issue_propertyC | Delete issue property |
| get_remote_issue_linksC | Get remote issue links |
| create_or_update_remote_issue_linkC | Create or update remote issue link |
| get_remote_issue_link_by_idB | Get remote issue link by ID |
| delete_remote_issue_link_by_idB | Delete remote issue link by ID |
| get_transitionsD | Get transitions |
| do_transitionC | Transition issue |
| get_votesC | Get votes |
| add_voteD | Add vote |
| remove_voteC | Delete vote |
| get_issue_watchersC | Get issue watchers |
| add_watcherC | Add watcher |
| remove_watcherC | Delete watcher |
| get_issue_worklogC | Get issue worklogs |
| add_worklogD | Add worklog |
| get_worklogD | Get worklog |
| update_worklogC | Update worklog |
| delete_worklogC | Delete worklog |
| link_issuesC | Create issue link |
| get_issue_linkC | Get issue link |
| delete_issue_linkC | Delete issue link |
| get_issue_link_typesB | Get issue link types |
| get_issue_types_for_projectC | Get issue types for project |
| get_all_labelsA | Get all labels |
| get_prioritiesD | Get priorities |
| get_all_projectsC | Get all projects |
| search_projectsC | Get projects paginated |
| get_projectC | Get project |
| get_project_componentsC | Get project components |
| get_project_versionsC | Get project versions |
| search_and_reconsile_issues_using_jql_postC | Search for issues using JQL enhanced search (POST) |
| get_statusesC | Get all statuses |
| get_userD | Get user |
| find_bulk_assignable_usersC | Find users assignable to projects |
| find_usersD | Find users |
| create_versionD | Create version |
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 62 tools
Most tools map to a distinct resource and action, but a few pairs blur together: get_issue_worklog/get_worklog, bulk_fetch_issues/search_and_reconsile_issues_using_jql_post, and get_all_projects/search_projects. The one-line descriptions are too terse to fully clarify these boundaries.
There is a strong base of verb_noun names like get_issue, create_issue, update_comment, and delete_worklog, but conventions drift with submit_bulk_*, create_issues vs bulk_fetch_issues, do_transition, and the outlier search_and_reconsile_issues_using_jql_post. Overall the names remain readable but are not consistently patterned.
With 62 tools, this far exceeds the 25+ 'too many' threshold and reaches the 50+ extreme-mismatch range. Even for a broad platform like Jira, the number of bulk, metadata, and subresource variants makes the surface overwhelming for an agent.
The server covers the core issue lifecycle thoroughly: create/edit/get/delete, transitions, comments, worklogs, watchers, votes, attachments, issue links, properties, remote links, search, projects, and users. Minor gaps like attachment download/delete and update/delete for components/versions are workable and do not create dead ends in the main workflow.