Azure DevOps (local) logo

Azure DevOps (local)

Beta

Microsoft's Azure DevOps server works with work items, repositories, pull requests, pipelines, wikis and test plans using the developer's own sign-in.

  • Developer Tools
  • Local
Runs
On the developer's Mac
Launched with
npx
Platform
macOS
Publisher
Microsoft

How it works

Every agent request passes through Ferentin policy before it reaches Azure DevOps (local).

It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y @azure-devops/mcp.

Ferentin's endpoint agent finds Azure DevOps (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.

  1. AI agentAsks for something
  2. Ferentin policies
  3. Azure DevOps (local) MCP serverRuns on the developer's Mac
  4. Governed resultChecked, logged, returned

About Azure DevOps (local)

Microsoft's Azure DevOps server works with work items, repositories, pull requests, pipelines, wikis and test plans using the developer's own sign-in.

Frequently asked about Azure DevOps (local)

How do I connect Azure DevOps (local) to Ferentin?
Enroll your Macs with the Ferentin endpoint agent, then add Azure DevOps (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
Is the Azure DevOps (local) integration generally available?
The Azure DevOps (local) integration is currently beta on Ferentin.