"Finding JIRA MCP to Create and Edit Jira Tickets" matching MCP tools:

• set_jira_linkA

  KaikuA

  Say which issue of the project's own Jira this issue is: its key (ACME-123) or its link on the site. The key is asked of that Jira first — one it does not have, or the token cannot see, is refused. An empty 'jiraKey' removes the link. One Jira issue per issue; the change is a line in the issue's history. Needs a Jira connected to the project and permission to edit the issue.

  Connector

  Destructive

  No auth

• search_jira_issuesA

  IA-QA — 152 QA & Dev Tools for AI AgentsB

  Search Jira using JQL (Jira Query Language). Returns matching issues with key fields. Ideal for finding open bugs, sprint tickets, or issues by label/assignee/component. BYOK — credentials transit in-memory only, never stored.

  ConnectorNo auth

• list_ticketsA

  GoptinA

  List tickets live from Jira / ClickUp with status, assignees, tags, list/sprint, parent, custom fields and linked tickets. Default: open tickets assigned to the user in their current sprint/list. ClickUp: pass list (e.g. "Sprint 102") and scope="anyone" for every ticket in a sprint, include_done for closed statuses.

  ConnectorNo auth

• list_ticketsA

  GoptinA

  List tickets live from Jira / ClickUp with status, assignees, tags, list/sprint, parent, custom fields and linked tickets. Default: open tickets assigned to the user in their current sprint/list. ClickUp: pass list (e.g. "Sprint 102") and scope="anyone" for every ticket in a sprint, include_done for closed statuses.

  ConnectorNo auth

• list_ticket_sync_connectionsA

  AnkraB

  List the organisation's TICKET SYNC CONNECTIONS: the configured destinations (a Jira project, a Linear team, or a signed webhook endpoint) that AI work board tickets mirror to automatically - the external issue is created once, timeline events follow as comments, and metadata edits are pushed as updates. ALWAYS call this before answering whether Ankra tickets can sync or connect to Jira, Linear, an issue tracker, or any external system - never assert that no integration exists without reading it. Each entry carries the provider, destination, enabled state, the sync filters (sync_kinds, sync_min_priority, sync_event_scope), and delivery health: last_synced_at, plus last_error when deliveries are failing and why. Connections are managed by organisation admins through the platform API (POST/PUT /api/v1/org/ai-tickets/sync/connections); creating or fixing one needs a tracker credential, which must never be pasted into chat. Read-only.

  ConnectorOAuth

• set_jira_connectionA

  KaikuA

  Switch a project's Jira connection on or off, keeping its token — and, with 'confluence', whether the same site's Confluence is read too. Off, nothing reads that Jira or writes to it — the issue screen, the agents, the status sync — and issues keep their keys there. Switched on, the held token is asked of the site first and refused with the site's reason if it no longer opens it. Connecting a Jira, or giving a new token — Confluence's own included — is done on the board's Jira sheet (get_jira_connection's 'url'), never here. For whoever administers the project.

  Connector

  Destructive

  No auth

• create_standalone_projectA

  mFlowA

  Create a new standalone project, seeded with default To Do/In Progress/Done statuses. Use this to start tracking work that has no external tracker — for work already in Jira or Trello, use that provider's own tools instead.

  ConnectorOAuth

• hub_send_call_to_jiraA

  DutifyA

  Push a call's extracted tasks into one or more Jira projects under the same cloud. Hub fans the action items out across the listed projects. Requires recordings:write scope AND a Jira integration on the workspace (see `hub_list_integrations`). IMPORTANT: returns boolean — `true` means Hub ACCEPTED the request, NOT that it actually landed in Jira. The vendor push happens async and silently fails on bad cloudId/project/expired tokens. To confirm landing, call `hub_get_call` again and check that `jiraProjectId` is populated.

  Connector

  Destructive

  No auth

• hub_send_call_to_jiraA

  DutifyA

  Push a call's extracted tasks into one or more Jira projects under the same cloud. Hub fans the action items out across the listed projects. Requires recordings:write scope AND a Jira integration on the workspace (see `hub_list_integrations`). IMPORTANT: returns boolean — `true` means Hub ACCEPTED the request, NOT that it actually landed in Jira. The vendor push happens async and silently fails on bad cloudId/project/expired tokens. To confirm landing, call `hub_get_call` again and check that `jiraProjectId` is populated.

  Connector

  Destructive

  No auth

• set_jira_projectA

  Inclusify AccessibilityA

  Use this when the user wants accessibility findings exported from a site to go to a different Jira project, or is setting one up for the first time. WRITES to this website's Inclusify configuration, never to the site itself and never to Jira — it records which project key exports should use, and files no tickets by itself. It CANNOT connect Jira: authorising Atlassian is a browser OAuth flow on the Inclusify panel's Integrations page and no assistant can do it, so this refuses until the workspace is connected. It also cannot list the available projects — ask the user for the project key, or have them read it off the board. REQUIRES CONFIRMATION, because pointing this at the wrong board sends the work to a team that did not ask for it while the team that did sees nothing, and nobody notices until they ask why no tickets were ever raised. The account owner is emailed a record, including the previous key. Needs the PRO plan, matching the panel.

  Connector

  Destructive

  API key

• get_jira_linkA

  KaikuA

  Which issue of the project's own Jira this issue is, and what that Jira says of it now — its summary, status, assignee and link — read with the token the project's administrator connected. 'connected' false means the project has no Jira; 'jira.state' is 'found', 'missing' (no such issue, or one the token cannot see), 'refused' (the token no longer opens the site), 'unreachable', 'off' or 'sealed'. Where the project keeps its statuses in step with that Jira (get_jira_sync), 'sync' says which way and, in 'problem', why the two were left apart: 'conflict' (both moved), 'no_pair_here' / 'no_pair_there' (a status with no pair), 'refused_here' (this project's workflow refused the move), 'no_move' (the site lists no move to the paired status), 'refused_there', 'missing', 'token'. Set the link with set_jira_link.

  ConnectorNo auth

• tm_get_coverage_summaryA

  MCP Server By TestMu AIB

  Test coverage for a project, overall and per folder, computed live from the project's test cases (matches the Test Cases screen). Also answers requirement and traceability coverage: pass jira_id (any Jira issue key, e.g. TE-123: a requirement, user story, epic, ticket or bug) to get that item's test coverage (the test cases linked to it and how many are automated; zero linked cases means uncovered). For a set of requirements, call once per Jira key. A scope with no test cases returns all zeros; a Jira key that does not exist in the connected Jira returns an error.

  ConnectorOAuth

• tm_get_coverage_summaryA

  TestMu AI (formerly LambdaTest)B

  Test coverage for a project, overall and per folder, computed live from the project's test cases (matches the Test Cases screen). Also answers requirement and traceability coverage: pass jira_id (any Jira issue key, e.g. TE-123: a requirement, user story, epic, ticket or bug) to get that item's test coverage (the test cases linked to it and how many are automated; zero linked cases means uncovered). For a set of requirements, call once per Jira key. A scope with no test cases returns all zeros; a Jira key that does not exist in the connected Jira returns an error.

  ConnectorOAuth

• jira_list_projectsA

  JiraA

  List all accessible Jira projects. Returns project keys, names, descriptions, and types. Use before searching to discover available projects.

  ConnectorNo auth

• search_docsA

  docketA

  Searches docket's help articles (how docket works: time tracking, tickets, budgets, invoicing, Jira, AI connections, …) and returns the best matches with a snippet. Read one in full with get_doc.

  ConnectorOAuth

• jira_to_test_suiteA

  IA-QA — 152 QA & Dev Tools for AI AgentsB

  Turn a Jira ticket into a test suite: Gherkin scenarios, E2E steps, API tests, test data and the ambiguities to clarify. Pass the issue object, or Jira credentials to fetch it. It never invents: a thin ticket returns an empty suite with verdict INCOMPLETE_SPEC and the questions to ask. test_suite._gherkin_warnings is a deterministic syntax check. BYOK: your LLM key.

  ConnectorNo auth

• tm_link_jira_issueA

  MCP Server By TestMu AIB

  Link a test case, test run, or a run result (instance) to a Jira issue (requirement / user story / epic / bug) — linked test cases are what give the issue its test coverage and traceability. Linking a result also links its case and run. Requires the Jira integration to be set up for the organization — otherwise a clear "set up Jira first" message is returned.

  ConnectorOAuth

• tm_link_jira_issueA

  TestMu AI (formerly LambdaTest)B

  Link a test case, test run, or a run result (instance) to a Jira issue (requirement / user story / epic / bug) — linked test cases are what give the issue its test coverage and traceability. Linking a result also links its case and run. Requires the Jira integration to be set up for the organization — otherwise a clear "set up Jira first" message is returned.

  ConnectorOAuth

• complete_jira_v1_connections_projects_tasksA

  mcpC

  The tasks in one project: with no since, the ones that are not done; with since (milliseconds), the ones Jira changed after it, oldest first. Each carries task_id, title, notes, status (open, doing or done), assignee, due and updated_at. -- MakeHybrid API plan, GET /jira/v1/connections/{connection_id}/projects/{project_id}/tasks, group jira.

  ConnectorNo auth

• get_linked_jira_commentsA

  KaikuA

  Read the comments of one issue of a project's own Jira (see get_linked_jira_issue), the newest first: who wrote each, when and what, and how many there are in all. Name the project by 'project', or an issue here by 'issue' — then its project's Jira is read, and the issue's own key there is the default. For the people who work in the project; at most 10 reads of the linked Jira a minute per person.

  ConnectorNo auth

• complete_jira_v1_connections_projectsA

  mcpC

  The projects this connection can reach, with the project_id every task call names. Asked of Jira each time, so one added there turns up here. -- MakeHybrid API plan, GET /jira/v1/connections/{connection_id}/projects, group jira.

  ConnectorNo auth