Skip to content

VS Code catalogue sku_set

How to: VS Code catalogue sku_set

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

Add catalogue to VS Code

  1. 01

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

{
  "servers": {
    "catalogue": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/catalogue"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

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

  3. 04

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

catalogue will not start until these are set, so sku_set never becomes available.

  • MCP_LICENSE_KEY

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.