DevToolsPlugin

Exposes Dev Proxy messages, and information about intercepted requests and responses in Chrome DevTools. Supports both HTTP requests and STDIO communication.

Configuration example

{
  "$schema": "https://raw.githubusercontent.com/dotnet/dev-proxy/main/schemas/v2.0.0/rc.schema.json",
  "plugins": [
    {
      "name": "DevToolsPlugin",
      "enabled": true,
      "pluginPath": "~appFolder/plugins/DevProxy.Plugins.dll",
      "configSection": "devTools"
    }
  ],
  "devTools": {
    "$schema": "https://raw.githubusercontent.com/dotnet/dev-proxy/main/schemas/v2.0.0/devtoolsplugin.schema.json",
    "preferredBrowser": "Edge"
  }
}

Configuration properties

Command line options

None

Known issues

Dev Tools don't open in Microsoft Edge on Windows

You use Dev Proxy on Windows and configure it to use Microsoft Edge to display Dev Tools. After you start Dev Proxy, it starts the inspector but Dev Tools don't open or they open empty.

To fix this issue:

1. Open Microsoft Edge
2. Go to Settings
3. Open System and performance
4. Disable Startup boost
5. Close all Microsoft Edge windows and processes
6. Start Dev Proxy

STDIO support

When using the DevToolsPlugin with the STDIO command, you can inspect STDIN/STDOUT/STDERR communication in Chrome DevTools:

• Messages appear with stdio://command-name URLs
• Requests show as STDIN method
• Responses show as STDOUT (200 status) or STDERR (500 status)
• Message bodies are formatted as JSON when applicable
• Timing information is available for each request/response pair

Configuration example for STDIO

{
  "$schema": "https://raw.githubusercontent.com/dotnet/dev-proxy/main/schemas/v2.1.0/rc.schema.json",
  "plugins": [
    {
      "name": "DevToolsPlugin",
      "enabled": true,
      "pluginPath": "~appFolder/plugins/DevProxy.Plugins.dll",
      "configSection": "devTools"
    }
  ],
  "devTools": {
    "preferredBrowser": "Edge"
  }
}

Then run:

devproxy STDIO npx -y @modelcontextprotocol/server-filesystem

Next step