wavexis-mcp
PulseGate's liveness check found it on 14 Sep 2026; it is registered on GitHub and PyPI and has been in the index since 27 Jul 2026. How this is checked
wavexis-mcp is an MCP (Model Context Protocol) server that makes the wavexis browser automation library available to large language models. It provides 220 tools across 13 capability tiers for tasks including web scraping, screenshots, and Chromium-based automation using BiDi and CDP protocols. The package is distributed on PyPI under an MIT license and is intended for developers integrating advanced browser control into LLM-powered agents.
Inferred · not functionally tested
Overview
5 featuresPurpose: Providing LLMs with a standardized, high-capability interface for browser automation without requiring Node.js dependencies.
Inferred · not functionally tested
Audience: developers
Inferred · not functionally tested
Functions: browser_automation, agents, data_extraction
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted, api_only
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: pypi.org · github.com. These links do not verify the individual claims.
wavexis-mcp is a Browser DevTools & extensions project. Inferred · not functionally tested: It focuses on providing LLMs with a standardized, high-capability interface for browser automation without requiring Node.js dependencies. Inferred · not functionally tested: It is built as an open-source project for developers. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: It runs on the command line and API, and it can be self-hosted.
It is developed by Mathias Paulenko, and it first shipped in 2026. Development happens publicly on GitHub with 96 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include Browser Automation, LLM Integration, and 220 Tools. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Browser Automation
- LLM Integration
- 220 Tools
- Screenshot Capture
- Web Scraping
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
2What PulseGate has recorded for this listing
Frequently asked questions about wavexis-mcp
- What does wavexis-mcp do?
- Inferred · not functionally tested: Wavexis-mcp focuses on providing LLMs with a standardized, high-capability interface for browser automation without requiring Node.js dependencies. It is catalogued under Browser DevTools & extensions on PulseGate.
- Who should use wavexis-mcp?
- Inferred · not functionally tested: wavexis-mcp is an open-source project built for developers.
- Does wavexis-mcp have a free plan?
- Basis unknown · not verified: Yes — wavexis-mcp is open source under the MIT license and free to use.
- What platforms does wavexis-mcp run on?
- Basis unknown · not verified: wavexis-mcp runs on the command line and API. It can also be self-hosted.
- Is wavexis-mcp still active?
- PulseGate's liveness check found it on 14 Sep 2026. Its GitHub repository shows 96 commits in the last 90 days.
- What are alternatives to wavexis-mcp?
- Similar projects tracked by PulseGate include wm-mcp, wuwa-mcp, and Wwise MCP Server.wm-mcpwuwa-mcpWwise MCP Server
- Who develops wavexis-mcp?
- wavexis-mcp is developed by Mathias Paulenko.
- When did wavexis-mcp launch?
- wavexis-mcp first shipped in 2026.
Similar projects
Closest matches by what these projects do