MCP Azure DevOps CLI

Created By
cege7480a year ago
MCP Server wrapping the azure cli devops extension with prompts and better tooling
Overview

what is MCP Azure DevOps CLI?

MCP Azure DevOps CLI is a command-line tool designed to interact with Azure DevOps services, providing a streamlined interface for various operations related to project management, pipeline management, work item tracking, and repository management.

how to use MCP Azure DevOps CLI?

To use the MCP Azure DevOps CLI, install it via npm or from source, authenticate with Azure DevOps, and configure your default organization and project. You can then execute commands to manage projects, pipelines, work items, and repositories.

key features of MCP Azure DevOps CLI?

  • Project Management: Create, list, show, and delete projects and teams.
  • Pipeline Management: Manage pipelines, runs, environments, and variables.
  • Work Item Tracking: Create, update, query, and manage work item relationships.
  • Repository Management: Manage Git repositories, branches, pull requests, and commits.
  • Plugin System: Extend functionality with plugins.

use cases of MCP Azure DevOps CLI?

  1. Automating project management tasks in Azure DevOps.
  2. Managing CI/CD pipelines efficiently.
  3. Tracking and managing work items programmatically.
  4. Handling Git repository operations from the command line.

FAQ from MCP Azure DevOps CLI?

  • What are the prerequisites for using MCP Azure DevOps CLI?

You need Node.js (v14 or higher) and npm (v6 or higher).

  • How do I authenticate with Azure DevOps?

Use the command az-devops login to authenticate, and you can use Personal Access Tokens (PAT) for secure login.

  • Can I extend the functionality of the CLI?

Yes! The CLI supports plugins that can be installed to enhance its capabilities.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cege7480
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