MCP HEATS UP: AZURE DEVOPS SERVER ARRIVES AS BUILDERS HIT RELIABILITY SNAGS
MCP is spreading fast, with a new Azure DevOps server, but early adopters report shaky connectors and odd app behavior. A new Azure DevOps Remote MCP Server in...
MCP is spreading fast, with a new Azure DevOps server, but early adopters report shaky connectors and odd app behavior.
A new Azure DevOps Remote MCP Server in Microsoft Foundry promises agents direct access to DevOps data, tightening the loop between code and operations DevOps.com. That’s a strong signal that MCP is moving into day-to-day engineering workflows.
At the same time, builders are tripping over rough edges: connectors returning “resource not found” thread, intermittent connection failures against 5.3 thread, “model not found” when using Instant with custom connectors thread, and inconsistent behavior inside Projects thread. Some also report web search disabling after adding Apps to Custom GPTs thread and app-review friction with passwordless logins thread.
If you’re rethinking interfaces, a sober take says keep your stable REST/GraphQL contracts and use MCP as an adapter at the edges The New Stack. That gives teams room to experiment without risking core systems.
MCP adoption is accelerating into mainstream dev tooling, but reliability gaps can burn SLAs if you rush to production.
Keeping your current APIs as the system of record provides stability while you trial MCP-based agents.
-
terminal
Spin up a minimal MCP server and run soak tests (connect/disconnect, retries, timeouts) across Developer Mode and Projects; track error rates and tool-call latency.
-
terminal
Validate auth and product toggles: confirm app behavior with passwordless logins and check whether web search stays enabled after adding Apps.
Legacy codebase integration strategies...
- 01.
Wrap existing REST/GraphQL endpoints behind MCP gradually and keep a feature-flagged fallback to direct APIs.
- 02.
Pin versions and add circuit breakers for connectors; log every tool call and surface failures to on-call.
Fresh architecture paradigms...
- 01.
Design a service layer that exposes capabilities as MCP tools with least-privilege scopes and centralized audit logs.
- 02.
Define SLOs for tool calls up front and choose idempotent operations to simplify retries.