Jira is a project management and issue tracking software developed by Atlassian that helps teams plan, track, and manage agile software development projects.
Why this server?
Allows ingestion of content from Jira as a data connector into Graphlit for search and retrieval
Why this server?
Enables searching, creating, updating, and managing Jira issues, including transitions, worklogs, and epic relationships
Why this server?
Provides access to JIRA data including searching issues, retrieving epic children, getting detailed issue information, creating and updating issues, extracting issue mentions, tracking issue relationships, handling file attachments, and transforming JIRA content for AI context windows
Why this server?
Referenced as a separate MCP server available from another repository, indicating integration capabilities with Jira.
Why this server?
Allows interaction with Jira tickets, including listing tickets, viewing details, creating new tickets, adding comments, and updating ticket status through Jira's API.
Why this server?
Provides comprehensive interaction with Jira's API, enabling JQL query execution, ticket management (creation, editing, deletion), project listing, status retrieval, user assignment, and attachment handling capabilities.
Why this server?
Provides tools for interacting with Jira, including getting issues by key, searching issues, creating new issues, assigning and unassigning issues, and editing existing issues. Works with Jira Cloud endpoints and potentially with Jira Data Center.
Why this server?
Provides integration with Jira, allowing viewing and management of projects, boards, sprints, and issues. Capabilities include listing projects, boards, sprints, and retrieving issues from sprints, with plans for additional functionality like issue creation, commenting, and user management.
Why this server?
Allows interaction with JIRA through JQL search queries and retrieving detailed issue information
Why this server?
Allows querying of Jira data by exposing it as relational SQL models through the CData JDBC Driver.
Why this server?
Provides natural language interaction with Jira, supporting project management tasks including project creation, issue and subtask management, issue linking, dependencies tracking, and automated workflows. Offers tools for retrieving, creating, updating, and deleting issues with support for detailed field formatting.
Why this server?
Enables searching Jira issues via JQL, retrieving issue details including status, assignments, and timestamps.
Why this server?
Provides tools for managing Jira Insights (JSM) asset schemas, including CRUD operations for object schemas, object types, and objects, as well as querying objects using Atlassian Query Language (AQL).
Why this server?
Provides integration with Jira to execute JQL queries, create issues, update issues, transition issues, get board sprints, get sprint issues, get current sprints, get epic issues, and get user issues.
Why this server?
Provides tools for retrieving JIRA issue details, allowing AI assistants to directly interact with JIRA issues.
Why this server?
Allows AI assistants to manage Jira issues programmatically, including creating, listing, updating, getting details, deleting issues, and adding comments.
Why this server?
Integrates with Jira to search for active portfolios in teams, create tasks, and manage portfolio status. Provides functionality to work with Jira tickets and filter issues by status.
Why this server?
Supports cross-MCP integration to link project management activities with team communications, allowing for comprehensive tracking of workflows between Mattermost and Jira.
Why this server?
Allows access to Jira issues directly from the IDE, including viewing assigned issues, getting detailed information on specific issues, and converting Jira issues into local tasks.
Why this server?
Integrates with Jira to automate project management tasks including issue creation and updates, sprint tracking, project and board management, and issue search and retrieval
Why this server?
Allows interaction with Jira, providing tools for listing projects, getting issue details, searching issues, managing project members, creating issues with custom fields, and querying sprints with filtering options.
Why this server?
Enables interaction with Jira to query issue details and lists, create and update work items, manage projects, and handle Jira attachments with automated download and organization capabilities.
Why this server?
Allows viewing and managing Jira issues, projects, users, and comments, with capabilities to create, update, and transition issues.
Why this server?
Enables querying Jira issue tracking and project management data via SQL.
Why this server?
Allows querying Jira issues, projects, and workflow data through SQL
Why this server?
Offers access to Jira issue tracking data including tickets, projects, and workflows.
Why this server?
Listed as a supported data source for integration with the MCP server, allowing access to Jira data.
Why this server?
Allows read-only access to Jira projects, issues, and workflows.
Why this server?
Allows SQL-based access to Jira project management and issue tracking data.
Why this server?
Listed as a supported data source for querying Jira issues, projects, and agile boards.
Why this server?
Allows querying Jira projects, issues, and sprints using SQL.
Why this server?
Allows querying Jira project and issue data through SQL interfaces.
Why this server?
Allows access to project management data from Jira including issues, projects, and users.
Why this server?
Provides access to Jira issue tracking data through SQL queries.
Why this server?
Listed as a supported data source for integration through the CData JDBC driver.
Why this server?
Provides read access to Jira issue tracking data through SQL interfaces, enabling natural language querying of project issues and tickets.
Why this server?
Listed as a supported data source in the compatibility table, enabling access to Jira data.
Why this server?
Allows read-only access to Jira project management data, enabling queries for issues, projects, sprints, and other agile resources.
Why this server?
Allows querying Jira issues, projects, and workflows through SQL.
Why this server?
Listed as a supported data source for integration, allowing access to Jira data through the MCP server.
Why this server?
Allows querying of Jira projects, issues and workflows through relational SQL models.
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver
Why this server?
Provides read-only access to Jira data through SQL models, allowing retrieval of information about projects, tickets, issues, and other Jira entities. Users can query live Jira data through natural language questions without writing SQL.
Why this server?
Provides access to Jira project management data including issues, projects, sprints, workflows, and other development tracking information through SQL queries.
Why this server?
Provides tools for interacting with Jira, including fetching and analyzing issues, running JQL queries, and a step-by-step wizard for creating new issues with support for project selection, issue type configuration, and field management.
Why this server?
Integrates with Jira to fetch issue summaries for use in branch names and update issue status when creating branches, allowing for automated workflow transitions when development work begins.
Why this server?
Allows AI assistants to interact with Jira tickets by fetching assigned tickets, adding comments, getting available status transitions, and updating ticket status.
Why this server?
Allows searching, viewing, creating, updating, and deleting Jira issues, as well as managing issue transitions, worklogs, and epic relationships.
Why this server?
Provides tools for interacting with Jira's REST API, enabling project browsing, issue management (viewing, creating, searching), commenting on issues, and transitioning issues through workflows.
Why this server?
Enables interaction with Jira instances through a unified API, providing capabilities for accessing issues, managing tickets, and integrating with Jira workflows.
Why this server?
Integrates with Jira's API to fetch issue details, retrieve assigned tickets, filter issues by type, list projects, get issue types, and track recent changes in tickets, enabling AI-powered Jira ticket management directly within Cursor IDE.
Why this server?
Provides tools for comprehensive JIRA issue management including creating, updating, deleting, and searching issues, managing issue links and relationships, adding comments and attachments, retrieving user information, and accessing field and issue type metadata.
Why this server?
Enables interaction with JIRA instances through the JIRA REST API v3, allowing for the creation and management of JIRA issues with rich markdown formatting, automatic conversion to Atlassian Document Format (ADF), and flexible field management including support for both standard and custom fields.
Why this server?
Enables querying, filtering, and analyzing JIRA issue data stored in CSV files, with tools for listing issues with various criteria, retrieving detailed information for specific issues, and generating project statistics and summaries.
Why this server?
Connects to Jira Cloud or Server/Data Center to generate weekly reports based on issue activity. Supports custom JQL queries, project filtering, and result limiting.
Why this server?
Enables interaction with Jira, allowing users to create tickets, fetch project information, and update Jira dashboards directly through the AI assistant.
Why this server?
Enables retrieving and searching JIRA issues using JQL (JIRA Query Language), with support for configurable field selection, pagination, and logging work on issues.
Why this server?
Allows creation of Jira issues with customizable fields, providing automatic response formatting and schema validation for issue creation.
Why this server?
Enables getting ticket details, searching tickets with JQL, creating new tickets, and adding comments to tickets in Jira.
Why this server?
Provides tools for interacting with JIRA APIs, including searching issues using JQL, listing projects, creating/updating/deleting issues, adding comments, transitioning issues between statuses, and searching for users with GDPR compliance support.
Why this server?
Integrates with Jira ticket numbers, allowing them to be included in Pull Request titles when creating PRs through the GitHub integration.
Why this server?
Enables searching tasks via JQL, creating new tasks, adding comments, managing workflows, time tracking with Tempo, and working with projects and epics
Why this server?
Enables searching issues, getting issue details, listing projects, and more in Jira
Why this server?
Provides tools for searching Jira issues with JQL queries and retrieving detailed information about specific Jira issues, including fields like summary, description, status, and assignee.
Why this server?
Provides tools for managing Jira issues, searches, sprints, and workflows
Why this server?
Allows searching and reading Jira issues through the jira_get_issue tool, which retrieves details of specific Jira issues from Jira Cloud instances
Why this server?
Enables AI models to interact with Jira through its REST API, providing functionality for accessing issue details, sprint information, and workload analytics, with features like connection pooling and rate limiting for optimal performance.