Summary
Two tools, both read-only, and between them they answer most of what people ask Jira in passing.
Nothing here writes — no transitions, no comments, no issue creation — so it is safe to hand to an agent that only needs to answer questions about the board. The whole surface is JQL, which makes it exactly as capable as the query you can write, and the fields parameter is what keeps a broad query from arriving as several hundred kilobytes of issue documents.
What it is
A read-only pair over the Jira REST API: an enhanced JQL search with paging, and a single-issue fetch by ID or key.
What you get
- Any JQL query run against your instance, with maxResults and a nextPageToken to walk the rest
- Fields and expand on both tools, so a search can come back as keys and summaries instead of whole issue documents
- One issue by issueIdOrKey, with its properties and a failFast switch
Requirements
JIRA_INSTANCE_URL, JIRA_USER_EMAIL and JIRA_API_KEY — an Atlassian account's API token together with the address of the instance it belongs to.
Setup effort
One command plus a key — npx -y @smithery/cli install jira-mcp --client claude, then supply credentials