AI assistants (MCP)

Ask your AI assistant how your teams are doing, and it answers from your Agile Analytics data. Agile Analytics has a server for the Model Context Protocol (MCP), the open standard that Claude, Cursor, GitHub Copilot and other assistants use to read from tools. Ask "How is our delivery going?", "Which repositories rest on one person?" or "What did AI-assisted development cost us last month, and what did it save?" and get the answer from your own organisation.

The assistant gets the same numbers the app shows. It can only read, never change anything, and only your organisation's data.

What you need

Go to Settings → AA API Key.

  • An API key. An admin of the organisation creates one with Generate. Treat it like a password: it gives access to your organisation's data.
  • The address. Under Connect an AI assistant the page shows your organisation's address, for example https://api.prod.agileanalytics.cloud/mcp/OF2170/. Copy it with the button next to it.

Connect your assistant

Replace <address> and <API key> in the examples.

Claude Code

claude mcp add --transport http agile-analytics <address> --header "Authorization: Bearer <API key>"

Cursor

Add to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for all projects:

{
  "mcpServers": {
    "agile-analytics": {
      "url": "<address>",
      "headers": { "Authorization": "Bearer <API key>" }
    }
  }
}

Visual Studio Code with GitHub Copilot

Add to .vscode/mcp.json:

{
  "servers": {
    "agile-analytics": {
      "type": "http",
      "url": "<address>",
      "headers": { "Authorization": "Bearer <API key>" }
    }
  }
}

Claude Desktop

Claude Desktop connects to servers with an API key through the mcp-remote bridge. Add to claude_desktop_config.json (Settings → Developer → Edit config) and restart Claude Desktop:

{
  "mcpServers": {
    "agile-analytics": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "<address>",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": { "AUTH_HEADER": "Bearer <API key>" }
    }
  }
}

What the assistant can read

ToolWhat it answers
Health reportThe 0-100 health score per area, the three thirds and the total, and how they developed, for the organisation or one team
ReportsThe latest DORA metrics, sprint flow and predictability, error budgets, or booked hours
SignalsWhat slipped, recovered or went over budget recently
Collaboration riskRepositories nobody active knows any more, repositories resting on one person, and dormant ones
AI adoptionThe share of AI-assisted merge requests, and the AI leaderboard if you have it switched on
AI cost and returnAI spend per tool against the AI-assisted work, and the hours it saved
KudosWho received the most kudos
Teams and peopleYour teams, everyone in the organisation, and what one person works on

The tools follow your plan, as the app does. Error budgets, collaboration risk and AI impact are part of Scale-Up, and the AI leaderboard is part of Enterprise. When you ask about something your plan doesn't include, the assistant says so.

Good to know

  • Read-only. The assistant cannot create, change or delete anything in Agile Analytics.
  • One organisation per key. A key only works for the organisation it was created in, at that organisation's address.
  • Most numbers come from the nightly reports, the same ones the Overview page shows, so they change once a day.
  • Revoke a key in Settings → AA API Key when you no longer need it, or when someone who had it leaves. Assistants using that key lose access right away.
  • Your data goes to the assistant you connect. Answers are sent to the AI assistant you use, under that provider's terms. Only connect assistants your organisation approves of.