The Jira MCP Server for Cursor is a tool that connects Cursor with Jira, allowing you to manage Jira tickets directly from the Cursor application. This integration simplifies workflow by eliminating the need to switch between applications when working with Jira issues.
The easiest way to install the Jira MCP Server is via Smithery:
npx -y @smithery/cli install @kornbed/jira-mcp-server --client claude
If you prefer manual installation:
npm install
.env
file in the root directory with your Jira credentials:JIRA_HOST=https://your-domain.atlassian.net
[email protected]
JIRA_API_TOKEN=your-api-token
PORT=3000
To obtain your Jira API token:
.env
fileStart the server using one of the following commands:
# Development mode
npm run dev
# Production mode
npm run build
npm start
You can connect the Jira MCP Server to Cursor in two ways:
npm run build
{
"mcpServers": {
"jira": {
"command": "node",
"args": ["/path/to/jira-mcp-cursor/dist/server.js"]
}
}
}
Be sure to replace /path/to/jira-mcp-cursor
with the absolute path to your project.
npm start
{
"mcpServers": {
"jira": {
"url": "http://localhost:3000",
"capabilities": [
"list_tickets",
"get_ticket",
"get_comments",
"create_ticket",
"update_status",
"add_comment"
]
}
}
}
Once configured, you can use the following commands in Cursor:
/jira list
- Show your tickets/jira view TICKET-123
- View details of a specific ticket/jira comments TICKET-123
- See comments on a ticket/jira create
- Create a new ticket/jira comment TICKET-123
- Add a comment to a ticket/jira status TICKET-123
- Update a ticket's statusGET /api/tickets?jql=project=TEST+AND+status=Open
Returns a list of tickets, optionally filtered by JQL query.
GET /api/tickets/TEST-123
Returns detailed information about the specified ticket.
GET /api/tickets/TEST-123/comments
Returns all comments for the specified ticket.
POST /api/tickets
Content-Type: application/json
{
"summary": "New feature request",
"description": "Implement new functionality",
"projectKey": "TEST",
"issueType": "Task"
}
Creates a new Jira ticket with the provided details.
POST /api/tickets/TEST-123/comments
Content-Type: application/json
{
"body": "This is a new comment"
}
Adds a comment to the specified ticket.
POST /api/tickets/TEST-123/status
Content-Type: application/json
{
"transitionId": "21"
}
Updates the status of the specified ticket.
GET /api/tickets/search?searchText=login+bug&projectKeys=TEST,PROD&maxResults=10
Searches for tickets matching the specified text across the given projects.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.