{
  "mcpServers": {
    "tavily-mcp": {
      "command": "wsl.exe",
      "args": [
        "bash",
        "-lc",
        "TAVILY_API_KEY=\"tvly-dev-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\" npx -y tavily-mcp@latest"
      ],
      "env": {},
      "disabled": false,
      "autoApprove": []
    }
  }
}



Note: I also tested with a bash script /home/patry/tavily-start.sh containing:

bash
#!/bin/bash
export TAVILY_API_KEY="tvly-dev-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
exec npx -y --quiet tavily-mcp@latest
and command: wsl.exe bash -lc /home/patry/tavily-start.sh.
In both variants, the behavior is the same.

In Settings → MCP:

Tavily appears with a green dot.

All tools are listed: tavily_search, tavily_extract, tavily_crawl, tavily_map, tavily_research, …

No visible error in the UI.

MCP server status in WSL2
In WSL2 (Ubuntu), I can run:

bash
bash /home/patry/tavily-start.sh
and I see:

text
Tavily MCP server running on stdio
The process stays running and is ready to accept MCP connections.
So Tavily MCP + API key are OK.

What I expect
When I ask the local LLM in Void something like:

"Peux-tu faire une recherche web sur WSL2 et m'expliquer les bases ?"

I expect Void to:

Call the Tavily MCP tool (tavily_search).

Use the web search results in its answer.

Mention that it searched the web or at least include up-to-date information.

What actually happens
Instead, Void behaves as if the assistant had no web tools at all:

Example answer 1:

"Je n'ai pas trouvé de résultats dans les fichiers de votre codebase pour 'WSL2 basics', mais voici une explication simple de WSL2…"

Example answer 2:

"Je n'ai pas accès à des liens web externes, mais voici une explication simple de WSL2 en français…"

So the assistant:

Searches only in the local files / codebase.

Explicitly says it cannot access external links or the web.

Never mentions using tavily_search or any Tavily tool.

This is exactly the same behavior as a model with no MCP web tools enabled.

Why I think this is a Void MCP client bug
Tavily MCP server runs fine with the API key (tested in WSL2).

Void shows a green dot and lists all Tavily tools in the MCP settings.

The local LLM works perfectly for explanations, code, and local files.

But no Tavily tool is ever called in practice: no web results, no mention of web search, same answer as offline mode.

This matches issues reported in other MCP clients where tools are connected but never actually invoked (tools “green but inactive”).

Questions / help
Could this be:

A bug in how Void decides when to call MCP tools (especially Tavily) for local models?

A missing configuration step to explicitly enable Tavily for a given model / project in Void?

A known limitation/bug with WSL2 + MCP STDIO servers?

Any guidance or workaround to make Void actually call tavily_search with the configuration above would be greatly appreciated.
My goal is to have Void behave like Cursor: local LLM + MCP tools (filesystem + Tavily web search).

If you need logs or a specific flag to enable MCP debug output, please tell me exactly what to run and where to find the logs, as I am not very experienced.


Thank you very much for your help and for Void.