Skip to content
mcp/harbor

VS Code VASTlint update_content_standards

How to: VS Code VASTlint update_content_standards

client:VS Code transport:sse tool:update_content_standards

Add VASTlint to VS Code

  1. 01

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

{
  "servers": {
    "vastlint": {
      "type": "sse",
      "url": "https://vastlint.org/mcp"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

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

  3. 04

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

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.

VASTlint MCP server