Jira MCP Tool for Cursor

What is Jira MCP Tool for Cursor?

A Model Context Protocol (MCP) tool that allows Cursor AI to read Jira issue descriptions and comments directly within your coding environment. It runs inside Cursor and uses basic authentication to connect to a Jira instance.

How to use Jira MCP Tool for Cursor?

Setup involves cloning the repository, creating a .env file with your Jira username and password, installing dependencies (npm install), building the package (npm run build), and registering the tool in Cursor under Settings > MCP Tools by adding a command like node /path/to/cursor-jira-mcp/build/index.js. Once configured, ask Cursor AI natural language queries such as "Show me the description for PROJ-123" to retrieve Jira data.

Key features of Jira MCP Tool for Cursor

• Reads full descriptions of Jira issues
• Retrieves all comments on a Jira issue
• Works with basic authentication credentials
• Integrates seamlessly into Cursor AI
• Supports natural language queries for Jira data

Use cases of Jira MCP Tool for Cursor

• Quickly view Jira issue details without leaving your code editor
• Get comments or feedback from a Jira ticket while troubleshooting
• Retrieve bug descriptions or feature specs inside Cursor AI chat
• Avoid switching between browser tabs when referencing Jira information

FAQ from Jira MCP Tool for Cursor

Can the tool write to or update Jira issues?

No. The tool currently only reads issue descriptions and comments; it does not support creating, editing, or transitioning Jira issues.

What authentication method does it use?

It uses basic authentication with a username and password stored in a .env file. The Jira URL can be configured (e.g., jira.dev.corp.company.com or jira.corp.comapny.com).

In which environments can I use this tool?

It is designed exclusively for Cursor on desktop. It requires a local Node.js installation and a Jira instance accessible from your machine.

How do I test if the tool is working?

You can run npm run start after setup to verify Jira authentication is successful. Also confirm the .env credentials are correct and the Jira URL is reachable.

Does it support public Jira or only corporate instances?

It works with any Jira instance that supports basic authentication, including corporate or on-premises instances. Public Jira (e.g., atlassian.net) may require API tokens instead of passwords; the README does not cover that configuration.