Azure DevOps MCP Server

Created By
NikoMixa year ago
Overview

what is Azure DevOps MCP Server?

Azure DevOps MCP Server is a tool designed to interact with the Azure DevOps Services API, facilitating file operations, repository management, and advanced search functionalities.

how to use Azure DevOps MCP Server?

To use the MCP Server, you need to set up a Personal Access Token in Azure DevOps and configure it in your environment. You can run it using Docker or NPX commands as specified in the setup instructions.

key features of Azure DevOps MCP Server?

  • Automatic branch creation for file operations
  • Comprehensive error handling with clear messages
  • Preservation of Git history during operations
  • Support for batch operations on files
  • Advanced search capabilities for repositories, code, and work items

use cases of Azure DevOps MCP Server?

  1. Managing repositories and files in Azure DevOps projects.
  2. Automating the creation of branches and handling file updates.
  3. Searching for specific code snippets or work items across multiple repositories.

FAQ from Azure DevOps MCP Server?

  • What is a Personal Access Token?

A Personal Access Token is a secure way to authenticate to Azure DevOps services without using your username and password.

  • Can I use this server for multiple Azure DevOps projects?

Yes! You can configure it to work with multiple projects by specifying the project name in your commands.

  • Is there a limit to the number of files I can push at once?

The server supports batch operations, allowing you to push multiple files in a single commit.

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

Recommend Servers

View All
Crevio

a day ago
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)

19 hours ago