Azure DevOps MCP Server

Created By
aymenfurtera year ago
Overview

what is Azure DevOps MCP Server?

Azure DevOps MCP Server is a Model Context Protocol (MCP) server designed for Azure DevOps, providing capabilities for work item management.

how to use Azure DevOps MCP Server?

To use the server, you need to build the Docker image and run it with the necessary environment variables, including your Azure DevOps Personal Access Token, organization URL, and project name.

key features of Azure DevOps MCP Server?

  • Search for work items
  • Create new work items
  • Update existing work items
  • Retrieve work item states
  • Simple command-line interface for testing

use cases of Azure DevOps MCP Server?

  1. Managing work items in Azure DevOps projects.
  2. Automating work item creation and updates.
  3. Integrating with development tools like VS Code for enhanced productivity.

FAQ from Azure DevOps MCP Server?

  • What are the prerequisites to run the server?

You need Docker and an Azure DevOps Personal Access Token with appropriate permissions.

  • Can I run the server locally?

Yes! You can build and run the server locally for development and testing purposes.

  • How do I integrate it with VS Code?

You can add specific configurations to your VS Code settings to integrate with the MCP server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aymenfurter
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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)

a day ago