Azure DevOps MCP Server

Created By
RichardChen820a year ago
Overview

what is Azure DevOps MCP Server?

Azure DevOps MCP Server is a Model Context Protocol (MCP) server designed for integrating with Azure DevOps services, allowing users to query repositories, pull requests, and other resources through the MCP interface.

how to use Azure DevOps MCP Server?

To use the server, clone the repository, install the dependencies, set up your Azure DevOps Personal Access Token (PAT), and start the server using npm.

key features of Azure DevOps MCP Server?

  • Standardized interaction with Azure DevOps resources via MCP.
  • Ability to query repositories and pull requests.
  • Integration capability with AI assistants and other tools supporting MCP.

use cases of Azure DevOps MCP Server?

  1. Querying Azure DevOps repositories for information.
  2. Integrating with AI tools to automate DevOps tasks.
  3. Facilitating pull request management through standardized queries.

FAQ from Azure DevOps MCP Server?

  • What are the prerequisites for using the server?

You need Node.js (v16 or higher), npm or yarn, TypeScript, and an Azure DevOps account with a Personal Access Token (PAT).

  • How do I set up the Personal Access Token?

Create a PAT in Azure DevOps with appropriate permissions and set it as an environment variable.

  • Can I integrate this server with other tools?

Yes! The server is designed to be integrated with any tools that support the Model Context Protocol.

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

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago