With Gemini CLI

To configure the DVT MCP Server in the Gemini CLI agent, follow these steps:

1. Start a DVT MCP CLI Endpoint for your project

Linux

$DVT_HOME/bin/dvt_mcp.sh start /path/to/dvt/project -lang vlog -lang vhdl -default.build <compilation_args>

Windows

%DVT_HOME%/bin/dvt_mcp.bat start /path/to/dvt/project -lang vlog -lang vhdl -default.build <compilation_args>

2. Configure the command that starts the MCP Connector

Add the command to start the MCP Connector in the Gemini CLI configuration and make sure DVT_HOME is set.

Linux

gemini mcp add --scope project --env DVT_HOME=path/to/dvt/home dvt_mcp /bin/bash -c '$DVT_HOME/bin/dvt_mcp.sh connect'

Windows

gemini mcp add --scope project --env DVT_HOME=path/to/dvt/home dvt_mcp cmd /c '%DVT_HOME%/bin/dvt_mcp.bat connect'

For more information, please refer to the official Gemini CLI MCP documentation

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.