Ecosystem · mobilebridge

Drive Android browsers with the same toolbelt.

Same 36-tool MCP interface, different target device. mobilebridge discovers connected Android handsets, manages browser sessions on them, and exposes them to VulpineOS as if they were local Vulpine browser contexts.

Open source · MPL 2.0GoAndroid

What it does

mobilebridge sits on the host, talks to connected Android devices over ADB, and brokers CDP sessions into the on-device browser. The VulpineOS orchestrator treats those sessions as additional contexts in the pool — so the same agent code works against desktop Vulpine browser and Android Chrome / Firefox without modification.

Device discovery

vulpine_list_mobile_devices enumerates handsets visible to the bridge. Live status.

Session control

vulpine_connect_mobile_device opens a session and returns an endpoint. vulpine_disconnect_mobile_device tears down.

Same agent

Run the same browser-tool workflow against mobile and desktop targets. Toolbelt parity.

Where it goes

iOS support and richer per-device controls (gesture replay, simulator support) live behind the public roadmap. mobilebridge today is Android-first with a deliberate scope so it stays production-grade.

Resources

mobilebridge source
github.com/VulpineOS/mobilebridge

Self-host the runtime today.

All four open-source pieces — VulpineOS, Foxbridge, vulpine-mark, mobilebridge — are MPL 2.0 and ship together.

Star on GitHub→Read the docs