Azure DevOps MCP Server

Created By
AzureDevOpsAPIa 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, set up your environment with Node.js and Azure DevOps credentials, then configure the server with your organization URL and authentication method (PAT or Azure Identity) to start interacting with Azure DevOps resources.

Key features of Azure DevOps MCP Server?

  • Standardized access to Azure DevOps resources via AI assistants.
  • Support for managing projects, work items, repositories, and pipelines.
  • Natural language execution of common DevOps workflows.
  • Multiple authentication methods for secure access.

Use cases of Azure DevOps MCP Server?

  1. Automating project management tasks through AI.
  2. Integrating AI assistants for enhanced DevOps workflows.
  3. Simplifying access to Azure DevOps resources for developers.

FAQ from Azure DevOps MCP Server?

  • What authentication methods are supported?

The server supports Personal Access Token (PAT), Azure Identity, and Azure CLI for authentication.

  • Is there a guide for troubleshooting authentication issues?

Yes, detailed troubleshooting information is available in the Authentication Guide.

  • Can I contribute to the project?

Yes, contributions are welcome! Please refer to the contributing guidelines in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AzureDevOpsAPI
Star
0
Language
TypeScript
License
MIT license

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)

a day ago