jira
A TypeScript-based MCP server for Jira integration with Cursor
claude mcp add --transport stdio kornbed-jira-mcp-server node dist/server.js \ --env PORT="Port on which the MCP server will listen (e.g., 3000)" \ --env JIRA_HOST="Your Jira host URL (e.g., https://your-domain.atlassian.net)" \ --env JIRA_EMAIL="Your Jira account email" \ --env JIRA_API_TOKEN="Your Jira API token"
How to use
This Jira MCP Server for Cursor exposes a set of Jira-related operations via the MCP protocol, enabling Cursor to interact with Jira tickets. It supports listing tickets, retrieving ticket details and comments, creating tickets, adding comments, and updating ticket status. The server is designed to work with Cursor using either a command-based integration (via a built-in MCP client) or an HTTP-based integration where Cursor talks to the server over HTTP and requests a defined set of capabilities like list_tickets, get_ticket, get_comments, create_ticket, update_status, and add_comment. After starting the server, you can register the MCP server in Cursor and invoke commands such as /jira list, /jira view TEST-123, /jira create, /jira comment TEST-123, and /jira status TEST-123 to manage Jira issues directly from Cursor.
How to install
Prerequisites:
- Node.js (recommended LTS) and npm installed on your machine
- A Jira account with API access and a valid API token
- Access to the project repository or npm package @kornbed/jira-mcp-server
Installation steps:
- Install dependencies via Smithery (recommended for automatic setup):
npx -y @smithery/cli install @kornbed/jira-mcp-server --client claude
- If not using Smithery, install locally:
npm install
- Create and configure environment variables. Copy the example and fill in your Jira credentials:
cp .env.example .env
Edit the .env file to include:
JIRA_HOST=https://your-domain.atlassian.net
JIRA_EMAIL=your-email@example.com
JIRA_API_TOKEN=your-api-token
PORT=3000
- Build and run the server:
npm run build
npm start
- Alternative development workflow:
npm run dev
- If using the command-based Cursor integration, build first and then configure Cursor to point to the built server executable. If using HTTP integration, ensure the server is running and accessible via the configured port.
Additional notes
Tips and common considerations:
- Ensure your JIRA_HOST, JIRA_EMAIL, and JIRA_API_TOKEN are kept secure and not checked into version control.
- The server exposes REST-like endpoints for Jira operations and MCP protocol support for Cursor integration; choose HTTP-based integration to simplify connections without requiring Cursor to run a local node process.
- If you encounter CORS or network-related issues, verify that the server is reachable at the configured PORT and that Jira API tokens have the necessary scopes.
- When using the command-based integration, provide the absolute path to the built server script in Cursor's MCP configuration.
- The npm_package for this server is @kornbed/jira-mcp-server, which can be used for installation and updates.
Related MCP Servers
iterm
A Model Context Protocol server that executes commands in the current iTerm session - useful for REPL and CLI assistance
mcp
Octopus Deploy Official MCP Server
furi
CLI & API for MCP management
editor
MCP Server for Phaser Editor
DoorDash
MCP server from JordanDalton/DoorDash-MCP-Server
mcp
MCP сервер для автоматического создания и развертывания приложений в Timeweb Cloud