MCP server for Jira with OAuth 2.0 SSO authentication
Four well-named tools with complete input schemas and strong descriptions. All tools follow verb_noun naming (jira_get_issue, jira_search_issues, etc.). Descriptions are detailed (150-300 chars) and include examples, error guidance, and use-case context. Input schemas use Zod with regex validation, min/max constraints, and defaults. Tool annotations (readOnlyHint, idempotentHint, destructiveHint, openWorldHint) are present on all tools. Output is formatted as text with CHARACTER_LIMIT truncation, but output schema structure is not formally documented. Error handling is mentioned in descriptions but not systematically categorized (retryable vs fatal). No batch variants or pagination cursor support despite jira_search_issues accepting max_results/start_at.
Check if a Jira issue is assigned to someone and return assignee info. Returns a simple assignee status: name and email if assigned, or "Unassigned" if not. Faster than jira_get_issue when you only need assignment info. Args: - issue_key (string): Jira issue key, e.g. "PROJ-123" Returns: - "✅ Jane Doe <[email protected]>" if assigned - "⚠️ Unassigned" if not assigned Examples: - "Is PROJ-42 assigned?" → issue_key: "PROJ-42" - "Who is working on BUG-7?" → issue_key: "BUG-7"
Find all unassigned open issues in a Jira project. A convenience tool that searches for issues where assignee is empty and status is not Done. Args: - project_key (string): Jira project key, e.g. "PROJ" - max_results (number): Max issues to return, 1–50 (default: 20) Returns: List of unassigned issues with key, status, and summary. Examples: - "What's unassigned in PROJ?" → project_key: "PROJ" - "Show me open tickets nobody owns" → project_key: "MYAPP"
Fetch a Jira issue/ticket by its key and return full details including assignee. Returns: issue summary, type, status, priority, assignee (or "Unassigned"), reporter, dates, and labels. Args: - issue_key (string): Jira issue key, e.g. "PROJ-123" Examples: - "Get ticket PROJ-42" → issue_key: "PROJ-42" - "Is MYAPP-100 assigned to someone?" → issue_key: "MYAPP-100" Errors: - "Not authenticated" → run 'npm run auth' first - "Jira API error 404" → issue key does not exist
Search Jira issues using JQL (Jira Query Language). Returns a list of issues matching the query with key, status, assignee, and summary. Args: - jql (string): JQL query string - max_results (number): Max issues to return, 1–50 (default: 20) - start_at (number): Offset for pagination (default: 0) Common JQL examples: - Unassigned in a project: 'project = PROJ AND assignee is EMPTY' - Assigned to me: 'assignee = currentUser()' - Open bugs: 'project = PROJ AND issuetype = Bug AND status != Done' - Recently updated: 'project = PROJ AND updated >= -7d ORDER BY updated DESC' Returns: Total count + list of issues with key, status, assignee, summary.
Output schema not formally documented. Tools return text content via CHARACTER_LIMIT truncation, but LLMs cannot infer the structure of formatted responses (field names, types, nested objects). Downstream tools cannot reliably extract data.
Error handling is descriptive in tool descriptions but not systematically categorized. No explicit guidance on which errors are retryable (e.g., 'Not authenticated' vs 'Jira API error 404'). LLMs cannot reliably decide whether to retry or ask the user.
jira_search_issues accepts pagination (max_results, start_at) but does not return a total_count or next_cursor. LLMs cannot determine if more results exist or how to fetch them efficiently.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2026-07-28+ | v2 |
No batch variants. Agents calling jira_check_assignee or jira_get_issue in a loop (e.g., for 10 issues) generate 10 sequential calls instead of one batch call. Wastes tokens and latency.
Credentials (Jira API token, OAuth tokens) are managed via auth-server.ts and saved locally, but the tool definitions do not document how authentication is injected or what happens if tokens expire. LLMs see 'Not authenticated' error but have no recovery path.