Jira MCP Server (tezaswiraj7222/jira-mcp) is an MCP server listed on the M8ven Trust Index. It scores 52 out of 100, grade D. It declares 91 tools. No publisher has claimed this listing.

D
Caution
52/100

Jira MCP Server

Supercharge your AI assistant with seamless Jira integration. Enables AI assistants like GitHub Copilot and Claude to interact with your Jira Cloud instance.

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

tezaswiraj7222

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
🚨
Secret credentials may flow to a network call
3 flows detected: JIRA_OAUTH_CLIENT_ID, JIRA_OAUTH_ACCESS_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 2 critical, 12 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 4 credentials: JIRA_API_TOKEN, JIRA_OAUTH_ACCESS_TOKEN, JIRA_OAUTH_CLIENT_SECRET, JIRA_OAUTH_REFRESH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes91 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_boards

Get all Scrum and Kanban boards, optionally filtered by project or type.

jira_get_board

Get details of a specific board including configuration.

jira_get_board_configuration

Get the configuration of a board including columns, estimation, and ranking.

jira_get_sprints

Get sprints for a board, optionally filtered by state.

jira_get_sprint

Get details of a specific sprint.

jira_create_sprint

Create a new sprint on a board.

jira_update_sprint

Update sprint details including name, dates, and goal.

jira_start_sprint

Start a sprint that is in 'future' state.

jira_complete_sprint

Complete an active sprint. Optionally move incomplete issues to another sprint or backlog.

jira_get_sprint_issues

Get all issues in a sprint.

jira_move_issues_to_sprint

Move issues to a sprint.

jira_get_backlog_issues

Get issues in the backlog (not in any active sprint) for a board.

jira_move_issues_to_backlog

Move issues from a sprint back to the backlog.

jira_rank_issues

Change the rank of issues on a board by placing them before or after another issue.

jira_get_attachments

Get all attachments for an issue.

jira_upload_attachment

Upload a file attachment to an issue. Requires the file path on the local filesystem.

jira_get_attachment_metadata

Get metadata for a specific attachment by ID.

jira_get_attachment_content

Get the content/download URL for an attachment. Returns the redirect URL or content depending on redirect setting.

_internal_jira_set_auth

Use when the user wants to connect Jira using Basic Auth (email + API token). This tool should only be called when the user explicitly provides credentials.

jira_oauth_get_auth_url

Generate the OAuth 2.0 authorization URL that the user should visit to grant access. Returns the URL and required state parameter.

jira_oauth_exchange_code

Exchange the authorization code for access tokens after the user has completed the OAuth flow.

jira_oauth_set_tokens

Set OAuth tokens directly if you already have them (e.g., from a previous session or external OAuth flow).

jira_oauth_refresh

Manually refresh the OAuth access token using the refresh token.

jira_oauth_list_sites

List all Jira sites accessible with the current OAuth token.

jira_clear_auth

Use when the user asks to remove or reset stored Jira credentials.

jira_auth_status

Check the current authentication status and type.

jira_bulk_edit_issues

Edit multiple issues at once. Supports bulk editing of labels, assignee, priority, components, and fix versions. Returns a taskId to track progress.

jira_bulk_watch_issues

Add watchers to multiple issues at once. Returns a taskId to track progress.

jira_bulk_unwatch_issues

Remove watchers from multiple issues at once. Returns a taskId to track progress.

jira_get_bulk_operation_progress

Check the progress of an async bulk operation using its taskId.

jira_whoami

Use when the user asks who they are in Jira or wants to verify the Jira account in use.

jira_get_issue
jira_search_issues
jira_search_issues_summary
jira_resolve

Primary routing tool. Use this tool first when the user intent is clear (get issue, search, or my issues) but the exact Jira tool to call is uncertain.

jira_get_issue_summary
jira_get_my_open_issues
jira_get_issue_comments

Use when the user asks for the discussion or comments on a specific ticket; returns a clean list.

jira_add_comment

Use when the user asks to add a comment to a specific ticket; confirm intent before posting.

jira_list_projects

Use when the user asks which Jira projects they can access or wants a list of projects.

jira_get_project

Use when the user mentions a project key and asks for project details or metadata.

jira_create_issue

Create a new Jira issue. Requires project key, issue type, and summary at minimum.

jira_update_issue

Update an existing Jira issue. Only provided fields will be modified.

jira_assign_issue

Assign or unassign a Jira issue to a user.

jira_get_transitions

Get available workflow transitions for an issue. Use before transitioning to see valid options.

jira_transition_issue

Move a Jira issue to a different status by executing a workflow transition.

jira_get_epics

Get epics for a board.

jira_get_epic_issues

Get all issues belonging to an epic.

jira_move_issues_to_epic

Move issues to an epic.

jira_remove_issues_from_epic

Remove issues from their epic (move to no epic).

jira_get_filters

Get saved filters, optionally filtered by name.

jira_get_filter

Get details of a specific filter.

jira_create_filter

Create a new saved filter.

jira_update_filter

Update an existing filter.

jira_get_my_filters

Get filters owned by the current user.

jira_get_favourite_filters

Get filters marked as favourite by the current user.

jira_get_dashboards

Get a list of dashboards. Can filter by favourite or owned dashboards.

jira_search_dashboards

Search for dashboards by name, owner, or other criteria.

jira_get_dashboard

Get details of a specific dashboard by ID.

jira_get_dashboard_gadgets

Get all gadgets on a dashboard.

jira_add_dashboard_gadget

Add a gadget to a dashboard. Provide either moduleKey or uri to specify the gadget type.

jira_get_all_labels

Get all labels used across all issues in the Jira instance.

jira_add_labels

Add, set, or remove labels on an issue. Use 'add' to append, 'set' to replace all, or 'remove' to delete specific labels.

jira_autocomplete_jql

Get autocomplete suggestions for JQL field values. Useful for building JQL queries interactively.

jira_validate_jql

Validate one or more JQL queries for syntax and semantic correctness.

jira_parse_jql

Parse JQL queries and return their abstract syntax tree (AST) structure. Useful for understanding query structure.

jira_get_issue_types

Get available issue types, optionally filtered by project.

jira_get_priorities

Get available priority levels for issues.

jira_get_statuses

Get available statuses, optionally filtered by project.

jira_get_components

Get components for a specific project.

jira_get_versions

Get versions for a specific project.

jira_search_users

Search for Jira users by name, email, or username.

jira_get_changelog

Get the history of changes for an issue.

jira_get_fields

Get all available fields including custom fields.

jira_get_create_metadata

Get metadata for creating issues in a project, including available issue types and their fields. Uses the modern non-deprecated API endpoints.

jira_get_edit_metadata

Get metadata for editing a specific issue, including editable fields.

jira_get_issue_links

Get all linked issues for a specific issue.

jira_create_issue_link

Create a link between two issues.

jira_get_link_types

Get available link types for linking issues.

jira_get_watchers

Get the list of users watching an issue.

jira_add_watcher

Add a user to watch an issue.

jira_remove_watcher

Remove a user from watching an issue.

jira_get_votes

Get the vote count and voters for an issue.

jira_add_vote

Add your vote to an issue.

jira_remove_vote

Remove your vote from an issue.

jira_add_worklog

Use when the user wants to log time/work on a specific Jira ticket. Allows specifying time spent, start date/time, and an optional description.

jira_get_issue_worklogs
jira_get_updated_worklog_ids

Get IDs of worklogs that were created or updated since a specific date/time. Use this to discover worklogs for reporting purposes.

jira_get_worklogs_by_ids

Get full worklog details for a list of worklog IDs. Use after getting IDs from jira_get_updated_worklog_ids.

jira_get_user_worklogs
jira_get_deleted_worklog_ids

Get IDs of worklogs that were deleted since a specific date/time. Useful for audit and sync purposes.

// known CVEs in dependencies2 critical12 high12 low

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

criticalvitest@3.0.0GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

criticalvitest@3.0.0GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

highaxios@1.13.4GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.13.4GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.13.4GHSA-43fc-jf86-j433

Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig

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_ACCEPTANCE_CRITERIA_FIELDCustom field ID for acceptance criteria —
🔐 secretJIRA_API_TOKEN"": "your-api-token"
configJIRA_BASE_URL"": "https://your-domain.atlassian.net",
configJIRA_CLOUD_IDYour Jira Cloud ID ✅
configJIRA_EMAIL"": "your-email@example.com",
🔐 secretJIRA_OAUTH_ACCESS_TOKENAccess token ✅
configJIRA_OAUTH_CLIENT_IDOAuth Client ID ✅
🔐 secretJIRA_OAUTH_CLIENT_SECRETOAuth Client Secret ✅
🔐 secretJIRA_OAUTH_REFRESH_TOKENRefresh token ⬜
// 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

91/91 tools missing one or more hints — jira_get_boards (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jira_get_board (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); jira_get_board_configuration (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +88 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.

Tool handlers catch errors

5/8 tool handlers wrap calls in try/catch (63%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 3/91 tools referenced in tests (3%)

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

Production dependencies are patched

0 critical, 12 high severity in production deps — axios@1.13.4 (high), axios@1.13.4 (high)

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

Dev dependencies

2 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

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 6 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/tezaswiraj7222/jira-mcp?variant=verified)](https://m8ven.ai/mcp/tezaswiraj7222/jira-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 43b32b13f276b92bb9a39cf305971780937d4c6d
code hash: cf2e2eae3770d3ef8210dee7d816a96c78600859f273045df831319131a5b270
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