Log inSubmit server
Wavexis MCP logo

Wavexis MCP

by MathiasPaulenko

Automates Chrome, Edge, and Firefox through 220 MCP browser tools using CDP or BiDi and your installed browser.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Wavexis MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mathiaspaulenko-wavexis-mcp": {
      "command": "uvx",
      "args": [
        "wavexis-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

MathiasPaulenko/wavexis-mcp exposes the wavexis browser automation library through 220 MCP tools for Chrome, Edge, and Firefox. It uses CDP for Chromium-based browsers and BiDi for Firefox, without Node.js or downloading Chromium. Agents can run one-shot URL tasks or maintain persistent sessions for multi-step navigation, interaction, extraction, screenshots, PDFs, and browser diagnostics. Reach for it when browser control needs broad coverage, optional capability tiers, or direct CDP/BiDi access.

Use cases

  • Automate multi-step browser sessions
  • Scrape data from paginated URLs
  • Capture screenshots and generate PDFs
  • Inspect and modify page DOM content
  • Run Lighthouse and browser diagnostics

Key features

  • 220 tools across 13 capability tiers
  • Chrome and Edge through CDP
  • Firefox through BiDi
  • Stateless calls and persistent sessions
  • Multi-action YAML workflows
  • Structured errors with suggestions

Tools72

What Wavexis MCP lets your agent do. Expand a tool for its parameters.

Verified live~26.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

8/9 checks healthy over the last 90d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · wavexis-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
Last commit6d agoMost recent push to the default branch.
Tools exposed72Callable tools this server registers over MCP.
Directory activity1 upvotesConfig copies, upvotes, and views on AllMCPs.

How Wavexis MCP works

What MathiasPaulenko/wavexis-mcp does

MathiasPaulenko/wavexis-mcp connects MCP-compatible AI clients to the wavexis browser automation library. It exposes 220 tools across 13 capability tiers, covering browser sessions, navigation, DOM inspection and mutation, JavaScript execution, screenshots, PDFs, scraping, iframe and shadow DOM interaction, network controls, storage, emulation, testing, DevTools features, and other browser functions.

The server works with Chrome and Edge through the Chrome DevTools Protocol (CDP), and with Firefox through WebDriver BiDi. It uses browsers already installed on the machine rather than downloading a separate Chromium build. The implementation is written in Python.

How it works

An MCP client supplies the model with tool definitions and receives JSON results from tool calls. WaveXisMCP passes those calls to wavexis, which performs the operation through the selected browser backend. Results can contain text, structured data, base64-encoded output, or file paths.

Two operating patterns are available:

  • Stateless calls accept a URL, launch or acquire a browser, perform the operation, and close automatically.
  • Session-based workflows begin with wavexis_session_open, reuse the returned session_id across calls, and finish with wavexis_session_close.

Persistent sessions suit sequences such as opening a page, navigating, clicking, filling a form, and capturing a screenshot. The server also provides wavexis_act for heuristic natural-language actions such as clicking, typing, filling, or hovering. Multi-action YAML workflows can combine several operations into one tool call, while raw CDP and BiDi tools provide a lower-level escape hatch.

Setup and configuration

Install the Python package with pip install wavexis-mcp, run it without a local installation using uvx wavexis-mcp, or configure the MCP client to launch the wavexis-mcp command. The documented Python versions are 3.11, 3.12, and 3.13.

The default capability set is core, which provides 72 tools. Pass --caps=all to expose all 220 tools, or select groups such as network, storage, and emulation. The CDP backend is included by default. Firefox and the BiDi backend require the optional bidi installation and the relevant browser driver; ChromeDriver or EdgeDriver is used for Chromium BiDi, while Firefox uses geckodriver.

A minimal uvx configuration uses the wavexis-mcp command with --caps all. The project documents configuration examples for Claude Desktop, Cursor, Windsurf, and VS Code.

Tools and capabilities

Core tools include session lifecycle management, direct and history navigation, waiting, reload and stop controls, screenshots, PDF generation, page snapshots, multi-URL scraping, JavaScript evaluation, CSS-selector DOM queries, attribute changes, scrolling, iframe operations, and shadow DOM evaluation.

Additional capability tiers cover:

  • Network inspection and modification, including headers, throttling, interception, mocking, HAR handling, and request replay.
  • Browser storage, device and viewport emulation, geolocation, locale, timezone, dark mode, touch, and sensors.
  • Accessibility snapshots and audits, downloads, permissions, dialogs, performance, CSS, console, security, and tracing.
  • Coordinate-based mouse input, video capture, assertions, locator generation, YAML workflows, Lighthouse audits, crawling, visual differences, and Core Web Vitals.
  • Experimental browser features such as service workers, WebAuthn, media, extensions, preferences, Bluetooth, and Cast.

Errors include a suggestion field intended to help an LLM choose a corrective action. Stealth mode can hide navigator.webdriver and adjust browser-exposed values such as plugins, languages, and the Chrome runtime.

Limitations and notes

The server depends on a locally available supported browser and, for BiDi use, the appropriate driver. Closing a persistent session terminates its browser process or disconnects from the remote browser and discards unsaved page state. JavaScript evaluation, DOM mutation, navigation, downloads, and network controls can change page state or trigger external requests, so they should be used with appropriate care.

Capability selection affects which tools are exposed to the MCP client. Starting with core and enabling additional tiers keeps the tool set smaller; all exposes the full catalog.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Wavexis MCP

MathiasPaulenko/wavexis-mcp is an MCP server that connects AI clients to the wavexis browser automation library. It controls Chrome, Edge, and Firefox through CDP or BiDi and exposes tools for sessions, navigation, DOM interaction, JavaScript evaluation, scraping, screenshots, PDFs, and browser diagnostics.

Install it with `pip install wavexis-mcp` or run it with `uvx wavexis-mcp`. The server requires Python 3.11, 3.12, or 3.13 and a supported installed browser. Add the command to your MCP client configuration, optionally passing `--caps all` or selected capability tiers.

Yes, Firefox is supported through the BiDi backend. Install the optional BiDi dependency with `pip install "wavexis-mcp[bidi]"` and provide geckodriver. Chrome and Edge use CDP by default, while Chromium BiDi uses ChromeDriver or EdgeDriver.

Open a persistent session with `wavexis_session_open`, pass its `session_id` to subsequent navigation and interaction tools, then call `wavexis_session_close` when finished. For compact sequences, the server also supports multi-action YAML workflows.

No, it requires neither Node.js nor a separate Chromium download. The Python server launches or connects to an existing Chrome, Edge, or Firefox installation, with the required browser driver needed for BiDi operation.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWavexis MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mathiaspaulenko-wavexis-mcp?style=directory)](https://allmcps.com/mcp/mathiaspaulenko-wavexis-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/mathiaspaulenko-wavexis-mcp"><img src="https://allmcps.com/api/badge/mathiaspaulenko-wavexis-mcp?style=directory" alt="Wavexis MCP on AllMCPs" /></a>