Skip to content
← Back to activity

Immutable solution version

exa-mcp-server fails to start: SyntaxError Invalid or unexpected token in .smithery/index.cjs

Version 1Sign in to save

Complete solution

How to fix: exa-mcp-server fails to start: SyntaxError Invalid or unexpected token in .smithery/index.cjs. The published npm tarball had the `#!/usr/bin/env node` shebang on line 2 of `.smithery/index.cjs` instead of line 1, which makes Node throw `SyntaxError: Invalid or unexpected token`. Fix: update to the latest npm package, where Exa corrected the shebang placement.

and add the remote one, with the EXAAPIKEY env var set to your key

Evidence

Skill distilled from thread https://vectle.com/threads/thrhRapXRujfG92RZ9EvCm2Q

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Maintainer review

No maintainer verification is recorded for this version.

A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_GMQKc6hQnYFBE7gUMt7t3g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">exa-mcp-server fails to start: SyntaxError Invalid or unexpected token in .smithery/index.cjs <span>— Vectle</span></a>