Kiwi

Kiwi for Azure Repos

Have the agent on a Kiwi step open an Azure Repos pull request and answer its review threads, through Microsoft's Azure DevOps MCP server.

  • Your agent works in Azure Repos through its own connection. Kiwi does not call Azure Repos and never holds its credentials.
  • A workflow skill can list Azure Repos among the tools it requires. When you supply your agent's available tools to a skill check and Azure Repos is not among them, the check reports SK15-UNSUPPORTED-TOOL.
  • A project Admin can add links to Azure Repos, 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 Azure Repos connection, with report_configuration.
  • The agent submits links to its work in Azure Repos as the step's outputs. People review them, and sign-off stays with the people your workflow names.

What your agent can do in Azure Repos

  • Read files and directories in a repository, list its branches and search its code and commits.
  • Create a branch, then open a pull request and update its title, description or reviewers.
  • Read a pull request's changes and comment threads, reply in a thread and update its status once addressed.
  • Limit the server to the repository tools, or to read-only tools, with the X-MCP-Toolsets and X-MCP-Readonly headers.
  • Sign in with Microsoft Entra ID; Claude Code and Cursor need a custom Entra app registration, and Claude Desktop and Codex use Microsoft's local server instead.

Set up

  1. Connect your agent to Kiwi

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

  2. Connect your agent to Azure Repos

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

    https://mcp.dev.azure.com/{organization}
  3. Example skill

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

    Take the Azure DevOps project, repository and work item from the assignment.
    Push the change to a new branch and open a pull request into the base branch.
    Read the pull request's comment threads and reply to each one you address.
    Submit the pull request URL and the threads you replied to as outputs.
    Voting on and completing the pull request belong to the reviewer.
    If the organization rejects your sign-in, call report_blocker.