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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

6 hours ago