What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
An Azure DevOps MCP failure can occur at several different layers: the process may not start, the client may be unable to connect, sign-in may fail, authorization may be denied, tools may be filtered out, or a tool may return no data. The fastest fix is to identify the first layer that fails, then use the matching remote or local procedure. Azure DevOps Services is covered here; Azure DevOps Server (on-premises) is not supported by Microsoft’s remote or local MCP server.
Start with the symptom
Record the client name and version, whether you configured a hosted remote server or a local package, the complete error text, and the relevant MCP output log. Then match what you see to this table.
| Symptom | Likely layer | First action |
|---|---|---|
| Server not found, refused connection, URL error or timeout | Transport or network | Check the remote URL and HTTP type, or the local executable and arguments. |
| No sign-in prompt or an OAuth error | Authentication | Use Entra OAuth for remote; choose a supported local method for headless environments. |
AADSTS message or access denied |
Identity, consent or authorization | Apply the action for the exact AADSTS code, then verify organization and project permissions. |
| Client says connected but no tools appear | Tool loading or filtering | Check agent mode, tool filters, duplicate definitions and the client’s MCP tool list. |
| Tools run but return nothing | Resource, project or permission scope | Use the correct organization, project and resource identifiers and test a read-only query. |
| Assistant fails before any tool call | Client orchestration | Restart the assistant; if it persists, use the client provider’s diagnostics. |
Choose the correct server mode
Hosted remote server
The hosted service uses Streamable HTTP. Configure the organization-specific endpoint as https://mcp.dev.azure.com/{organization}, replace the placeholder with only your organization name, and set the server type to http. It uses Microsoft Entra ID OAuth, not a personal access token (PAT). The organization must be Entra-backed, and the client must support the required authentication flow.
Free tools Windows power users keep installed
One-click scans. No signup required.
A root endpoint without an organization is a special case: the organization then has to be supplied in every tool call. Guests should use the organization-specific URL. Microsoft documents remote setup as requiring no local installation, but it is usable only by clients that support this Entra flow. Microsoft’s current guidance says Codex and Claude Desktop do not support the hosted flow; its setup guidance uses a local stdio configuration for Codex. Recheck Microsoft’s current compatibility list because client support can change.
#1 Best Overall
Local stdio package
The local server runs over stdio and is normally launched with Node.js and npx:
npx -y @azure-devops/mcp <organization>The maintainer troubleshooting guide asks you to verify Node.js 20 or later when installation fails. Local authentication options include interactive OAuth, a PAT supplied through an environment variable, and Azure CLI authentication. A local process can display “Connected” even though interactive OAuth cannot finish in WSL2, SSH, Docker, CI or another headless environment.
Do not combine the remote HTTP configuration with the local command, and do not define the same local server in both a project mcp.json and VS Code settings. Duplicate definitions can cause duplicate-server or tool-limit problems. After editing the MCP configuration, reload or restart the client.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsFix remote connection and startup errors
- Correct the endpoint. Use
https://mcp.dev.azure.com/{organization}; do not put a project name, collection name or trailing command in the organization slot. Settypetohttp. - Check HTTPS reachability. Corporate proxies, firewalls and VPN policies must permit outbound HTTPS to
mcp.dev.azure.com. A browser test alone does not prove that the MCP client can use the endpoint through its own proxy settings. - Confirm client support. The remote service requires an Entra OAuth flow. Microsoft’s remote troubleshooting page states: “Non-Microsoft clients can’t authenticate with the remote MCP Server because Microsoft Entra ID doesn’t currently support dynamic client registration, which these clients require.” Use a client documented as compatible, or switch to the local server.
- Complete Entra sign-in. The account must be Entra-backed and able to access the Azure DevOps organization. If a remote VS Code session is headless or its browser redirect is stuck, clear stale VS Code credentials and reload the window before trying again.
- Check guest access. A guest needs membership in the tenant and appropriate Azure DevOps and project permissions. Use the organization-specific endpoint rather than the root endpoint.
If the Azure DevOps MCP enterprise application is missing from the tenant, Microsoft’s procedure requires an administrator to create its service principal with Azure CLI. This is a tenant administration task, not a client-side startup change.
Fix local installation and launch failures
- Install or verify Node.js 20 or later.
- Run
npx -y @azure-devops/mcp <organization>manually to expose package or argument errors. - Make sure the configured command is
npx, the package name is exact, and the organization argument is present and spelled correctly. - Ensure the client points at the intended configuration file. Remove a duplicate definition from either project
mcp.jsonor VS Code settings. - Restart or reload the MCP client after every configuration change.
For a headless local environment, use one of the non-browser methods documented by the maintainer. With a PAT in an environment variable, set ADO_MCP_AUTH_TOKEN and launch with --authentication envvar. With Azure CLI, sign in using az login, select the correct account and launch with --authentication azcli. These flags belong to the local package; they do not turn the hosted remote server into a PAT-authenticated service.
Example local definitions
The exact JSON wrapper differs by client, but the essential local shape is a command plus arguments:
{
"command": "npx",
"args": ["-y", "@azure-devops/mcp", "contoso"]
}For PAT mode, pass the authentication argument in the client’s argument list and provide ADO_MCP_AUTH_TOKEN through its environment configuration. Never commit that token to a repository or paste it into a shared configuration file.
Resolve authentication and authorization errors
Interpret the exact AADSTS code
- AADSTS50076: multifactor authentication is required. Complete the tenant’s MFA challenge.
- AADSTS700016: the application was not found in the tenant. An administrator may need to add or consent to the enterprise application.
- AADSTS65001: consent is missing. Grant the required consent according to your organization’s policy.
- AADSTS50105: the user is not assigned to the application. Ask an administrator to assign the account or group.
Do not infer the remedy from the “AADSTS” prefix alone. Follow the action for the complete code, then verify that the signed-in account belongs to the Azure DevOps organization, is a member of the needed project and can read the requested resource.
Fix local multi-tenant problems
If az devops project list succeeds but MCP calls return TF400813, Azure CLI may be using a different tenant from the organization, especially for guest or multi-tenant users. Identify the organization’s tenant and provide it with --tenant <tenant-id> where the local server command supports that option. Sign out and back in with the intended tenant if the CLI account itself is wrong.
When the client says connected but tools are missing
- Open the client’s MCP tool list and confirm the Azure DevOps tools were actually loaded.
- In GitHub Copilot, use agent mode; standard chat mode does not expose MCP tools.
- Check tool filtering and remove accidental allowlists or denylists.
- Do not send both
X-MCP-ToolsetsandX-MCP-Toolson a remote request; Microsoft documents them as mutually exclusive. Restart the assistant after changing either filter. - Search for duplicate server definitions. The maintainer guide notes a 128-tool configuration limit; duplicates can consume that budget and hide expected tools.
- Try a simple read-only request, such as listing Azure DevOps projects, with an explicit organization and project name.
If the tool runs but returns no records, confirm the resource identifier, project membership and permissions. A successful transport handshake proves neither authorization nor data visibility.
Read logs at the right layer
In VS Code, open the MCP or GitHub Copilot Output channel and inspect connection, authentication and tool-loading messages. Capture the first error, not only the final “failed” line. If the assistant fails before invoking any MCP tool, restart it; Microsoft’s remote troubleshooting guidance classifies that condition as outside the Azure DevOps MCP boundary and directs you to the client provider if it continues.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Or skip the browser setup
If your goal is reliable website screenshots inside an automation or agent workflow rather than Azure DevOps repository data, ScreenshotNeo provides a separate screenshot API and MCP server. It accepts a URL and returns PNG, JPEG, WebP or PDF. Before capture it accepts cookie/consent banners and removes more than 60 known consent platforms, newsletter popups and chat widgets; each step can be disabled. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP tools are take_screenshot, get_page_info and capture_pdf, for Claude, Cursor and other MCP clients.
One request is enough:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);See the complete options and MCP configuration in the ScreenshotNeo documentation. Features include full-page and CSS-selector captures, device presets, retina scale, dark mode, custom CSS and JavaScript, waits, request blocking, headers, cookies, geolocation, PDF controls, resizing, caching, signed links, webhooks, bulk capture and a usage API. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account.
Prevent the next failure
- Document whether each client uses remote HTTP or local stdio.
- Keep organization, tenant and project identifiers explicit.
- Use a non-interactive local authentication method in CI, containers and SSH sessions.
- Keep tokens in environment variables or a secret manager.
- After changing filters or configuration, restart the client and test one read-only tool before complex prompts.
- Record the exact client, server mode, error code and first failing log line when escalating.
Frequently Asked Questions
Can I use a PAT with the hosted remote Azure DevOps MCP server?
No. The hosted remote service uses Microsoft Entra ID OAuth. PAT environment-variable authentication is a documented option for the local stdio package.
Why does the server show Connected when authentication is broken?
The process or transport handshake can succeed before an interactive OAuth redirect or tool authorization succeeds, especially in headless local environments.
Is Azure DevOps Server on-premises supported?
Microsoft’s documented remote and local Azure DevOps MCP servers support Azure DevOps Services, not Azure DevOps Server on-premises.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
