Kiwi
Kiwi

Kiwi for Jira

Have the agent on a Kiwi step read its Jira work item, comment on it and move it to the next status, through the Atlassian Rovo MCP Server.

  • Your agent works in Jira through its own connection. Kiwi does not call Jira and never holds its credentials.
  • A workflow skill can list Jira among the tools it requires. When you supply your agent's available tools to a skill check and Jira is not among them, the check reports SK15-UNSUPPORTED-TOOL.
  • A project Admin can add links to Jira, with notes, under Connections and bind them to the steps that use them. The agent reads them with list_connections.
  • The agent can report the tools and plugins it ran with, including its Jira connection, with report_configuration.
  • The agent submits links to its work in Jira as the step's outputs. People review them, and sign-off stays with the people your workflow names.

What your agent can do in Jira

  • Read a work item by its key and search work items with JQL.
  • Create a work item or edit its fields, for example to record a defect found during the step.
  • List the transitions available to a work item and move it to the next status in its workflow.
  • Comment on a work item, or add a web link from it to the pull request or page the step produced.
  • Link related work items and read the sprint data of a board.

Set up

  1. Connect your agent to Kiwi

    Add Kiwi's hosted MCP server, https://kiwiflow.io/mcp, to your coding agent.

    Coding agentsQuickstart

  2. Connect your agent to Jira

    Add the Jira MCP server to your agent with this URL. The credentials stay with your agent.

    https://mcp.atlassian.com/v2/mcp

    Jira documentation

  3. Example skill

    Publish instructions like these as a workflow skill that lists Jira among its required tools.

    Read the Jira work item key from the run's inputs and fetch the work item.
Implement what it describes, then comment on it with a summary of the change.
Add a web link from the work item to the pull request.
Move it to In Review only when that transition is listed for the work item.
Submit the work item key and the pull request URL as the step's outputs.
Scope changes go to the decision owner named in the assignment.
If the work item is missing or you lack access, call report_blocker.
Get startedRead the setup guide