Codex
To configure the MCP Server in the Codex VS Code Extension, go to , and add the following configuration:
When using DVT IDE VS Code extension from marketplace:
Name: dvt
Type: STDIO
Command to launch: /bin/bash
Arguments: [-c, $DVT_HOME/platform/<os>-<arch>/bin/dvt_mcp.sh connect]
Environment variables: { DVT_HOME: <extensions_dir>/amiq.dvt-<version>-<os>-<arch>/dvt_home }
When using DVT IDE VS Code extension from marketplace:
Name: dvt
Type: STDIO
Command to launch: cmd
Arguments: [/c, %DVT_HOME%/platform/<os>-<arch>/bin/dvt_mcp.bat connect]
Environment variables: { DVT_HOME: <extensions_dir>/amiq.dvt-<version>-<os>-<arch>/dvt_home }
When using DVT IDE VSCodium from a kit distribution:
Name: dvt
Type: STDIO
Command to launch: /bin/bash
Arguments: [-c, $DVT_HOME/bin/dvt_mcp.sh connect]
Environment variables: { DVT_HOME: /path/to/dvt_home }
When using DVT IDE VSCodium from a kit distribution:
Name: dvt
Type: STDIO
Command to launch: cmd
Arguments: [/c, %DVT_HOME%/bin/dvt_mcp.bat connect]
Environment variables: { DVT_HOME: /path/to/dvt_home }
Alternatively, you can configure the MCP Server using Codex CLI:
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.