- Home
- MCP servers
- DrissionPage
DrissionPage
- python
5
GitHub Stars
python
Language
4 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"jumodada-drissionmcp": {
"command": "drissionpage-mcp",
"args": [],
"env": {
"CHROME_PATH": "/custom/path/to/chrome"
}
}
}
}DrissionPage MCP Server delivers production-ready browser automation for Claude Code, Claude Desktop, and other MCP clients. It provides structured, deterministic web automation through 14 specialized tools, backed by a fast and type-safe engine. You can automate navigation, element interactions, page operations, and waiting behavior to build robust web automation workflows without relying on vision-based approaches.
How to use
You integrate the server with an MCP client by running the local MCP endpoint and registering it in your client’s MCP settings. After installation, you connect your client to a local process that exposes the 14 automation tools. You can then issue natural language prompts to perform actions such as navigating to web pages, locating and interacting with elements, taking screenshots, and extracting data.
How to install
Prerequisites you need before installation are Python 3.8+ and a Chrome or Chromium browser. You also need a client that supports MCP connections, such as Claude Code or Claude Desktop.
# Install the MCP server package from PyPI
pip install drissionpage-mcp
# Verify the installation
drissionpage-mcp --version
Configuration and usage notes
- Standard local server setup (stdio) is used by default. The command to start the MCP server locally is provided as shown below.
{
"mcpServers": {
"drissionpage": {
"command": "drissionpage-mcp",
"args": []
}
}
}
Using with Claude Code or Claude Desktop
After you have installed the MCP server, you add the local server to your MCP client configuration so the client knows where to reach the service. A typical local configuration points to the stdio-based server you started with the command above.
Available tools
page_navigate
Navigate to a URL provided in your prompt, returning the new page context and URL.
page_go_back
Go back in browser history to the previous page.
page_go_forward
Go forward in browser history to the next page.
page_refresh
Reload the current page to get the latest state.
element_find
Find a DOM element using a CSS selector or XPath expression and return a reference for subsequent actions.
element_click
Click the located element to trigger actions such as navigation or form submission.
element_type
Type text into the selected element, with optional delay between keystrokes.
page_screenshot
Capture a screenshot of the full page or the current viewport.
page_resize
Change the browser window size to specified width and height.
page_click_xy
Click a specific point on the page by coordinates.
page_close
Close the browser session and release resources.
page_get_url
Return the current page URL.
wait_for_element
Wait until a specified element appears on the page, with a timeout.
wait_time
Pause execution for a given amount of time.