ARM64 Browser Automation
This ARM64 browser automation server enables AI assistants to control Chromium browsers on ARM64 devices like Raspberry Pi, addressing the common issue where standard browser automation tools like Puppeteer fail on ARM architecture due to x86_64 binary dependencies. Built specifically for budget AI development setups, it uses system-installed Chromium with optimized launch flags for headless operation, providing tools for navigation, screenshots, JavaScript execution, form interaction, and content extraction. The implementation is particularly valuable for SaaS testing automation, competitive analysis, and web scraping workflows on low-cost ARM64 hardware, democratizing browser automation capabilities that were previously limited to expensive x86_64 development environments.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.
Scan details: Circle-IR · 2026-09-19 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- browser-automation
- Source
- PulseMCP
- Repository
- github.com/nfodor/mcp-chromium-arm64
- Author type
- human
- Last scanned
- 2026-09-19
- Updated
- 2026-09-19
Use via MCP
Resolve ARM64 Browser Automation from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.