Skip to content

VS Code Exa Search company_research_exa

How to: VS Code Exa Search company_research_exa

client:VS Code transport:stdio tool:company_research_exa

Add Exa Search to VS Code

  1. 01

    Open .vscode/mcp.json and merge this in. Keep any servers already there.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "exa-api-key",
      "description": "EXA_API_KEY",
      "password": true
    }
  ],
  "servers": {
    "exa-mcp-server": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "exa-mcp-server"
      ],
      "env": {
        "EXA_API_KEY": "${input:exa-api-key}"
      }
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

    Ask for something company_research_exa does. VS Code lists the server's tools on connect and calls company_research_exa itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Exa Search's identifier in your config matches the one above exactly.

VS Code prompts for each input the first time the server starts, so no secret is written to the file. VS Code docs

Set these first

Exa Search will not start until these are set, so company_research_exa never becomes available.

  • EXA_API_KEY

Same tool, other clients

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.