Drissionpage

DrissionPage MCP Server provides a production-ready interface for browser automation via MCP clients such as Claude Code and Claude Desktop. It exposes 14 deterministic, type-safe automation tools built on DrissionPage to perform navigation, element interaction, page operations, and wait utilities, enabling structured, scriptable web automation instead of relying on vision-based methods. Clients send natural-language prompts that are translated into tool calls (e.g., page_navigate, element_find, page_screenshot) to perform actions on a real browser session managed by the server. This setup is ideal for tasks like automated form submission, data extraction, page state verification, and monitoring across websites with high reliability and reproducibility.

To use it, install the MCP server (via pip install drissionpage-mcp) and run the server binary (drissionpage-mcp). Configure your MCP client (Claude Code/Claude Desktop or other MCP clients) to point at the server using the provided mcp configuration. The server exposes the 14 tools under the four capability groups: Navigation, Element Interaction, Page Operations, and Wait Operations. Examples include navigating to a URL, finding and clicking elements, taking screenshots, resizing the browser, and waiting for elements to appear. The tools are designed with type hints and Pydantic validation to ensure structured data exchange between the client and server.

Prerequisites

• Python 3.8 or newer
• Chrome or Chromium installed on the host machine

Installation steps

1. Create and activate a Python environment (optional but recommended):
   • venv: python -m venv venv
   • source venv/bin/activate (Linux/macOS) or venv\Scripts\activate (Windows)
2. Install the MCP server package from PyPI:

   pip install drissionpage-mcp
   

3. Verify installation and version:

   drissionpage-mcp --version
   

4. Run the MCP server (default command name provided by the package):

   drissionpage-mcp
   

5. Configure your MCP client with the server settings (see mcp_config below).

Optional advanced configuration

• You can pass additional runtime arguments, e.g. increased logging:

  drissionpage-mcp --log-level DEBUG
  

• Set environment variables for Chrome path if needed (see mcp_config example in this document): CHROME_PATH=/path/to/chrome export CHROME_PATH

Tips and considerations:

• The server expects a Chrome/Chromium browser; ensure it is installed and accessible. If you encounter browser startup issues, specify CHROME_PATH to point to the browser executable.
• For production usage, you can enable verbose logging via --log-level DEBUG to diagnose issues with MCP client integration.
• In Claude Code, ensure the MCP settings JSON includes the drissionpage server configuration as shown in the examples. Restart Claude Code after changes.
• The 14 tools are grouped into Navigation, Element Interaction, Page Operations, and Wait Operations. You can combine tool calls through natural-language prompts that map to these tools.
• If you update the server, re-test with a simple prompt to confirm connections before moving to complex automation tasks.