Exa Code MCP

Latest Audit Result

exa-code-mcp v2.0.3 is a thin wrapper around the dedicated Exa Code API (POST https://api.exa.ai/context) using raw axios — it does NOT depend on or use the exa-js SDK (latest 2.12.1). It exposes exactly one MCP tool, `get_code_context`, taking `query` and `tokensNum`. None of the standard Exa endpoints (search, get_contents, find_similar, answer, research) are implemented, and no search types or content options (text, highlights, auto) are passed. There is a clear bug: the `availableTools` registry in src/index.ts:17-20 declares `find_library_exa` and `get_library_context_exa`, but the actually registered tool name in src/tools/exa-code.ts:28 is `get_code_context` — the registry keys are unused dead/incorrect entries that drive the gating logic in shouldRegisterTool. The README only documents `get_code_context`, confirming the registry entries are stale. Health is needs_audit due to (a) no SDK adoption, (b) the registry/tool-name mismatch, and (c) the audit-context claim that the server maps to Exa search with code category is wrong — it calls /context directly. Dependencies: @modelcontextprotocol/sdk ^1.12.1, axios ^1.7.8, zod ^3.22.4.

Missing Features (11)

• exa-js SDK not used (raw axios against api.exa.ai/context endpoint)
• endpoint 'search' not implemented
• endpoint 'get_contents' not implemented
• endpoint 'find_similar' not implemented
• endpoint 'answer' not implemented
• endpoint 'research' not implemented
• search type 'auto' not passed (no search call made at all)
• content option 'text' not passed (no get_contents call)
• content option 'highlights' not passed
• availableTools registry lists 'find_library_exa' and 'get_library_context_exa' but actually registered tool is 'get_code_context' (registry/tool name mismatch)
• Audit context note 'maps to Exa search with code category' is incorrect — actually calls dedicated POST /context endpoint, not /search with category=code