Skip to content

extension_manifest_validate ​

Validate a manifest.json across browsers.

Quick start ​

Will this manifest load on Firefox and Safari?

Asked to check the manifest for Firefox, the agent validates it and reads the findings.

Asked to check the manifest for Firefox, the agent validates it and reads the findings.

How the agent uses it ​

This reports missing fields, invalid permissions, dangling file references, and cross-browser compatibility issues. Read buildBlocking for the errors that make extension_build refuse.

Reference ​

Grouplocal, on by default
TierSee
Needsnone
Read onlyyes
Destructiveno
Idempotentyes
Reaches the open webno

Inputs ​

InputTypeRequiredDefaultWhat it does
manifestPathstringnoPath to manifest.json. Or pass projectPath and the manifest is located for you.
projectPathstringnoPath to the extension project root; manifest.json is resolved from it (root or src/). Accepted in place of manifestPath.
browsersarray of stringno["chrome","firefox","edge"]Browsers to validate against
browserstringnoSingle browser to validate against; alias for browsers:[browser] to match the other tools.

Next ​

  • MCP server: install, the two groups and the session gates
  • Install in your client
  • extension_analyze: Analyze a BUILT extension on disk: file sizes, declared entry points, permissions, bundle composition, and store-readiness checks.
  • extension_doctor: Diagnose a dev session end to end: ready contract, dev-server process, control-port agreement, control channel, eval token, executor, browser liveness.
  • extension_dom_snapshot: Take a shallow structured DOM snapshot of one chosen surface through the agent bridge (localhost only; the snapshot itself needs no CDP, but listTargets and tabUrl resolution...
  • extension_inspect: Inspect a running extension deeply over the browser's debugger protocol: full HTML (open shadow roots of #extension-root and [data-extension-root] hosts inlined; other shadow ro...
  • extension_list_extensions: List the extensions in the running dev browser: id, name, version, and, on Chromium, live contexts.
  • extension_logs: Read or stream logs from every context of a running dev session (service worker, content scripts, popup, options, sidebar, devtools, pages) in one ordered timeline.
  • extension_theme_verify: Verify a Chrome theme manifest before it ships.