List Jira tickets connected to a Jira Assets object and return object plus ticket details. Use it to trace issues tied to one asset by object ID.
Apache 2.0
741,659 tools. Updated 2026-11-04 07:43
"A server for creating JIRA tickets" matching MCP tools:
- Aggregate raw findings from iSELF, Prometheus, Wazuh, NetworkScanner, and OctoAI by running all five incident detectors without creating tickets.MIT
- Scans Jira tickets and comments to detect leaked secrets like API keys and passwords. Returns a redacted report with no raw secret values.GPL 3.0
- Retrieve all ticket priorities from Autotask to use as filter criteria when searching tickets or as values when creating new tickets.Apache 2.0
- List all ticket priorities from Autotask to find values for filtering or creating tickets.Apache 2.0
- Retrieve all ticket priority values from Autotask to use when filtering or creating tickets.Apache 2.0
Matching MCP Servers
- AlicenseAqualityCmaintenanceEnables semantic search and analysis of customer support tickets. Provides tools to search tickets, analyze the dataset, and retrieve individual tickets using natural language.3MIT
- AlicenseAqualityDmaintenanceEnables creating Jira issues and listing issue types for a Jira Cloud project using Basic Auth credentials.2126 npmApache 2.0
Matching MCP Connectors
Jira MCP Pack
- Melonhelp TicketsOAuth
Read your Melonhelp Tickets help desk: tickets, comments, saved filters and metrics.
- Retrieve external links on a roadmap bar, such as Jira tickets, documents, and designs. Use this to view linked items or show Jira tickets for a bar.MIT
- Retrieve all ticket statuses from Autotask to use for filtering or creating tickets.Apache 2.0
- Retrieve all ticket statuses from Autotask to filter or create tickets.Apache 2.0
- List ticket departments to retrieve the IDs required for creating or moving tickets in Upmind.MIT
- Search across Jira tickets, meeting transcripts, and documentation to answer freeform questions about codebase, architecture, or past decisions. Natural language queries.MIT
- List valid values for JIRA fields like labels, priorities, statuses, issue types, resolutions, and components to use when creating or updating issues.MIT
- Import external content like Jira tickets or Slack threads into a curated context library with YAML metadata for organization.MIT
- Search Jira tickets using JQL queries to retrieve issues matching specific criteria.MIT
- Remove a link between two Jira tickets, regardless of direction. Specify link_type when multiple links connect them to select the right one.MIT
- Retrieve custom attribute definitions for TDX components like tickets, assets, or CIs to enable accurate data entry when creating or updating items with custom fields.MIT
- Creates a link between two Jira tickets, with options for relationship types like 'relates to', 'Blocks', 'Duplicate', or 'Cloners'.MIT
- Retrieve Jira tickets assigned to, reported by, or mentioning you, with filters by status, project, or username.MIT
- Search for Jira tickets in specified projects using text queries to find relevant issues quickly.GPL 2.0
- Move Jira tickets to an active or future sprint by name or ID. Assign tickets to sprints for better planning and tracking.MIT
- Analyzes Jira ticket content and optional project context to provide complete implementation guidance for Optimizely development.MIT