"How to add MCP to the Firefox browser" matching MCP servers:

Browser control for Claude Code, on Firefox.

Enables turning requirements documents into RFCs, functional test scenarios, and a traceability matrix, with tools to parse, diff, and verify coverage.

Enables agents to turn a plain-language description of a device into a complete, validated build package — parts list, 3D-printable parts, wiring, firmware code, picture assembly guide, and tests — that anyone can assemble without electronics experience.

Firefox browser automation via WebDriver BiDi for testing, scraping, and browser control. Supports snapshot/UID-based interactions, network monitoring, console capture, and screenshots.

Automates the conversion of Figma designs into TypeScript React components and integrates with GitHub to create pull requests for the generated code. It includes visual regression testing with Playwright and accessibility validation to ensure implementations match the original designs.

Provides a stable, side-effect-free MCP tool contract that enables AI workflows to be prototyped, demoed, tested, or dry-run without connecting to databases, APIs, files, or other real data sources. It enables swapping in a real data server later without changing the AI-facing interface.

Provides a testable gateway path for running a local MCP-style server in hosted-like conditions, with tenant-isolated reads, approval-denied writes, deterministic failures, and smoke-test verification.

Gives AI agents a compact, semantic interface to the browser, returning structured page snapshots with stable element IDs instead of raw DOM. Enables agents to navigate, interact, and extract information from web pages efficiently.

Enables browser automation and smoke testing via Playwright, with tools for navigation, DOM interaction, screenshots, network capture, and more.

MCP server that lets agents drive a browser and record every action into a replayable trace, then replay it deterministically with network request assertions. It exposes tools for navigating, clicking, filling, and verifying requests.

Exposes your Chrome/Edge browser as MCP tools for AI agents, enabling browser automation through a Chrome extension with 47 tools for navigation, interaction, page reading, and more.

Enables AI agents and MCP clients to drive real Chrome, Edge, Brave, and Firefox browsers through native automation protocols. It exposes tools for navigation, page snapshots, form filling, clicks, screenshots, console/network inspection, and tab management.

Free JSON Schema validation, JSON to TypeScript, CSV to JSON, JSON repair and JSON to CSV for AI agents. Hosted MCP plus local STDIO. Connect once with a scoped key; enforce tool allowlists and quotas, inspect request IDs. Runnable repair → validate → CSV workflow. Bounded OpenAPI and webhook checks. No LLM calls or payments. Setup: invokeport.com/agents.

Enables MCP clients to open websites, capture screenshots at multiple breakpoints, and run automated design audits for issues like overflow, small tap targets, low contrast, missing alt text, tiny text, and clipped content.

Enables AI assistants to capture screenshots of web pages using automated browser sessions. Supports full-page and element-specific screenshots, device simulation, and JavaScript execution for comprehensive web testing and monitoring.

Enables browser automation for React Native Web applications using coordinate-based clicks to trigger RNW's gesture responder, with multi-tab management, screenshots, and persistent sessions.

Enables AI-driven browser automation with advanced form testing, batch operations, and intelligent element extraction for MCP-compatible applications.

Adds persistent QA state to browser automation, enabling AI agents to maintain session-scoped artifacts and generate reports across multiple steps.

Enables AI agents to control a hardened, human-like Chromium browser for automation and testing, with ad blocking, natural mouse movements, and Cloudflare Turnstile assistance.

A local stdio MCP server that verifies an isolated WPE WebKit runtime through a network-disabled Docker acceptance test. It exposes two bounded tools for native input, DOM/text state, and PNG capture without receiving URLs, profiles, credentials, or public-web access.