Create and Publish Azure DevOps MCP Server to the Cursor Marketplace

[natebunton]

Feature Request: Official Azure DevOps Plugin for Cursor (MCP Server)

Summary

Create an official Azure DevOps plugin for Cursor, backed by an MCP server, and publish it to the Cursor Marketplace, similar to the existing Azure plugin.

• Azure plugin: https://cursor.com/marketplace/azure
• Azure plugin source: https://github.com/microsoft/azure-skills
• Cursor plugin docs: https://cursor.com/docs/plugins
• Plugin template: https://github.com/cursor/plugin-template
• Plugin examples: https://github.com/cursor/plugins
• Publish page: https://cursor.com/marketplace/publish

We already have a working custom Azure DevOps MCP server config in Cursor, but need an official, discoverable, MS-owned plugin.

---

Goal

Deliver a Microsoft-maintained Cursor plugin that lets AI agents interact with Azure DevOps:

• Installable from the Cursor Marketplace
• Configurable auth (PAT at a minimum)
• MCP server exposing core Azure DevOps operations

---

Current Custom Setup (Works, But Not Ideal)

We can currently configure a custom MCP server like this:

{ "mcpServers": { "ADO": { "command": "npx", "args": [ "-y", "@azure-devops/mcp@latest", "MYORGNAME", "--authentication", "envvar" ], "env": { "ADO_MCP_AUTH_TOKEN": "••••••••" } } } }

Limitations:

• Not visible in the Marketplace
• Each user has to set it up manually
• Not clearly “officially supported” by Microsoft

---

High-Level Requirements

1. MCP Server Capabilities

Expose tools / resources for common Azure DevOps workflows (using Azure DevOps REST APIs under the hood):

• Work items
  • Get / list / search work items
  • Create work items (bugs, tasks, user stories, etc.)
  • Update fields (state, assignee, tags, links)
• Repos
  • List repositories and branches
  • List / get pull requests
  • Read files and directories
• Pipelines / Builds
  • List builds / pipelines
  • Get build / pipeline status and basic logs/links
  • Trigger reruns where feasible

Implementation details (suggested, not strict):

• Use existing Azure DevOps REST SDKs or direct REST calls
• Map each logical action to an MCP tool with clear, minimal parameters

2. Authentication

• Required (MVP):
  • Support PAT-based auth (Personal Access Token), similar to current custom config
  • Token supplied via env var (e.g., ADO_MCP_AUTH_TOKEN) or Cursor plugin settings
• Optional / future:
  • Support more advanced auth (OAuth / service principals) if compatible with Cursor’s plugin model

Document:

• How to generate PAT
• Required scopes (e.g., work items, code, build)

3. Cursor Plugin Packaging

Create a repo similar to microsoft/azure-skills that:

• Implements an MCP server for Azure DevOps
• Uses the Cursor plugin template as a base:
  • https://github.com/cursor/plugin-template
• Includes:
  • package.json, build scripts, and MCP entrypoint
  • Example cursor.json (or equivalent plugin manifest) for:
    • Command
    • Args
    • Env vars for auth
  • README with:
    • Install + setup
    • Example Cursor prompts and flows
    • Auth configuration (PAT + scopes)

---

Marketplace Integration

Publish an “Azure DevOps” plugin to:

• https://cursor.com/marketplace
• https://cursor.com/marketplace/publish

Requirements:

• Plugin metadata:
  • Name: Azure DevOps
  • Publisher: Microsoft
  • Short description: e.g. “Manage Azure DevOps work items, repos, and pipelines from Cursor.”
• Configuration UI:
  • Input for PAT (stored securely)
  • Organization URL / name
• Link to the GitHub source repo (similar to azure-skills)

---

Example User Flows (What the Agent Should Be Able to Do)

The AI agent in Cursor should be able to:

1. Triage issues

   • Take a natural-language bug description
   • Create a work item in Azure DevOps with:
     • Title, description, area path, iteration, tags, priority, etc.

2. Link code and work items

   • Given a work item ID, find related branches / PRs
   • Summarize status for the user

3. Inspect pipelines

   • Given a build/pipeline name or ID:
     • Fetch latest runs
     • Report success/failure
     • Provide link(s) to full logs in Azure DevOps UI

These flows should be achievable via a small set of well-designed MCP tools.

---

Definition of Done

• MCP server implemented for Azure DevOps with:
  • Work item, repo, and pipeline operations
• Auth via PAT supported and documented
• Plugin repo created under a Microsoft org (similar to microsoft/azure-skills)
• README with:
  • Install / configure steps
  • Example Cursor configuration
  • Required PAT scopes
  • Example tool invocations / prompts
• Plugin published to Cursor Marketplace as “Azure DevOps”
• Basic smoke tests confirming:
  • Connect from Cursor
  • List work items
  • Create a work item
  • Read a repo file
  • Fetch pipeline status

[danhellem]

@natebunton this is not going to be a priority. But I will take a look at the publish requirements and decide from there

[danhellem]

I have reached out to the cursor marketplace to get this started