Jira MCP

A Model Context Protocol (MCP) server for interacting with self-hosted Jira instances using Personal Access Token (PAT) authentication.

- ✅ Personal Access Token authentication for self-hosted Jira
- ✅ Create, read, update, and delete Jira issues
- ✅ Search issues using JQL (Jira Query Language)
- ✅ Add and view comments
- ✅ Manage issue assignments
- ✅ List projects and issue types
- ✅ Transition issues between statuses
- ✅ Get current user information

- Node.js 18 or higher
- A self-hosted Jira instance (e.g.,https://jira.domain.com)
- A Jira Personal Access Token

git clone https://github.com/edrich13/mcp-jira-server.git cd mcp-jira-server

{ "mcpServers": { "jira": { "command": "npx", "args": ["-y", "mcp-jira-server"], "env": { "JIRA_BASE_URL": "https://jira.domain.com", "JIRA_PAT": "your-personal-access-token-here" } } } }

{ "mcpServers": { "jira": { "type": "stdio", "command": "node", "args": ["/Users/edrich.rocha/.nvm/versions/node/v22.6.0/bin/mcp-jira-server"], "env": { "JIRA_BASE_URL": "https://jira.domain.com", "JIRA_PAT": "your-personal-access-token-here" } } } }

Create or update.vscode/mcp.jsonin your workspace:

{ "servers": { "jira": { "command": "npx", "args": ["-y", "mcp-jira-server"], "env": { "JIRA_BASE_URL": "https://jira.domain.com", "JIRA_PAT": "your-personal-access-token-here" } } } }

{ "servers": { "jira": { "command": "node", "args": ["/absolute/path/to/mcp-jira-server/build/index.js"], "env": { "JIRA_BASE_URL": "https://jira.domain.com", "JIRA_PAT": "your-personal-access-token-here" } } } }

- JIRA_BASE_URL: The base URL of your self-hosted Jira instance (e.g.,https://jira.domain.com)
- JIRA_PAT: Your Personal Access Token
- JIRA_USER_AGENT(optional): Custom User-Agent header for Jira instances behind reverse proxies (oauth2-proxy, nginx, etc.) that filter requests by User-Agent. If your API requests get redirected to SSO login despite valid PAT, your reverse proxy may require a specific User-Agent to bypass authentication for API clients.

Get details of a specific Jira issue by its key.

- issueKey(string, required): The Jira issue key (e.g., "PROJ-123")

Search for Jira issues using JQL (Jira Query Language).

- jql(string, required): JQL query string
- maxResults(number, optional): Maximum number of results (default: 50)

Search for all open issues in project PROJ assigned to me

- project = PROJ AND status = Open
- assignee = currentUser() AND status != Done
- priority = High AND created >= -7d
- reporter = john.doe AND status IN (Open, "In Progress")

- projectKey(string, required): Project key
- summary(string, required): Issue title/summary
- issueType(string, required): Issue type (e.g., "Bug", "Task", "Story")
- description(string, optional): Detailed description
- priority(string, optional): Priority level (e.g., "High", "Medium", "Low")
- assignee(string, optional): Username to assign to
- labels(array, optional): Array of labels
- components(array, optional): Array of component names
- Custom fields: Any additional parameters prefixed withcustomfield_(e.g.,customfield_10001)

Create a new bug in project PROJ with summary "Login page not loading" and high priority

Create a story in PROJ with custom field customfield_10001 set to "Sprint 1"

- issueKey(string, required): Issue key to update
- summary(string, optional): New summary
- description(string, optional): New description
- assignee(string, optional): New assignee username
- priority(string, optional): New priority
- labels(array, optional): New labels array
- status(string, optional): New status (e.g., "In Progress", "Done")
- Custom fields: Any additional parameters prefixed withcustomfield_(e.g.,customfield_10002)

Update issue PROJ-123 to set status to "In Progress" and assign to john.doe

- issueKey(string, required): Issue key
- comment(string, required): Comment text

Add a comment to PROJ-123 saying "Fixed in latest deployment"

- projectKey(string, required): Project key

Get available issue types for a project.

- projectKey(string, required): Project key

- issueKey(string, required): Issue key
- assignee(string, required): Username to assign to

- issueKey(string, required): Issue key to delete

⚠️ Warning:This action is permanent and cannot be undone.

Get information about the currently authenticated user.

After configuring the server, restart Claude Desktop or VS Code to load the new MCP server.

Search for all issues assigned to me that are not done

Create a new task in project PROJ with summary "Test MCP integration"

- Verify the absolute path in your configuration
- Ensure the server is built (npm run build)
- Check that environment variables are set correctly
- Restart Claude Desktop or VS Code after configuration changes

- Verify your Personal Access Token is still valid
- Check that the token has not expired
- Ensure the token has appropriate permissions
- Verify the JIRA_BASE_URL is correct (no trailing slash)

- Check Jira server logs for detailed error messages
- Verify the Jira API is accessible from your machine
- Ensure your user account has necessary permissions
- Try accessing the REST API directly:https://jira.domain.com/rest/api/2/myself

- "Cannot find module": Runnpm installandnpm run build
- "Connection refused": Check if Jira server is accessible and URL is correct
- "Unauthorized": Verify your Personal Access Token
- "Issue type not found": Usejira_get_issue_typesto see valid types for the project
- API requests redirect to SSO login: Your Jira may be behind a reverse proxy (oauth2-proxy, nginx) that filters by User-Agent. SetJIRA_USER_AGENTenvironment variable to a whitelisted User-Agent string. Contact your system administrator to get the allowed User-Agent value.
- Never commit your Personal Access Tokento version control
- Store tokens securely in configuration files with restricted permissions
- Use tokens with minimal required permissions
- Set expiration dates for tokens
- Rotate tokens regularly
- Monitor token usage in Jira's audit logs

This MCP server uses the Jira REST API v2. For more information about Jira's API:

- Jira REST API documentation:https://your-jira-instance/rest/api/2/
- JQL syntax guide: Check your Jira instance documentation

- MCP Server: Check the logs in Claude Desktop or VS Code
- Jira API: Refer to your self-hosted Jira documentation
- Authentication: Contact your Jira administrator

Contributions are welcome! Please ensure:

- Code follows TypeScript best practices
- All tools are properly documented
- Error handling is comprehensive
- Security best practices are followed

An MCP server for interacting with Jira's REST API to manage projects, issues, and users.

Interact with JIRA to search for issues using JQL and retrieve detailed issue information.

Integrate with JIRA to allow AI assistants to directly interact with JIRA issues.

Integrate Atlassian JIRA into any MCP-compatible application to manage issues and projects.

A server for integrating Jira with Claude, enabling project and issue management. Requires configuration via environment variables.

Interact with Jira projects using natural language.

An MCP server for interacting with the Jira API to manage projects, issues, and workflows.

An MCP server for interacting with Jira projects and issues.

A read-only MCP server for Jira, enabling LLMs to query live Jira data using the CData JDBC Driver.

A Jira integration that allows LLMs to act as project managers and personal assistants for teams.