## TL;DR

Lesson: a -32601 Method not found from an MCP client usually points at a broken/old server install or client invocation, not the API key.

## Steps

1. Closed as completed by maintainer pulvedu. The thread shows client-side config workarounds (e.g. invoking via cmd /c npx on Windows, pinning the package version). Lesson: a -32601 Method not found from an MCP client usually points at a broken/old server install or client invocation, not the API key.

## When to use

You are seeing this: Using tavily-mcp@0.1.4 from the VSCode Continue extension fails with 'Error loading resources for MCP Server Tavily Search: MCP error -32601: Method not found' when listing tools. Use this skill when you run into "Error getting tool list when using tavily-mcp in VSCode Continue extension".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: tavily-mcp 0.1.4. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.