NEVER commit your Jira API tokens or credentials to version control!
- Always use environment variables or
.envfiles (which are gitignored) - Never hardcode credentials in source code
- Rotate API tokens regularly
- Use minimal permissions required for the integration
- Log in to Atlassian Account Settings
- Click "Create API token"
- Name it appropriately (e.g., "MCP Server - Development")
- Store it securely - you won't be able to see it again
-
Use
.envfile for local developmentcp .env.example .env # Edit .env with your credentials -
Environment Variables for Production
export JIRA_HOST="https://your-company.atlassian.net" export JIRA_EMAIL="[email protected]" export JIRA_API_TOKEN="your-secure-token"
-
Minimal Permissions
- Only grant the Jira permissions your integration needs
- Use project-specific permissions where possible
-
Token Rotation
- Rotate API tokens every 90 days
- Immediately revoke compromised tokens
If you discover a security vulnerability, please report it to the repository maintainers via private message. Do not create public issues for security vulnerabilities.