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.
Strongest · Documentation 15/20 Weakest · Reliability 11/20
Static review · not runListed 2026-09-18
Read the FMRS scoring method →Runtime：Python 3.10+ · Prebuilt binary
CHROME_PATH
Optional; path to a custom Chrome executable, defaults to system Chrome/Chromium.
DP_HEADLESS
Optional; set to 1 to launch the browser headless.
DP_NO_SANDBOX
Optional; only for restricted container/root environments, Chrome sandbox stays enabled by default.
DP_MCP_DOWNLOAD_ROOT
Root directory where element_click_and_download saves download artifacts.
DP_MCP_UPLOAD_ROOT
Root directory from which element_upload_file may read files for upload.
DP_MCP_SCREENSHOT_ROOT
Root directory where page_screenshot_save stores screenshots.
DP_MCP_ARTIFACT_ROOT
Root directory where page_export_artifact stores PDF/MHTML artifacts.
{
"mcpServers": {
"drissionpage": {
"command": "drissionpage-mcp"
}
}
}
Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.
{
"servers": {
"drissionpage": {
"command": "drissionpage-mcp"
}
}
}
Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).
claude mcp add drissionpage -- drissionpage-mcp
Run it in a terminal; replace any <…> placeholders with your own values first.
Run drissionpage-mcp --version to confirm the installed version, then run drissionpage-mcp doctor and confirm mcp_supported and mcp_server_wiring are both ok; after restarting the client, the tool list should show the 69 tools including page_navigate and page_screenshot.
Once connected, you can ask your AI assistant things like:
No matching tools
Listed from the project's documentation, not tested by this site.
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.
Microsoft's official Playwright-based browser automation MCP server
The Chrome team's official MCP server exposing Chrome DevTools capabilities to AI assistants
Control the FSB browser extension from any MCP client for DOM-first AI browser automation.
Playwright-based browser automation MCP server
Source revision 140756ac4e70 Data synced 2026-11-02 Read the FMRS scoring method