Web Agent Protocol MCP Server

Web Agent Protocol MCP server exists for a simple reason — assistants are far more useful when they can act on Web Agent Protocol directly instead of describing what you should do. 🌐Web Agent Protocol (WAP) - Record and replay user interactions in the browser with MCP support.

What you get

The Web Agent Protocol (WAP) is a standardized framework designed to enable seamless interaction between users, web agents, and browsers by recording and replaying browser actions. It separates the concerns of action recording and execution, allowing for efficient automation and reusability. The Python SDK for WAP implements the full specification, making it easy to:

What the assistant can call

Once Web Agent Protocol is connected, these are the calls the assistant has available:

• Mode — Command

Configuration and credentials

You will need 3 environment variables: PYTHONPATH, OPENAI_API_KEY, DEEPSEEK_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Web Agent Protocol's toolset — Mode — is a fair guide to whether it matches your workflow. It is maintained by OTA-Tech-AI; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• 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.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the web agent protocol mcp server does with a few real requests.