chrome-devtools-mcp emulate supports extra HTTP headers
Introduced 2026-05-26 · score 0.97
HOW TO USE IT
When testing or debugging a page with custom request headers, call `emulate` on the selected page with `extraHttpHeaders` as a JSON string. Headers persist across navigations; pass an empty string to clear them, and omit the parameter to leave them unchanged.
emulate({"extraHttpHeaders":"{\"X-Custom\":\"value\",\"Authorization\":\"Bearer <token>\"}"})emulate({"extraHttpHeaders":""})WHY THIS HELPS
Set page-level HTTP headers while testing or debugging a web application in Chrome.
REQUIREMENTS AND LIMITATIONS
- Version: 1.1.0
- extraHttpHeaders: JSON string object of extra HTTP headers; headers are sent on every HTTP request from the page and persist across navigations until cleared. Empty string clears all extra headers.
- Headers apply to HTTP requests originating from the page and persist across navigations until cleared.
- Docs conflict: Card says parameter is `extraHTTPHeaders` and clearing uses `{}`; v1.1.0 reference documents `extraHttpHeaders` (lowercase `ttp`) as a JSON string, and says to clear with an empty string. It does not document omission behavior.
FIRST-PARTY EVIDENCE
- https://github.com/ChromeDevTools/chrome-devtools-mcp/releases/tag/chrome-devtools-mcp-v1.1.0
- https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/1176
- https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/chrome-devtools-mcp-v1.1.0/docs/tool-reference.md
Check the installed version and the source before using it. Entry JSON