[regression] ado mcp server does not work anymore.

[neilghosh]

Describe the bug

The ADO MCP server does not working anymore. It worked in V 354. But now in V 374. It shows in /mcp but does not show at startup nor the tools are recognized

Affected version

0.0.374

Steps to reproduce the behavior

Configure MCP server at ~/.copilot/mcp-config.json

     "ado": {
       "type": "local",
       "command": "npx",
       "tools": ["*"],
       "args": ["-y", "@azure-devops/mcp", "<Org>"]
     }

launch copilot cli.

See there is no ado mcp connected message

Prompt the following "show me tools from ADO MCP"

It would respond there is no ado mcp

Expected behavior

It should say the following in launch

● Configured MCP servers: ado

Additional context

https://github.com/microsoft/azure-devops-mcp

[collinbarrett]

I think I'm seeing this same breakage as well. Confirmed that reverting to 0.0.374 resolves the issue.

[neilghosh]

@collinbarrett You mean reverting to any earlier version. 0.0.374 is the the one I see issues.
However I saw in some PCs the latest 0.0.377 it worked but then did not work in other PCs I have with exact same config.

[collinbarrett]

I think I'm seeing this same breakage as well. Confirmed that reverting to 0.0.374 resolves the issue.

Apologies, my original comment should have said "reverting to 0.0.354 resolves the issue."

Also note that I'm running in programmatic mode in an Azure Pipeline (isolated temporary host) in my use case. And, I'm using the same prompt/model/config in all of the tests below.

This morning, I am seeing ado tool calls work successfully in:

• 0.0.354
• 0.0.355
• 0.0.373
• 0.0.374

Seems like ado tool calls might still be working in the newer versions below, I just don't see them explicitly logged in logs like I did in earlier versions.

• 0.0.375
• 0.0.376
• 0.0.377

(Analyzed by using --log-level debug and --log-level all. Those two log levels seem pretty identical in verbosity.)