Azure DevOps MCP (Model Context Protocol)

Created By
kevinmeyvaerta year ago
Working implementation of a SSE Server MCP for interfacing with Azure Devops
Overview

What is Azure DevOps MCP?

Azure DevOps MCP (Model Context Protocol) is a reference server implementation that allows AI assistants to interact with Azure DevOps resources programmatically.

How to use Azure DevOps MCP?

To use Azure DevOps MCP, clone the repository, install the dependencies, configure the environment variables, and start the server. You can then interact with Azure DevOps using the provided endpoints.

Key features of Azure DevOps MCP?

  • Integration with Azure DevOps using the official Node.js SDK
  • Support for Model Context Protocol (MCP)
  • Project management operations
  • Work item management
  • Repository operations
  • Code search capabilities

Use cases of Azure DevOps MCP?

  1. Automating project management tasks in Azure DevOps.
  2. Managing work items programmatically.
  3. Performing repository operations and code searches through an AI assistant.

FAQ from Azure DevOps MCP?

  • What are the prerequisites for using Azure DevOps MCP?

You need Node.js (v18 or higher), an Azure DevOps account, and a Personal Access Token (PAT).

  • How do I configure the environment variables?

Copy .env.example to .env and fill in the required variables such as AZURE_DEVOPS_ORG_URL and AZURE_DEVOPS_PAT.

  • Is there a license for Azure DevOps MCP?

Yes, the project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kevinmeyvaert
Star
0
Language
TypeScript
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