Web MCP Server

This application is a library for automating with Selenium. Exposed over MCP by the web mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A Python based SDK for web automation using Selenium.

To use this application you must have any of the following browsers installed:

Adding it to your client

The server ships on PyPI as browserdriver, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

• Chrome — Firefox
• Opera — Edge

Configuration

You will need 2 environment variables: CHROME_DRIVER, YOUR_CHROME_DRIVER_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the web mcp server does with a few real requests.

When to reach for it

This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Web's toolset — Chrome, Opera — is a fair guide to whether it matches your workflow. It is maintained by Mauricio; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.