Azure DevOps MCP Server by Zubeid Hendricks

Created By
ZubeidHendricksa year ago
MCP Server for the Azure DevOps API, enabling project management, repository operations, and more.
Overview

Azure DevOps MCP Server

Azure DevOps MCP Server is a powerful tool designed for integrating and managing Azure DevOps projects via its API, streamlining project management, repository operations, and other workflows.

How to use Azure DevOps MCP Server?

To use the MCP Server, integrate it with your Azure DevOps setup by following the installation instructions on the project's GitHub page. You can then access various API functionalities that simplify project management tasks.

Key features of Azure DevOps MCP Server?

  • Seamless integration with Azure DevOps API
  • Project management capabilities
  • Repository operations and management
  • Enhanced developer productivity tools

Use cases of Azure DevOps MCP Server?

  1. Automating project management tasks in Azure DevOps.
  2. Managing code repositories efficiently through API interactions.
  3. Integrating custom workflows tailored to development teams.

FAQ from Azure DevOps MCP Server?

  • What is Azure DevOps MCP Server?

It is a server designed to interact with the Azure DevOps API, facilitating project management and repository operations.

  • Is the MCP Server open-source?

Yes! The Azure DevOps MCP Server is open-source and available on GitHub.

  • How can I contact the author?

You can reach out to Zubeid Hendricks via GitHub or email at zubeid.hendricks@gmail.com.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ZubeidHendricks
Star
-
Language
-
License
-

Recommend Servers

View All
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.

3 hours ago
Gpt Scrambler

2 days ago