Claude Code

To configure the MCP Server in Claude Code’s VS Code Extension, create a file named .mcp.json in the root directory of your project, with the following content:

Linux

When using DVT IDE VS Code extension from marketplace:

{
    "mcpServers": {
        "dvt": {
            "type": "stdio",
            "command": "/bin/bash",
            "args": [
                "-c",
                "$DVT_HOME/platform/<os>-<arch>/bin/dvt_mcp.sh connect"
            ],
            "env": {
                "DVT_HOME": "<extensions_dir>/amiq.dvt-<version>-<os>-<arch>/dvt_home"
            }
        }
    }
}

Windows

When using DVT IDE VS Code extension from marketplace:

{
    "mcpServers": {
        "dvt": {
            "type": "stdio",
            "command": "cmd",
            "args": [
                "/c",
                "%DVT_HOME%/platform/<os>-<arch>/bin/dvt_mcp.bat connect"
            ],
            "env": {
                "DVT_HOME": "<extensions_dir>/amiq.dvt-<version>-<os>-<arch>/dvt_home"
            }
        }
    }
}

Linux

When using DVT IDE VSCodium from a kit distribution:

{
    "mcpServers": {
        "dvt": {
            "type": "stdio",
            "command": "/bin/bash",
            "args": [
                "-c",
                "$DVT_HOME/bin/dvt_mcp.sh connect"
            ],
            "env": {
                "DVT_HOME": "path/to/dvt_home"
            }
        }
    }
}

Windows

When using DVT IDE VSCodium from a kit distribution:

{
    "mcpServers": {
        "dvt": {
            "type": "stdio",
            "command": "cmd",
            "args": [
                "/c",
                "%DVT_HOME%/bin/dvt_mcp.bat connect"
            ],
            "env": {
                "DVT_HOME": "path/to/dvt_home"
            }
        }
    }
}

Alternatively, you can configure the MCP Server using Claude Code CLI:

Linux

When using DVT IDE VS Code extension from marketplace:

claude mcp add --env DVT_HOME='<extensions_dir>/amiq.dvt-<version>-<os>-<arch>/dvt_home' --transport stdio dvt -- /bin/bash -c '$DVT_HOME/platform/<os>-<arch>/bin/dvt_mcp.sh connect'

Windows

When using DVT IDE VS Code extension from marketplace:

claude mcp add --env DVT_HOME='<extensions_dir>/amiq.dvt-<version>-<os>-<arch>/dvt_home' --transport stdio dvt -- cmd /c '%DVT_HOME%/platform/<os>-<arch>/bin/dvt_mcp.bat connect'

Linux

When using DVT IDE VSCodium from a kit distribution:

claude mcp add --env DVT_HOME='path/to/dvt_home' --transport stdio dvt -- /bin/bash -c '$DVT_HOME/bin/dvt_mcp.sh connect'

Windows

When using DVT IDE VSCodium from a kit distribution:

claude mcp add --env DVT_HOME='path/to/dvt_home' --transport stdio dvt -- cmd /c '%DVT_HOME%/bin/dvt_mcp.bat connect'

Note

The methods above will enable access to the MCP Server only for the current DVT project. If you want to enable the MCP Server for all projects, either add the above server configuration in the ~/.claude.json file or use the claude mcp add --scope user <other_args> command.

After creating the JSON file (or using the claude mcp add command), follow these steps:

1. Open the Claude Code chat and start a new session.

2. Use the /mcp (MCP Servers) command.

3. The DVT MCP Server should be marked Connected with a green indicator

Note

Mainstream MCP hosts limit the environment of the MCP Server subprocess. Ensure that DVT_HOME and other necessary environment variables are properly set in the configuration.