Search for:
Why this server?
Specifically mentions integration with JIRA and supports both Atlassian Cloud and Server/Data Center deployments, suggesting it can fetch JIRA tickets.
Why this server?
TypeScript implementation with features for JIRA ticket creation and TODO management. This aligns with the request to find and pull down JIRA tickets.
Why this server?
A Python-based server designed for interaction with JIRA, making it suitable for managing and interacting with projects and tickets through custom APIs.
Why this server?
Specifically designed to interact with JIRA issues, currently offering the ability to retrieve issue details, indicating potential for future expansion to attachment access.
Why this server?
Offers file conversion tools. This is useful for handling attachments and potentially converting images for reference.
Why this server?
Allows running JavaScript/TypeScript code, which could be useful for custom logic related to image processing or interacting with the JIRA API beyond what's directly offered.
Why this server?
Allows running Python code and accessing websites. Could be used to interact with JIRA's API and process image data from attachments.
Why this server?
While focused on GitHub, it allows interaction with repositories and issue tracking, suggesting potential for integration with JIRA tickets in some workflows (e.g., linking commits to JIRA tickets).
Why this server?
Similar to GitHub Enterprise MCP Server, offers comprehensive GitHub operations including file management and issue tracking.