Skip to main content
Glama
306,745 tools. Last updated 2026-07-27 04:49

"Using Jira tickets as input for task automation" matching MCP tools:

  • 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
  • Search Jira issues using JQL queries to find specific tickets by project, status, assignee, or custom criteria. Returns issue keys and titles for quick identification.
    MIT
  • Search across Jira tickets, meeting transcripts, and documentation to answer freeform questions about codebase, architecture, or past decisions. Natural language queries.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • Retrieve the linked JIRA issue key and URL for a given task. Check task-JIRA associations without modifying data.
    MIT
  • Use physical HID input to press a key or keyboard shortcut when other automation paths fail.
    MIT
  • Scroll the mouse wheel up or down by specifying a positive or negative delta. Use when other automation paths cannot accomplish the task.
    MIT
  • Types a string as if typed on a physical keyboard (US layout). Use when other automation methods cannot accomplish the task.
    MIT
  • Link two Jira issues with types like Blocks, Relates to, or Duplicate to define relationships between tickets.
    MIT
  • Create a connection between a Karea task and a JIRA issue using the issue key, enabling unified tracking.
    MIT
  • Create Jira tickets such as Story, Task, Bug, or Sub-task by providing project key, summary, and issue type. Optionally add description, labels, due dates, and time estimates.
    MIT
  • Search JIRA issues using JQL queries or simplified filters to find tickets by project, status, assignee, or text content.
    TypeScript
    MIT
  • Retrieve Jira issues by submitting a JQL query to filter and fetch specific results, with options to limit the number of returned entries using the Jira MCP Server.
    MIT
  • Bulk create Jira issues using field dictionaries for multiple entries. Specify issue types like 'Bug', 'Task', or 'Story' as per your Jira instance, and optionally reload created issues.
    MIT