Skip to main content
Glama
jrsaavedra1022

Azure DevOps Classic MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AZDO_PATNoPersonal Access Token for Azure DevOps; exclusive with AZDO_BEARER_TOKEN.
AZDO_PROJECTNoDefault project name or GUID.
AZDO_LOG_LEVELNoLog level: silent, error, or info.error
AZDO_TIMEOUT_MSNoTimeout per attempt in milliseconds, between 100 and 120000.15000
AZDO_MAX_RETRIESNoAdditional retries, between 0 and 3.2
AZDO_BEARER_TOKENNoBearer token for Azure DevOps; exclusive with AZDO_PAT.
AZDO_ORGANIZATIONNoDefault organization; can be overridden per tool.
AZDO_ALLOWED_ORGANIZATIONSNoComma-separated list of allowed organizations; empty allows any accessible organization.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
ado_list_organizationsA

Read Azure DevOps Accounts for an explicit member UUID using the Accounts API. Requires compatible identity credentials/profile permissions; may not work with organization-scoped PATs. Results filtered by organization allowlist.

ado_list_configured_organizationsA

List locally configured organizations; does not discover memberships or verify access.

ado_list_projectsB

Read one page of accessible projects.

ado_list_release_definitionsB

Read one page of Classic Release definitions.

ado_get_release_definitionA

Read safe Classic Release metadata without task bodies or variable values.

ado_list_release_environmentsA

Read environments within a Classic Release definition, not YAML environments.

ado_get_release_variablesA

Read direct variables at definition scope or a selected environment. Secret or unspecified secrecy values are always hidden. Does not resolve variable groups or merge scopes.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation4/5

Most tools are clearly separated by resource type and action, but ado_list_organizations and ado_list_configured_organizations are easy to confuse at a glance despite their distinct descriptions. The remaining release-related tools have clear boundaries.

Naming Consistency5/5

All tools follow a consistent ado_ prefix with a predictable list_* or get_* verb pattern. Naming is uniform, snake_case throughout, and easy to navigate.

Tool Count5/5

Seven tools is a well-scoped size for a focused Azure DevOps Classic Release inspection server. Each tool covers a distinct step in the discovery flow without unnecessary redundancy.

Completeness4/5

The set provides a coherent read-only path from organization discovery to project listing to release definitions, environments, and variables. It lacks write operations and actual release run history, but that appears intentionally out of scope.

Maintenance

ActivityMaintained
ResponsivenessNo issues