Jira Mcp

Jira MCP Server

[npm version] [License: MIT] [TypeScript] [Node.js] [MCP] [CI/CD]

The most complete open source Model Context Protocol (MCP) server for Jira & Atlassian. Connect any MCP-compatible AI client to your Jira instance in seconds — manage issues, sprints, comments, transitions, users, and Confluence pages without leaving your AI assistant.

{  "mcpServers": {    "jira": {      "command": "npx",      "args": ["-y", "raalarcon-jira-mcp-server"],      "env": {        "JIRA_HOST": "https://your-domain.atlassian.net",        "JIRA_EMAIL": "[email protected]",        "JIRA_API_TOKEN": "your-api-token"      }    }  }}

Compatible AI Clients

[Open Source Love] [PRs Welcome] [Contributors] [Stars]

Find This Server On

• MCP Market — MCP server marketplace
• MCP Servers — Awesome MCP Servers directory
• Claude Marketplaces — Claude plugins & MCP directory
• npm — npx raalarcon-jira-mcp-server

Features

• ✅ Project Management: List projects and issue types
• ✅ Issue CRUD: Create, read, update and delete issues
• ✅ Comments: Create, read, update and delete comments with enhanced pagination
• ✅ Transitions: Move issues between states
• ✅ Assignments: Assign issues to users
• ✅ User Management: Search and manage users
• ✅ Sprint Management: Complete agile sprint lifecycle management
• ✅ Wiki Integration: Access Confluence pages by URL identifier with HTML to text conversion
• ✅ Rich Text Support: Markdown to ADF conversion for formatted descriptions and comments
• ✅ Validation: Yup schema validation
• ✅ Authentication: Full Jira Cloud support
• ✅ Optimized Responses: Token-efficient field filtering
• ✅ Type Safety: Full TypeScript support

Installation

Option 1: Using npx (Recommended)

The easiest way to use this MCP server is with npx:

1. Configure your MCP client (e.g., Claude Desktop) with this configuration:

{  "mcpServers": {    "jira": {      "command": "npx",      "args": ["-y", "raalarcon-jira-mcp-server"],      "env": {        "JIRA_HOST": "https://your-domain.atlassian.net",        "JIRA_EMAIL": "[email protected]",        "JIRA_API_TOKEN": "your-api-token"      }    }  }}

2. Get your Jira API token (see instructions below)

That's it! The server will be automatically downloaded and run when needed.

Option 2: Local Development

1. Clone the repository:

git clone https://github.com/raalarcon9705/jira-mcp.gitcd jira-mcp

2. Install dependencies:

npm install

3. Build the project:

npm run build

4. Configure your MCP client with the full path to the built server:

{  "mcpServers": {    "jira": {      "command": "node",      "args": ["/full/path/to/jira-mcp/dist/index.js"],      "env": {        "JIRA_HOST": "https://your-domain.atlassian.net",        "JIRA_EMAIL": "[email protected]",        "JIRA_API_TOKEN": "your-api-token"      }    }  }}

Note: Replace /full/path/to/jira-mcp/ with the actual absolute path to your project directory.

Getting API Token

1. Go to Atlassian Account Settings
2. Click "Create API token"
3. Give it a descriptive name
4. Copy the generated token

Usage

Using with npx (Recommended)

Once configured in your MCP client, the server will automatically start when needed. No additional setup required!

Rich Text Support with Markdown

The server now supports automatic Markdown to ADF conversion for issue descriptions and comments. Simply use Markdown syntax and it will be automatically converted to Atlassian Document Format (ADF).

Supported Markdown Elements

• Headers: # H1, ## H2, ### H3
• Text formatting: **bold**, *italic*
• Code: `inline code` and code blocks
• Lists: - bullet lists and 1. numbered lists
• Links: [text](url)
• Blockquotes: > quoted text
• Checkboxes: - [x] completed task

Example Usage

// Create issue with Markdown descriptioncreate_issue({  projectKey: 'PROJ',  summary: 'Bug Report',  description: `# Bug Report
## DescriptionThis is a **critical** bug affecting the login system.
## Steps to Reproduce1. Go to login page2. Enter invalid credentials3. Click login button
## Code Example\`\`\`javascriptfunction login(username, password) {  return authenticate(username, password);}\`\`\`
> **Note**: This bug was reported by multiple users.`,});
// Create comment with Markdowncreate_comment({  issueKey: 'PROJ-123',  body: `## Update
**Status**: Fixed ✅
- [x] Identified root cause- [x] Implemented fix- [x] Tested solution
The issue has been resolved.`,});

Development

npm run dev

Production

npm run buildnpm start

Testing with npx

You can also test the server directly with npx:

# Test the servernpx raalarcon-jira-mcp-server
# Or use with MCP Inspectornpx @modelcontextprotocol/inspector# Then configure: command: "npx", args: ["-y", "raalarcon-jira-mcp-server"]

Available Tools

Projects

get_projects

Retrieves all projects accessible to the authenticated user.

Parameters:

• expand (optional): Additional data to include
• recent (optional): Number of recent projects (0-20)

Response: Array of projects with essential fields:

[  {    "key": "PROJ",    "name": "Project Name",    "id": "10001",    "projectTypeKey": "software"  }]

get_issue_types

Gets all available issue types for a specific project.

Parameters:

• projectKey (required): Project key

Response: Array of issue types with essential fields:

[  {    "id": "10002",    "name": "Task",    "desc": "A small, independent piece of work",    "subtask": false,    "level": 0  }]

Issues

create_issue

Creates a new issue in Jira.

Parameters:

• projectKey (required): Project key
• summary (required): Issue summary
• issueType (required): Issue type (Bug, Story, Task, etc.)
• description (optional): Issue description
• priority (optional): Priority (Highest, High, Medium, Low, Lowest)
• assignee (optional): Assignee account ID
• labels (optional): Array of labels
• components (optional): Array of components
• fixVersions (optional): Array of fix versions
• customFields (optional): Custom field values

Response: Issue PROJ-123 created successfully

get_issue

Gets details of a specific issue (custom fields removed for token efficiency).

Parameters:

• issueKey (required): Issue key (e.g., PROJ-123)
• expand (optional): Additional information
• fields (optional): Specific fields to return

Response: Complete issue object with custom fields filtered out

update_issue

Updates an existing issue.

Parameters:

• issueKey (required): Issue key to update
• summary (optional): New summary
• description (optional): New description
• priority (optional): New priority
• assignee (optional): New assignee
• labels (optional): New labels
• components (optional): New components
• fixVersions (optional): New fix versions
• customFields (optional): Custom fields

Response: Issue PROJ-123 updated successfully

delete_issue

Deletes an issue.

Parameters:

• issueKey (required): Issue key to delete
• deleteSubtasks (optional): Delete subtasks too (default: false)

Response: Issue PROJ-123 deleted successfully

Comments

create_comment

Adds a comment to an issue.

Parameters:

• issueKey (required): Issue key
• body (required): Comment text (supports ADF format)
• visibility (optional): Visibility settings

Response: Comment 12345 created successfully

get_comments

Gets all comments for an issue.

Parameters:

• issueKey (required): Issue key
• startAt (optional): Start index (default: 0)
• maxResults (optional): Max comments (1-100, default: 50)

Response: Optimized comment structure:

{  "total": 5,  "start": 0,  "max": 50,  "items": [    {      "id": "12345",      "author": "John Doe",      "authorId": "account-id",      "created": "2025-01-01T10:00:00.000Z",      "text": "Comment text content"    }  ]}

update_comment

Updates an existing comment.

Parameters:

• issueKey (required): Issue key
• commentId (required): Comment ID
• body (required): New comment text
• visibility (optional): New visibility settings

Response: Comment 12345 updated successfully

delete_comment

Deletes a comment.

Parameters:

• issueKey (required): Issue key
• commentId (required): Comment ID

Response: Comment 12345 deleted successfully

Transitions

get_transitions

Gets available transitions for an issue.

Parameters:

• issueKey (required): Issue key

Response: Array of transitions with essential fields:

[  {    "id": "21",    "name": "In Progress",    "desc": "The assignee is currently working on this activity",    "toName": "In Progress",    "toId": "3",    "available": true,    "category": "In Progress"  }]

transition_issue

Moves an issue to a different state.

Parameters:

• issueKey (required): Issue key
• transitionId (required): Transition ID
• comment (optional): Comment to add during transition
• fields (optional): Additional fields to update

Response: Issue PROJ-123 transitioned successfully

Assignments

assign_issue

Assigns an issue to a user.

Parameters:

• issueKey (required): Issue key
• assignee (required): User account ID

Response: Issue PROJ-123 assigned successfully

get_users

Searches for users in Jira.

Parameters:

• query (optional): Search query by name or email
• projectKey (optional): Filter by project access
• maxResults (optional): Max users (1-100, default: 50)

Response: Array of users with essential fields:

[  {    "id": "account-id",    "name": "John Doe",    "email": "[email protected]",    "active": true,    "type": "atlassian"  }]

get_current_user

Gets information about the current authenticated user.

Response: Current user with essential fields:

{  "id": "account-id",  "name": "Current User",  "email": "[email protected]",  "active": true,  "timezone": "America/New_York",  "type": "atlassian"}

Sprint Management

get_agile_boards

Gets all agile boards available in the Jira instance. Required to find board IDs for sprint operations.

Parameters:

• projectKey (optional): Filter boards by project
• boardType (optional): Filter by type (scrum, kanban)

Response: Array of boards with essential fields:

[  {    "id": 191,    "name": "DreamStar Board",    "type": "scrum",    "projectKey": "DRMSTR",    "projectName": "DreamStar"  }]

get_sprints

Gets all sprints for a specific board. Returns sprint information including ID, name, state, and dates.

Parameters:

• boardId (required): The ID of the board to get sprints from
• state (optional): Filter sprints by state (active, closed, future)

Response: Array of sprints with essential fields:

[  {    "id": 387,    "name": "DRMSTR Sprint 1",    "state": "active",    "startDate": "2025-09-15T14:05:37.511Z",    "endDate": "2025-09-26T05:00:00.000Z",    "goal": ""  }]

create_sprint

Creates a new sprint. Sprint name and origin board ID are required. Start date, end date, and goal are optional.

Parameters:

• name (required): Name of the sprint to create
• originBoardId (required): ID of the board where the sprint will be created
• startDate (optional): Start date of the sprint (ISO 8601 format)
• endDate (optional): End date of the sprint (ISO 8601 format)
• goal (optional): Goal or objective of the sprint

Response: Created sprint with essential fields:

{  "id": 421,  "name": "DRMSTR Sprint 3",  "state": "future",  "goal": ""}

update_sprint

Updates sprint information (name, dates, goal, state). Only provided fields will be updated. For closed sprints, only name and goal can be updated.

Parameters:

• sprintId (required): ID of the sprint to update
• name (optional): New name for the sprint
• startDate (optional): New start date (ISO 8601 format)
• endDate (optional): New end date (ISO 8601 format)
• goal (optional): New goal or objective for the sprint
• state (optional): New state (future, active, closed)

Response: Sprint 421 updated successfully

close_sprint

Closes and completes a sprint. This action requires the sprint to be in the "active" state. Once closed, the sprint cannot be reopened.

Parameters:

• sprintId (required): ID of the sprint to close

Response: Sprint 421 closed successfully

delete_sprint

Deletes a sprint. Once deleted, all open issues in the sprint will be moved to the backlog. This action is irreversible.

Parameters:

• sprintId (required): ID of the sprint to delete

Response: Sprint 421 deleted successfully. All open issues moved to backlog.

move_issue_to_sprint

Moves an issue to a specific sprint. Returns a confirmation message. Issues can only be moved to open or active sprints.

Parameters:

• issueKey (required): Key of the issue to move (e.g., "PROJ-123")
• sprintId (required): ID of the sprint to move the issue to

Response: Issue PROJ-123 moved to sprint 421 successfully

get_sprint_issues

Gets all issues for a given sprint. Returns a list of essential issue details (key, summary, status, assignee, priority).

Parameters:

• sprintId (required): ID of the sprint
• maxResults (optional): Maximum number of issues to return (1-100, default: 50)

Response: Array of issues with essential fields:

[  {    "key": "DRMSTR-1",    "summary": "Implement user authentication",    "status": "In Progress",    "assignee": "John Doe",    "priority": "High"  }]

Response Optimization

The server is optimized for token efficiency:

• Essential Fields Only: Returns only necessary fields for each operation
• Custom Fields Filtered: Automatically removes custom fields from issue responses
• Short Field Names: Uses abbreviated field names (e.g., desc instead of description)
• Success Messages: Clear, concise success confirmations
• Structured Data: Consistent response formats across all tools

Error Handling

The server includes robust error handling with descriptive messages. Common errors include:

• Authentication: Invalid or expired credentials
• Permissions: Insufficient permissions for the operation
• Validation: Invalid input data
• Resources: Issues or projects not found
• API: Rate limits or Jira server errors

Development

Project Structure

src/├── index.ts              # Main MCP server├── jira-client.ts        # Jira API client├── schemas/│   └── index.ts          # Yup validation schemas└── tools/    ├── projects.ts       # Project tools    ├── issues.ts         # Issue tools    ├── comments.ts       # Comment tools    ├── transitions.ts    # Transition tools    ├── assignments.ts    # Assignment tools    └── sprints.ts        # Sprint management tools

Adding New Features

1. Create validation schema in src/schemas/index.ts
2. Implement method in src/jira-client.ts
3. Create MCP tool in appropriate file in src/tools/
4. Register tool in src/index.ts

Testing

Using MCP Inspector (Recommended)

1. Install MCP Inspector:

   bash

   npm install -g @modelcontextprotocol/inspector

2. Build the project:

   bash

   npm run build

3. Start MCP Inspector:

   bash

   npx @modelcontextprotocol/inspector

4. Configure your server in the inspector interface:

   • Transport: STDIO (default)
   • Command: node
   • Args: build/index.js
   • Environment: Add your Jira credentials

Alternative Testing Methods

CLI Mode (for automation and scripting):

# List available toolsnpx @modelcontextprotocol/inspector --cli node build/index.js --method tools/list
# Call a specific toolnpx @modelcontextprotocol/inspector --cli node build/index.js --method tools/call --tool-name get_projects

Configuration File (for complex setups):

{  "mcpServers": {    "jira-server": {      "command": "node",      "args": ["build/index.js"],      "env": {        "JIRA_HOST": "https://your-domain.atlassian.net",        "JIRA_EMAIL": "[email protected]",        "JIRA_API_TOKEN": "your-api-token"      }    }  }}

Claude Desktop: Configure MCP servers directly in Claude Desktop for real-world testing

Advanced Configuration

Environment Variables (for advanced users):

# Jira configurationexport JIRA_HOST="https://your-domain.atlassian.net"export JIRA_EMAIL="[email protected]"export JIRA_API_TOKEN="your-api-token"
# Timeout settingsexport MCP_SERVER_REQUEST_TIMEOUT=60000export MCP_REQUEST_TIMEOUT_RESET_ON_PROGRESS=false
# Proxy settings (if using MCP Proxy)export MCP_PROXY_FULL_ADDRESS=http://localhost:5577
# Auto-open browserexport MCP_AUTO_OPEN_ENABLED=true

Query Parameters (for direct testing):

http://localhost:6274/?transport=stdio&serverCommand=node&serverArgs=build/index.js

Manual Testing

# Build and run the servernpm run buildnpm start

Wiki

query_wiki

Accesses Confluence pages by URL identifier and returns formatted content.

Parameters:

• query (required): Page code to search for (like F4CjNw)

Response: Markdown-formatted page content with metadata:

# Page Title
**ID:** 933462039**Space:** Orderbahn Team (OT)**URL:** /spaces/OT/pages/933462039/...**Author:** User Name**Last Modified:** 2025-09-26T16:35:30.695Z**Code:** F4CjNw
## Content
[Page content in plain text with preserved line breaks]
## Page Hierarchy
- Parent Page (page)  - Child Page (folder)    - Current Page (page)

Features:

• Automatic redirect following for short URLs
• HTML to plain text conversion preserving structure
• Page hierarchy display
• Comprehensive error handling

Contributing

We welcome contributions to the Jira MCP Server! Please follow these guidelines to ensure a smooth contribution process.

Getting Started

1. Fork the repository on GitHub
2. Clone your fork locally:
   bash

   git clone https://github.com/raalarcon9705/jira-mcp.gitcd jira-mcp

3. Install dependencies:
   bash

   npm install

4. Create a new branch for your feature:
   bash

   git checkout -b feature/your-feature-name

Development Workflow

Setting Up Your Environment

1. Install MCP Inspector (official testing tool):

   bash

   npm install -g @modelcontextprotocol/inspector

2. Build the project:

   bash

   npm run build

3. Test with MCP Inspector:

   bash

   npx @modelcontextprotocol/inspector

   Then configure your server:

   • Transport: STDIO
   • Command: node
   • Args: build/index.js
   • Environment: Add your Jira credentials

Code Standards

• TypeScript: All code must be written in TypeScript
• Type Safety: Avoid any types, use proper Jira.js types
• Error Handling: Include comprehensive error handling
• Validation: Use Yup schemas for input validation
• Comments: Add clear comments for complex logic
• Formatting: Follow existing code style and formatting

Adding New Features

1. Create validation schema in src/schemas/index.ts:

   typescript

   export const yourFeatureSchema = yup.object({  // Define your schema});

2. Implement API method in src/jira-client.ts:

   typescript

   async yourFeature(input: YourFeatureInput) {  try {    // Implementation  } catch (error) {    throw new Error(`Failed to your feature: ${error.message}`);  }}

3. Create MCP tool in appropriate file in src/tools/:

   typescript

   {  name: 'your_tool',  description: 'Clear description of what the tool does',  inputSchema: {    // Define input schema  }}

4. Register tool in src/index.ts:

   typescript

   // Add to appropriate handler

5. Optimize response for token efficiency:

   • Return only essential fields
   • Use short field names
   • Filter out unnecessary data

Testing Your Changes

1. Build the project:

   bash

   npm run build

2. Test with MCP Inspector:

   bash

   npx @modelcontextprotocol/inspector

   • Configure server: STDIO, node build/index.js
   • Test all affected tools
   • Verify responses are optimized

3. Test with CLI mode (for automation):

   bash

   # List toolsnpx @modelcontextprotocol/inspector --cli node build/index.js --method tools/list
   # Test specific toolnpx @modelcontextprotocol/inspector --cli node build/index.js --method tools/call --tool-name get_projects

4. Verify response optimization:

   • Check that only essential fields are returned
   • Ensure field names are shortened
   • Confirm custom fields are filtered out

Pull Request Process

Before Submitting

• Code compiles without TypeScript errors
• All tools work as expected
• Response optimization is implemented
• Error handling is comprehensive
• Documentation is updated if needed
• No personal data is included in examples

Creating a Pull Request

1. Commit your changes with clear messages:

   bash

   git add .git commit -m "Add new feature: brief description"

2. Push to your fork:

   bash

   git push origin feature/your-feature-name

3. Open a Pull Request on GitHub with:

   • Clear title describing the change
   • Detailed description of what was added/changed
   • Testing instructions for reviewers
   • Screenshots if UI changes are involved

Pull Request Template

## Description
Brief description of the changes
## Type of Change
- [ ] Bug fix- [ ] New feature- [ ] Breaking change- [ ] Documentation update
## Testing
- [ ] All existing tests pass- [ ] New functionality tested- [ ] Response optimization verified
## Checklist
- [ ] Code follows project standards- [ ] Self-review completed- [ ] Documentation updated- [ ] No personal data included

Code Review Process

1. Automated checks will run on your PR
2. Maintainers will review your code
3. Address feedback promptly
4. Make requested changes and update the PR
5. PR will be merged once approved

Reporting Issues

When reporting bugs or requesting features:

1. Check existing issues first
2. Use the issue template provided
3. Include reproduction steps for bugs
4. Provide clear description for feature requests
5. Include relevant logs and error messages

Development Guidelines

Response Optimization

• Essential fields only: Return only necessary data
• Short field names: Use abbreviated names (e.g., desc instead of description)
• Filter custom fields: Remove customfield_* from issue responses
• Consistent format: Maintain uniform response structure

Error Handling

• Descriptive messages: Include context in error messages
• Proper error types: Use appropriate error types
• Logging: Add console.error for debugging
• User-friendly: Make errors understandable for end users

Documentation

• Update README: Add new tools to documentation
• Include examples: Provide usage examples
• Response format: Document response structure
• No personal data: Use generic examples only

Community Guidelines

• Be respectful and constructive in discussions
• Help others learn and contribute
• Follow the code of conduct
• Ask questions if you need help

Getting Help

• GitHub Issues: For bugs and feature requests
• Discussions: For questions and general help
• Documentation: Check existing docs first
• Code examples: Look at existing implementations

Thank you for contributing to the Jira MCP Server! 🚀

🤝 Contributing

We welcome contributions from the community! This project is open source and we value all contributions.

Quick Start for Contributors

1. Fork the repository on GitHub
2. Clone your fork:
   bash

   git clone https://github.com/your-username/jira-mcp.gitcd jira-mcp

3. Install dependencies:
   bash

   npm install

4. Create a branch for your feature:
   bash

   git checkout -b feature/your-feature-name

5. Make your changes and test them
6. Submit a pull request

Ways to Contribute

• 🐛 Report bugs using our bug report template
• ✨ Request features using our feature request template
• 💻 Submit code improvements and new features
• 📚 Improve documentation and examples
• 🧪 Add tests for better coverage
• 🌍 Translate documentation to other languages

Development Guidelines

• Follow our Contributing Guide
• Read our Code of Conduct
• Use TypeScript for all new code
• Add tests for new functionality
• Update documentation as needed

Getting Help

• 💬 Discussions: Use GitHub Discussions for questions
• 🐛 Issues: Use GitHub Issues for bugs and feature requests
• 📖 Documentation: Check the README and CONTRIBUTING.md

Publishing to npm

To publish this MCP server to npm for distribution:

1. Login to npm:

   bash

   npm login

2. Run the publish script:

   bash

   ./publish.sh

3. Or publish manually:

   bash

   npm run buildnpm publish

The package will be available as raalarcon-jira-mcp-server and users can install it with:

npx raalarcon-jira-mcp-server

License

MIT

Support

To report bugs or request features, please open an issue in the repository.

Note: This MCP server is designed to work with Jira Cloud. For Jira Server/Data Center, additional modifications are required for authentication and some endpoints.