Jira MCP Server (rui-branco/jira-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 57 tools. No publisher has claimed this listing.

C
Caution
74/100

Jira MCP Server

Enables users to fetch and search Jira tickets, comments, and attachments directly within Claude Code. It features JQL support and automatically exports linked Figma designs to provide comprehensive project context.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

rui-branco

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
// tools this server exposes57 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

jira_get_myself

Get the current authenticated user's info including accountId. Use this to get your account ID for assigning tickets. When multiple Jira instances are configured, use the 'instance' parameter to specify which one.

jira_get_ticket

Fetch a Jira ticket by its key (e.g., MODS-12115). Returns full details including description, comments, attachments, and linked Figma designs.

jira_search

Search Jira tickets using JQL. Returns detailed fields including dates, story points, labels, components, fix versions, time tracking, and parent. Examples: 'project = MODS AND status = Open'. When multiple Jira instances are configured, use the 'instance' parameter to specify which one.

jira_add_comment

Add a comment to a Jira ticket. Follow the server instructions' comment style rules.

jira_reply_comment

Reply to a specific comment on a Jira ticket. Quotes the original comment and mentions the author.

jira_edit_comment

Edit an existing comment on a Jira ticket (replaces the text). Follow the server instructions' comment style rules.

jira_delete_comment

Delete a comment from a Jira ticket. This action is irreversible.

jira_transition

Change the status of a Jira ticket. Use targetStatus to transition by name (auto-handles intermediate steps like In Progress), transitionId for direct transition, or omit both to list available transitions.

jira_update_ticket

Update fields on a Jira ticket. IMPORTANT: Only pass the fields you want to change. Omitted fields are left untouched. NEVER use em dashes (—) or en dashes (–) in text — use commas, periods, or rewrite the sentence instead.

jira_search_users

Search for Jira users by name or email. Returns account IDs and display names. Use this to find users for mentions or assignments. When multiple Jira instances are configured, use the 'instance' parameter to specify which one.

jira_get_changelog

Get status change history for a Jira ticket or multiple tickets via JQL. Returns all status transitions with timestamps and authors, plus computed metrics (cycle time, lead time, time in each status). Use issueKey for a single ticket, or jql for bulk retrieval. Instance is auto-detected from issueKe

jira_add_instance

Add or update a Jira instance configuration. Saves to config and makes it available immediately without restart. To add a new instance, provide name + email + token + baseUrl. To update an existing instance (e.g. change projects or set as default), just provide name and the fields to change.

jira_remove_instance

Remove a Jira instance configuration by name. Cannot remove the last remaining instance.

jira_list_instances

List all configured Jira instances with their names, URLs, project prefixes, and which is the default.

jira_get_teams

Search for available Jira teams by name. Returns matching teams with their IDs. Use this to find a team before setting it as default or assigning to a ticket. IMPORTANT: You MUST display the results in your chat response so the user can see them.

jira_create_ticket

Create a new Jira issue (story, task, bug, epic, etc.). Returns the new issue key and URL. Use jira_search_users to get account IDs for assignee. NEVER use em dashes or en dashes in text fields.

jira_create_subtask

Create a subtask under a parent Jira ticket. The subtask is created in the same project as the parent. NEVER use em dashes or en dashes in text fields.

jira_link_tickets

Link two Jira tickets together with a relationship type. Use jira_get_link_types to discover available link type names. Common types: 'Blocks' (blocks/is blocked by), 'Relates' (relates to), 'Duplicate' (duplicates/is duplicated by), 'Cloners' (clones/is cloned by).

jira_delete_ticket

Delete a Jira ticket. This action is IRREVERSIBLE. If the ticket has subtasks, set deleteSubtasks to true or the deletion will fail.

jira_add_attachment

Upload a file attachment to a Jira ticket. Provide either a local file path or base64-encoded file content.

jira_get_link_types

List all available issue link types in the Jira instance. Use this to discover valid link type names before using jira_link_tickets.

jira_get_transitions

List available status transitions for a Jira ticket. Use this to discover valid transition names/IDs before using jira_transition.

jira_unlink_tickets

Remove a link between two Jira tickets. Fetches the issue to find the link ID automatically.

jira_remove_attachment

Remove an attachment from a Jira ticket by attachment ID or filename. If using filename, fetches the ticket to find the attachment ID.

jira_add_watcher

Add a watcher to a Jira ticket. The watcher will receive notifications for changes on the ticket.

jira_remove_watcher

Remove a watcher from a Jira ticket.

jira_add_worklog

Log time/work on a Jira ticket. Use Jira time format for timeSpent (e.g., '2h 30m', '1d', '30m').

jira_get_worklogs

Get work logs (time tracking entries) for a Jira ticket.

jira_clone_ticket

Clone/duplicate a Jira ticket. Creates a new ticket with the same summary, description, priority, labels, and components. Optionally links the clone to the original.

jira_move_to_sprint

Move one or more tickets into a sprint. Use jira_get_sprints to find sprint IDs.

jira_get_sprints

List sprints for an agile board. Returns sprint IDs, names, states, and dates.

jira_get_boards

List agile boards (Scrum or Kanban). Optionally filter by project key or board name.

jira_get_issue_types

List available issue types for a project. Useful before creating tickets to know valid issue type names.

jira_get_priorities

List all available priority levels in the Jira instance.

jira_get_components

List all components for a project. Useful before creating tickets to know valid component names.

jira_get_versions

List all versions/releases for a project. Useful for setting fixVersions on tickets.

confluence_get_spaces

List Confluence global spaces. Returns [{ key, name, id }]. On Cloud reuses the Jira instance credentials (Confluence base URL is <jiraBaseUrl>/wiki).

confluence_get_space

Get a single Confluence space by key. Returns space metadata including description and homepage.

confluence_create_space

Create a new Confluence global space. Provide key, name, and optional description (plain text).

confluence_update_space

Update a Confluence space's name or description. At least one of name/description must be provided.

confluence_delete_space

Delete a Confluence space by key. This is asynchronous on Confluence Cloud — the call returns a long-running task.

confluence_search

Confluence CQL search for content. Builds CQL: text ~ "<query>" AND type = <type> [AND space = "<key>"] ORDER BY lastModified DESC.

confluence_get_recent_pages

List recently modified pages within a time window. Params: spaceKey (optional), sinceDays (default 30), limit (default 25).

confluence_get_space_root_pages

List top-level (root) pages in a Confluence space, expanded with childTypes.page so consumers can tell which pages have children.

confluence_get_page_children

List direct child pages of a Confluence page, expanded with version, history and childTypes.page.

confluence_get_page

Fetch a full Confluence page. Returns v1 content (body.view, body.storage, space, ancestors, labels) merged with v2 body.atlas_doc_format when includeAdf is true. ADF is the only format that preserves table cell background colors on modern Cloud pages.

confluence_get_comments

List comments on a Confluence page, expanded with body.view, version, created/updated history.

confluence_add_comment

Add a footer comment to a Confluence page. Default format is 'text' (plain text / markdown-lite is wrapped in <p>…</p> with <br/> for single newlines). Use format='storage' to pass valid storage XHTML as-is.

confluence_update_page

Update an existing Confluence page. Title and/or body (storage XHTML). Version auto-bumps if omitted (fetches current version first). Confluence requires version.number = current + 1.

confluence_create_page

Create a new Confluence page. Body must be storage XHTML. Optional parentId nests under an existing page.

confluence_delete_page

Delete a Confluence page by ID.

confluence_get_labels

List labels on a Confluence page.

confluence_add_label

Add a label to a Confluence page.

confluence_remove_label

Remove a label from a Confluence page.

confluence_list_attachments

List attachments on a Confluence page.

confluence_upload_attachment

Upload a file as an attachment to a Confluence page. Provide either filePath or fileContent (base64) + fileName.

confluence_download_attachment

Download an attachment from a Confluence page by filename. Saves under ~/.config/jira-mcp/confluence-attachments/<pageId>/ and returns the local path.

// known CVEs in dependencies1 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.25.3GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configJIRA_MCP_CONFLUENCETo expose Confluence tools from boot (skip the activation step), set the confluence config key or the environment variable:
configJIRA_MCP_DRY_RUN3. Environment: export =1 before launching your AI client.
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

57/57 tools missing one or more hints — jira_get_myself (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jira_get_ticket (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jira_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +54 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

18/57 tools referenced in tests (32%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

5 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Production dependencies are patched

0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.25.3 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

1/2 production deps stale: node-fetch@2023-11-30 (2.7y)

Domain consistency

npm scope @rui.branco doesn't match GitHub owner rui-branco

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/rui-branco/jira-mcp?variant=verified)](https://m8ven.ai/mcp/rui-branco/jira-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b9554843f98ecbf65ed5239a046e8c4d877c0561
code hash: 5cd68f5400ef4b1ea3bb551a8a007e003901a819d3bb1b565b498ac8e6e3a8f1
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client