With OpenCode
To configure the DVT MCP Server in the OpenCode 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 OpenCode configuration.
> opencode mcp add
┌ Add MCP server
│
◇ Enter MCP server name
│ dvt_mcp
│
◇ Select MCP server type
│ Local
│
◇ Enter command to run
│ {env:HOME}/.dvt/bin/dvt_env exec dvt_mcp.sh connect
│
◆ MCP server "dvt_mcp" added to /home/user/.config/opencode/opencode.json
│
└ MCP server added successfully
> opencode mcp add
┌ Add MCP server
│
◇ Enter MCP server name
│ dvt_mcp
│
◇ Select MCP server type
│ Local
│
◇ Enter command to run
│ {env:UserProfile}/.dvt/bin/dvt_env.exe exec dvt_mcp.bat connect
│
◆ MCP server "dvt_mcp" added to /home/user/.config/opencode/opencode.json
│
└ MCP server added successfully
For more information, please refer to the official OpenCode 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.
> opencode mcp add
┌ Add MCP server
│
◇ Enter MCP server name
│ dvt_mcp
│
◇ Select MCP server type
│ Local
│
◇ Enter command to run
│ {env:DVT_HOME}/bin/dvt_mcp.sh connect
│
◆ MCP server "dvt_mcp" added to /home/user/.config/opencode/opencode.json
│
└ MCP server added successfully