Claude Code / AI Coding Tools
MCP server OAuth tools hidden — No such tool available error on Azure DevOps MCP server
Fix MCP servers requiring OAuth authentication not exposing their tools to Claude Code session — tools invisible despite server showing connected Includes evidence for Claude Code troubleshooting demand.
- Category
- AI Coding Tools
- Error signature
No such tool available: mcp__azure-devops__core_list_projects- Quick fix
- Verify the account session, API key, provider settings, and environment where the failing tool is running.
- Updated
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
- Confirm the exact error signature matches
No such tool available: mcp__azure-devops__core_list_projects. - Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
- 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
- Capture the exact error message and the command, editor action, or request that triggered it.
- Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
- Review the source evidence below and compare it with your environment.
- Apply one change at a time and rerun the smallest failing action.
- 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.
Sources checked
Evidence note: 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.
Related errors
- AI Coding Tools
FAQ
What should I check first?
Start with the exact No such tool available: mcp__azure-devops__core_list_projects text and the smallest action that reproduces it.
Can I ignore this error?
No. Treat it as a failed Claude Code workflow until the root cause is understood.
Is this guaranteed to have one fix?
No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.
How do I know the fix worked?
Rerun the same command, editor action, or request. The fix is working when that action completes without No such tool available: mcp__azure-devops__core_list_projects.