Kiwi for Azure Boards
Have the agent on a Kiwi step read its Azure Boards work item, comment on its progress and link the pull request, through Microsoft's Azure DevOps MCP server.
- Your agent works in Azure Boards through its own connection. Kiwi does not call Azure Boards and never holds its credentials.
- A workflow skill can list Azure Boards among the tools it requires. When you supply your agent's available tools to a skill check and Azure Boards is not among them, the check reports
SK15-UNSUPPORTED-TOOL. - A project Admin can add links to Azure Boards, 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 Boards connection, with
report_configuration. - The agent submits links to its work in Azure Boards 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 Boards
- Read a work item, or several at once, with its comments and revision history.
- Run a saved query or search work items, and list a team's backlog and iterations.
- Create work items, add a child item to a parent and update fields on one or many items.
- Comment on a work item and link it to a pull request or to another work item.
- Connect from an Azure DevOps organization backed by a Microsoft Entra tenant, because organizations that use only Microsoft accounts cannot use the remote server.
Set up
Connect your agent to Kiwi
Add Kiwi's hosted MCP server,
https://kiwiflow.io/mcp, to your coding agent.Connect your agent to Azure Boards
Add the Azure Boards MCP server to your agent with this URL. The credentials stay with your agent.
https://mcp.dev.azure.com/{organization}Example skill
Publish instructions like these as a workflow skill that lists Azure Boards among its required tools.
Read the Azure Boards work item ID from the run's inputs and fetch the item. Add a comment to the work item when you start, with the planned approach. Link the work item to the pull request once it is open. Submit the work item URL and the pull request URL as the step's outputs. Changing the item's iteration or priority is for the assigned product owner. If the work item cannot be read, call report_blocker with its ID.