What this error means

No such tool available: mcp__azure-devops__core_list_projects is a Claude Code failure pattern reported for developers trying to fix mcp servers requiring oauth authentication not exposing their tools to claude code session — tools invisible despite server showing connected. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Issue #11585 on anthropics/claude-code: MCP server with OAuth shows as connected via 'claude mcp list' but its tools are not exposed to Claude sessions. Azure DevOps MCP specifically affected. User gets 'No such tool available' error. Opus model flagged as regression. Categorized as AI Coding Tools per SKILL.md mapping for Claude Code MCP errors.

Common causes

  • GitHub Issue #11585 on anthropics/claude-code: MCP server with OAuth shows as connected via 'claude mcp list' but its tools are not exposed to Claude sessions. Azure DevOps MCP specifically affected. User gets 'No such tool available' error. Opus model flagged as regression. Categorized as AI Coding Tools per SKILL.md mapping for Claude Code MCP errors.

Quick fixes

  1. Confirm the exact error signature matches No such tool available: mcp__azure-devops__core_list_projects.
  2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
  3. Verify the account session, API key, provider settings, and environment where the failing tool is running.

Platform/tool-specific checks

  • Verify the command, editor, extension, or API client that produced the error.
  • Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
  • Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

  1. Capture the exact error message and the command, editor action, or request that triggered it.
  2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
  3. Review the source evidence below and compare it with your environment.
  4. Apply one change at a time and rerun the smallest failing action.
  5. Keep the working fix documented for the team or deployment environment.

How to prevent it

  • Keep provider/tool configuration documented.
  • Record non-secret diagnostics such as tool version, provider name, model name, and command path.
  • Add a lightweight check before CI or production workflows depend on the tool.