With Codex CLI
To configure the DVT MCP Server in the Codex CLI agent, follow these steps:
Start a DVT MCP CLI Endpoint for your project
$HOME/.dvt/bin/dvt_env exec dvt_mcp.sh start /path/to/dvt/project -lang vlog -lang vhdl -default.build <compilation_args>
%UserProfile%/.dvt/bin/dvt_env.exe exec dvt_mcp.bat start /path/to/dvt/project -lang vlog -lang vhdl -default.build <compilation_args>
Configure the command that starts the MCP Connector
Add the command to start the MCP Connector in the Codex configuration.
codex mcp add dvt_mcp -- /bin/bash -c '$HOME/.dvt/bin/dvt_env exec dvt_mcp.sh connect'
codex mcp add dvt_mcp -- cmd /c '%UserProfile%/.dvt/bin/dvt_env.exe exec dvt_mcp.bat connect'
For more information, please refer to the official Codex MCP documentation
Note
dvt_env must be installed before use.
Installation occurs automatically when you start any DVT product for the first time.
To install it manually beforehand, run: $DVT_HOME/bin/dvt_env install.
Note
$DVT_HOME environment variable is required for the DVT MCP Server to function properly.
While dvt_env attempts to auto-detect this value, it may fail in isolated CLI agent environments.
If detection fails, explicitly set $DVT_HOME in your MCP Connector configuration.
claude mcp add --env DVT_HOME=path/to/dvt/home dvt_mcp -- /bin/bash -c '$HOME/.dvt/bin/dvt_env exec dvt_mcp.sh connect'