This guide provides solutions for common issues when using the Jira Cloud MCP Server.
Symptoms:
- "Could not authenticate with Jira" error
- 401 Unauthorized responses
Solutions:
- Verify your API token is correct and not expired
- Regenerate a new token from Atlassian Account Settings
- Confirm the email matches your Atlassian account exactly
- Verify the Jira host URL (e.g., "your-instance.atlassian.net")
Symptoms:
- 403 Forbidden responses
- "User does not have permission" errors
Solutions:
- Verify your Jira account has appropriate permissions
- Check project-specific role assignments
- Verify project key is correct (case-sensitive)
Symptoms:
- 429 Too Many Requests responses
Solutions:
- Add delays between requests
- Batch related operations when possible
- Use pagination efficiently for large result sets
Symptoms:
- Container exits immediately
- Error messages in logs
Solutions:
- Check environment variables are properly set
- Review container logs:
docker logs <container_id>
Symptoms:
- Tools not appearing in MCP tool list
- "Tool not found" errors
Solutions:
- Verify server configuration in MCP settings
- Ensure tool names match exactly in requests
Error Code | Description | Possible Solutions |
---|---|---|
400 | Bad Request | Check request parameters |
401 | Unauthorized | Verify API token |
403 | Forbidden | Check permissions |
404 | Not Found | Verify resource exists |
429 | Too Many Requests | Add delays between requests |
500 | Server Error | Try again later |
Enable debug logs with:
export LOG_LEVEL=debug
For Docker:
docker run -e LOG_LEVEL=debug ...
If issues persist:
- Check GitHub Issues
- File a new issue with error details and reproduction steps