Azure DevOps MCP Server

Created By
Tiberriver256a year ago
An MCP server for Azure DevOps
Overview

What is Azure DevOps MCP Server?

Azure DevOps MCP Server is a Model Context Protocol (MCP) server implementation that allows AI assistants to interact with Azure DevOps APIs through a standardized protocol.

How to use Azure DevOps MCP Server?

To use the server, clone the repository, install dependencies, set up your environment with authentication credentials, and start the server using Node.js.

Key features of Azure DevOps MCP Server?

  • Standardized interaction with Azure DevOps resources for AI assistants.
  • Supports multiple authentication methods including Personal Access Token (PAT) and Azure Identity.
  • Provides tools for managing projects, work items, repositories, and executing DevOps workflows through natural language.

Use cases of Azure DevOps MCP Server?

  1. Automating project management tasks in Azure DevOps.
  2. Enabling AI assistants to create and update work items and pull requests.
  3. Facilitating natural language interactions with Azure DevOps APIs.

FAQ from Azure DevOps MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol that standardizes how AI assistants can interact with various APIs, including Azure DevOps.

  • What are the prerequisites for running the server?

You need Node.js, npm or yarn, and an Azure DevOps account with appropriate access.

  • How can I authenticate with Azure DevOps?

The server supports multiple authentication methods including PAT, Azure Identity, and Azure CLI.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Tiberriver256
Star
226
Language
TypeScript
License
MIT license
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

31 minutes ago