Skip to content

VS Code pentest mcp server pentest_get_guide

How to: VS Code pentest mcp server pentest_get_guide

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

Add pentest mcp server to VS Code

  1. 01

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

{
  "servers": {
    "pentest-mcp-server": {
      "type": "http",
      "url": "https://pentest.caseyjhand.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

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

  3. 04

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

pentest mcp server will not start until these are set, so pentest_get_guide never becomes available.

  • PENTEST_ENABLE_PAYLOAD_GENERATION
  • MCP_LOG_LEVEL

Same tool, other clients

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