[BUG] `find` tool returns "Anthropic client not available" error With Claude Cowork

Resolved 💬 8 comments Opened Jan 13, 2026 by gn00295120 Closed Jan 24, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When using Claude Desktop App in Cowork mode with the Claude in Chrome MCP server, the find tool always fails with the error:

Anthropic client not available. Please check your API configuration.

This happens even though:

The Chrome tab connection is valid

Other MCP tools work correctly in the same session

The error occurs regardless of the query content

The failure appears to be isolated to the find tool only.

What Should Happen?

The find tool should return a list of matching elements on the current page using natural-language queries, similar to:

{
"elements": [
{
"ref": "ref_123",
"type": "button",
"text": "Subscribe",
"location": { ... }
}
]
}

Error Messages/Logs

Failed to find element: Anthropic client not available.
Please check your API configuration.


---
This error is returned 100% of the time when calling the find tool.

Steps to Reproduce

  1. Open Claude Desktop App in Cowork mode
  1. Connect to Chrome using the Claude in Chrome MCP server
  1. Navigate to any webpage (e.g. https://claude-world.com/)
  1. Confirm other MCP tools work:

tabs_context_mcp

read_page

computer (screenshot / scroll)

  1. Call the find tool:

{
"tool": "mcp__Claude_in_Chrome__find",
"parameters": {
"tabId": 222397199,
"query": "Subscribe button"
}
}

  1. Observe the error: “Anthropic client not available”

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude for Mac 1.0.3218(8679c9)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 8 comments on GitHub. Read the full discussion on GitHub ↗