Best for
- Organizations using Atlassian Jira Data Center
- Teams that want to manage Jira issues via AI assistants
- Users needing on-premise or private integration with Jira
A
Atlassian Dc MCP Jira
Community
MCP server for Atlassian Jira Data Center
GitHub source repository ↗
60FMRS · C
A functional MCP server for integrating Jira Data Center with AI assistants. It provides clear configuration guidelines and secure credential storage. However, it is not official, and the tool names are not explicitly documented in the source.
This is a community-maintained MCP server for connecting to an Atlassian Jira Data Center instance. It allows search, view, and create issues. Authentication uses Personal Access Tokens (PAT). It is designed for self-hosted Jira Data Center environments. Note: This project is not affiliated with or endorsed by Atlassian.
Tools
The tool list has not been reviewed yet.
Setup
- Ensure Node.js 18+ and npm 7+ are installed.
- Run the quick setup:
npx @atlassian-dc-mcp/jira setupwhich will prompt for host, API base path, and token, and validate them before saving. - Alternatively, configure environment variables: set
JIRA_HOST(orJIRA_API_BASE_PATH) andJIRA_API_TOKEN. - Add the server to your MCP client configuration as shown in the README.
- Optionally, use a shared config file via
ATLASSIAN_DC_MCP_CONFIG_FILE.
claude_desktop_config.json
{
"mcpServers": {
"atlassian-jira-dc": {
"command": "npx",
"args": [
"-y",
"@atlassian-dc-mcp/jira"
],
"env": {
"JIRA_HOST": "your-jira-host",
"JIRA_API_TOKEN": "your-token"
}
}
}
}
Fit and risk
Not for
- Users of Jira Cloud (non-Data Center)
- Those requiring official support or warranty
- Users without a Jira Data Center instance or API token
Required permissions
- Requires a Jira Personal Access Token (PAT)
- Permissions depend on token scopes configured in Jira
- Typically needs read permissions for viewing issues and write permissions for creating
Risks and side effects
- Token could be leaked if stored in plain text config files
- Community-maintained project may lack timely security updates
- Overprivileged PATs could pose risks to the Jira instance
Troubleshooting
- Verify that `JIRA_HOST` or `JIRA_API_BASE_PATH` are set correctly without protocol or API path suffixes
- Test token validity using `npx @atlassian-dc-mcp/jira setup --non-interactive`
- If using a shared config file, ensure the path is absolute and the file exists
- Check network connectivity to the Jira instance
Use cases
Search for Jira issues
View issue details
Create new issues
Supported clients
Claude DesktopFull support
Claude CodeFull support