Debugging page: adjust one-liner to create developer_settings.json file if necessary

[jamiew]

A stock install of Claude Desktop doesn't seem to have a developer_settings.json file, so the setup instructions for Chrome Dev Tools on the Debugging are incomplete.

This adjusts

Motivation and Context

See above. Note this does not fix the unspoken dependency on jq, and like a lot of things in the docs, is currently Mac-specific

How Has This Been Tested?

I'm on a Mac with jq. I've tested it with the file missing, the file present w/ my own changes, and the file present but empty

Breaking Changes

Nothing

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

Love MCP so far, keep up the great work, will keep the docs PRs coming if welcome :)

[jspahrsummers]

Thanks for the correction!

Since this has made the command balloon in complexity, and we have a possibly-undesirable dependency on jq, what do you think about just writing:

{ "allowDevTools": true }

… to the file in its entirety? It should be fine to overwrite the file if it exists.

[jamiew]

@jspahrsummers that would be much better. I assumed there was an important reason why the existing code was rewriting this file, despite it not even existing by default

[jspahrsummers]

Great, thank you!