Skip to content

VS Code Second Eyes Agent Workflow Services read_menu

How to: VS Code Second Eyes Agent Workflow Services read_menu

client:VS Code transport:streamable-http tool:read_menu

Add Second Eyes Agent Workflow Services to VS Code

  1. 01

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

{
  "servers": {
    "secondeye-mcp-unblock": {
      "type": "http",
      "url": "https://secondeyesai.com/api/bar"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that Second Eyes Agent Workflow Services's identifier in your config matches the one above exactly.

Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs

Set these first

Second Eyes Agent Workflow Services will not start until these are set, so read_menu never becomes available.

  • SECOND_EYE_BASE_URL
  • MCP_X402_WALLET_KEY
  • MCP_X402_MAX_SPEND_USD
  • MCP_X402_SESSION_MAX_USD
  • MCP_X402_ALLOW_SLUGS

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.