Cursor
The MCP Server is automatically registered in Cursor IDE, so no manual configuration is required. You can start using the tools from DVT immediately.
Cursor Agents Window does not currently support MCP servers registered through the API. As a result, manual configuration is required.
To configure the server manually, navigate to in Cursor IDE or in Cursor Agents Window. and use the button to add the new configuration.
Note
Manually configured MCP Servers are used by both Cursor IDE and Cursor Agents Window. To avoid having the DVT MCP Server configured twice in Cursor IDE, disable the automatically registered extension-DVT MCP server using the toggle in Cursor IDE Settings.
{
"mcpServers": {
"dvt": {
"command": "/bin/bash",
"type": "stdio",
"args": [
"-c",
"$HOME/.dvt/bin/dvt_env exec dvt_mcp.sh connect"
]
}
}
}
{
"mcpServers": {
"dvt": {
"command": "cmd",
"type": "stdio",
"args": [
"/c",
"%UserProfile%/.dvt/bin/dvt_env.exe exec dvt_mcp.bat connect"
]
}
}
}
Warning
Cursor uses a shared MCP process for all the windows it opens. This requires an MCP Server reload whenever opening a new Cursor window, whether an IDE or an Agents Window. This ensures that the DVT MCP Server successfully connects to the newly opened project.
To do that, navigate to in Cursor IDE or in Cursor Agents Window and use the button on the DVT MCP Server. When using Remote SSH, the button might not appear. In this case, you can use the toggle to reload the MCP Server.
When you reload the MCP Server in the Agents Window, please make sure to reload it for all the projects that you are currently working on. You can select the project using the tab group located at the top of the window. It is not enough to reload just the MCP Server from the first tab.