A community-maintained local browser automation MCP server built on DrissionPage that exposes 69 typed atomic tools over stdio, covering navigation, tabs, element interaction, screenshots, frames and Shadow DOM, cookies and storage, network observation, waits, and console logs. It is structured-first with optional coordinate and deterministic natural pointer motion, and it redacts URLs, credentials, headers, cookies, network bodies, and related metadata by default. All tools load by default, there are zero prompts, and the only resource is a static optional-Skills catalog. It is beta software under Apache 2.0 and is not an upstream official project; real behavior depends on the local Chrome/Chromium and target sites, so use a dedicated browser profile and verify results.
DrissionPage MCP Server is a local Model Context Protocol server that exposes DrissionPage's browser automation capabilities as 69 typed, atomic tools to Codex CLI/IDE, Claude Code, Claude Desktop, Cursor, and other MCP clients. It runs over stdio, installs from the PyPI package drissionpage-mcp, and requires Python 3.10+ plus a local Chrome or Chromium. The design is structured-first and vision-ready: use DOM structure when reliable selectors exist, and coordinates with either direct or bounded deterministic natural pointer motion for canvas, map, chart, and other visual-only surfaces. The server executes exactly the requested browser operation; site flows, component-library adaptation, challenge handling, and business policy belong to the client or optional Skills. It exposes zero MCP prompts and one static optional-Skills catalog resource. The project is in beta, licensed under Apache 2.0, and maintained by a community author rather than the upstream product owner.
{
"mcpServers": {
"drissionpage": {
"command": "drissionpage-mcp"
}
}
}