Jira Issue Management
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 6 tools
Each tool has a clearly distinct purpose: create, delete, get, get transitions, transition, and update. The descriptions clarify the difference between getting transitions and performing a transition, leaving no ambiguity.
All tool names follow a consistent snake_case verb_noun pattern (create_issue, delete_issue, get_issue, get_issue_transitions, transition_issue, update_issue). No deviations or mixed conventions.
With only 6 tools, the set is well-scoped for core Jira issue management. Each tool earns its place, covering CRUD and workflow transitions without redundancy.
The surface covers create, read, update, delete, and workflow transitions, but lacks a search or list operation for discovering issues by project or JQL. This is a notable gap that would force agents to know issue keys in advance.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
create_issuedelete_issueget_issueget_issue_transitionstransition_issueupdate_issuecreate_issuedelete_issueget_issueget_issue_transitionstransition_issueupdate_issue
Add one secure layer between your agents and this server.