Skip to content

VS Code Edge find_skill

How to: VS Code Edge find_skill

client:VS Code transport:stdio tool:find_skill

Add Edge to VS Code

  1. 01

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

{
  "inputs": [
    {
      "type": "promptString",
      "id": "edge-key",
      "description": "EDGE_KEY",
      "password": true
    }
  ],
  "servers": {
    "edge": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@getedge/mcp"
      ],
      "env": {
        "EDGE_KEY": "${input:edge-key}"
      }
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that Edge'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

Edge will not start until these are set, so find_skill never becomes available.

  • EDGE_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 8 October 2026. It is what the server actually exposes, not what its listing claims.

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.