Agile Analytics local AI connector

Ask Claude, or another assistant that supports the Model Context Protocol (MCP), about your team's Agile Analytics numbers: sprint summary, cycle time, flow efficiency, work in progress, aging and forecast. The connector runs on your own computer, reads Azure DevOps with your own access, and answers with the same numbers the Agile Analytics extension shows, because it runs the extension's own metric code.

It is part of your Agile Analytics subscription: it answers only when the extension is installed in your organisation, the organisation is on its trial or has a valid licence, and a workflow mapping is saved for the project. Nothing is sent to Baytek.

Full guide: https://ado-analytics.baytekdev.com/docs/local-ai-connector/

Before you start

• Node.js 22 or later on your computer (node --version). The connector runs with npx, which comes with Node.js.
• Agile Analytics installed in your Azure DevOps organisation, with a workflow mapping saved for the project you ask about (Configuration → Workflow Mapping in the extension).
• The admin switch on (it is on unless an admin turned it off; see "Turning it off for your organisation" below).

1. Create a personal access token

In Azure DevOps, open User settings → Personal access tokens → New Token. Pick your organisation, an expiry date, and exactly these three scopes:

• Work Items: Read
• Project and Team: Read
• Extension Data: Read

Nothing else is needed. The token only lets the connector read; it cannot change anything.

Where the token goes

• Claude Desktop, on every system: it does not pass your environment variables to connectors, so put the token in the server entry's "env" block as AZURE_DEVOPS_PAT (shown in the example below), and keep that config file readable by your user account only.
• Windows, other assistants (Claude Code, VS Code): set it as a user environment variable named AZURE_DEVOPS_PAT (Start → "Edit environment variables for your account" → New), which keeps it out of config files. Restart your assistant afterwards so it sees the new variable.
• macOS and Linux: desktop assistants do not read your shell profile, so put the token in the server entry's "env" block as AZURE_DEVOPS_PAT (shown in the examples below), and keep that config file readable by your user account only (chmod 600 <file>).

If the connector answers azure-cli-sign-in-required (settings-unreadable before 6.76.1) although the variable is set, your assistant is not passing it to the connector: use the "env" block.

The token stays in the connector's memory. It is never printed, logged or written anywhere.

2. Add the connector to your assistant

The connector starts with:

npx -y @baytekdev/agile-analytics-mcp

Claude Desktop (Settings → Desktop app → Extensions → Edit config, under Local MCP servers; in older versions Settings → Developer → Edit Config. It opens claude_desktop_config.json: add the mcpServers section, keeping anything already in the file, save, then quit Claude Desktop completely, from the tray icon too, and open it again):

{
  "mcpServers": {
    "agile-analytics": {
      "command": "npx",
      "args": ["-y", "@baytekdev/agile-analytics-mcp"],
      "env": { "AZURE_DEVOPS_PAT": "<your token>" }
    }
  }
}

Claude Desktop needs the token in the entry on Windows too: it does not pass your environment variables to the connector. Leave the "env" line out only if you sign in with the Azure CLI.

Claude Code (one command, stored for your user account only):

claude mcp add --scope user agile-analytics -- npx -y @baytekdev/agile-analytics-mcp

On macOS and Linux, pass the token into the entry with -e:

claude mcp add --scope user agile-analytics -e AZURE_DEVOPS_PAT=<your token> -- npx -y @baytekdev/agile-analytics-mcp

On Windows, Claude Code starts npx through `cmd /

... View full README on GitHub