Edge MCP Bridge Native Host

edge-mcp-bridge is the Native Messaging and local MCP service used by the Edge MCP Bridge browser extension.

Requirements

• Node.js 20 or newer
• Chrome, Chromium, or Microsoft Edge

Configuration-first install

The browser extension generates a version-pinned npx MCP configuration. On first launch, npm downloads this package into its cache and edge-mcp-stdio performs user-level Native Host registration for the fixed owned extension identity. A global install is not required.

Manual global installation and registration remain available for diagnostics and managed deployments:

npm install -g edge-mcp-bridge
edge-mcp-bridge register --detect

Register a specific browser with --browser chrome, --browser chromium, or --browser edge. Use --browser all to register all three. Multiple extension IDs can be passed after one --extension-id option, which is useful when Chrome and Edge distribute different builds:

edge-mcp-bridge register --extension-id <chrome-id> <edge-id> --browser all

For automated environments, set a comma-separated EDGE_MCP_EXTENSION_IDS value instead:

EDGE_MCP_EXTENSION_IDS=<extension-id> edge-mcp-bridge register --detect

System-level registration requires an elevated shell:

edge-mcp-bridge register --extension-id <extension-id> --browser edge --system

Diagnose

edge-mcp-bridge doctor
edge-mcp-bridge report

Security Status

Version 1.0.31 is publicly available on npm; 1.0.32 is the current local candidate. The local HTTP/MCP endpoint intentionally uses a loopback-only trust model without client authentication. Keep it bound to 127.0.0.1 and use it only on a trusted device. Do not expose it through port forwarding, a reverse proxy, a shared host, or a 0.0.0.0 listener. MCP tool approval remains the client's responsibility.

License

MIT. The package preserves the original upstream copyright notice required by the license.