Issue Description

The exa-mcp-server package has different behavior between Windows and Linux, and the HTTP endpoint is missing most tools.

Environment

• OS: Linux (Ubuntu)
• Node: v20.19.5
• NPM: v10.8.2
• Package: [email protected]

Problem 1: NPX Package Fails on Linux

When trying to run the package via npx on Linux:

npx -y exa-mcp-server

Error:

npm error could not determine executable to run

The package.json defines the bin as:

{ "exa-mcp-server": ".smithery/stdio/index.cjs" }

But this file appears to be missing or inaccessible in the published package on Linux systems.

Expected: Package should work on Linux just like it does on Windows (where it successfully exposes 7 tools)

Problem 2: HTTP Endpoint Missing Tools

As a workaround, I tried using the HTTP endpoint:

{
  "type": "http",
  "url": "https://mcp.exa.ai/mcp",
  "headers": {
    "X-API-Key": "<api-key>"
  }
}

Result: Only 2 tools are exposed:

• web_search_exa
• get_code_context_exa

Expected: All 7 tools should be available:

• web_search_exa
• get_code_context_exa
• company_research_exa
• crawling_exa
• linkedin_search_exa
• deep_researcher_start
• deep_researcher_check

Configuration Tested

{
  "command": "npx",
  "args": [
    "-y",
    "exa-mcp-server"
  ],
  "env": {
    "EXA_API_KEY": "<api-key>"
  }
}

Logs

npm error could not determine executable to run
npm error A complete log of this run can be found in: /home/azureuser/.npm/_logs/2025-11-10T12_15_55_633Z-debug-0.log

From npm debug log:

15 verbose stack Error: could not determine executable to run
16 verbose pkgid [email protected]

Request

Please fix the Linux compatibility issue with the npx package. The bin entry point seems to be broken on Linux systems while it works fine on Windows.

If you need help debugging , I can have this fixed in 30 minutes lol.