MCP Aoai Web Browsing MCP Server

A minimal Model Context Protocol 🖥️ server/client🧑‍💻with OpenAI and 🌐 web browser control via Playwright. The mcp aoai web browsing mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.

What it actually does

1. The MCP server is built with FastMCP. 2. Playwright is an an open source, end to end testing framework by Microsoft for testing your modern web applications. 3. The MCP response about tools will be converted to the OpenAI function calling format. 4. The bridge that converts the MCP server response to the OpenAI function calling format customises the MCP-LLM Bridge implementation. 5. To ensure a stable connection, the server object is passed directly into the bridge. 6. The client_bridge supports both in-process and external (stdio) MCP server connections, enabling reuse by different clients (e.g.

Its toolset

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

• Configuration — During the development phase in December 2024, the Python project should be initiated with 'uv'. Other dependency management libraries, such as 'pip'

Adding it to your client

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

Configuration

You will need 5 environment variables: AZURE_OPEN_AI_ENDPOINT, AZURE_OPEN_AI_API_KEY, AZURE_OPEN_AI_DEPLOYMENT_MODEL, AZURE_OPEN_AI_API_VERSION, OPENAI_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.

When to reach for it

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Aoai Web Browsing's toolset — Configuration — is a fair guide to whether it matches your workflow. It is maintained by kimtth; 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.

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.
• 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 mcp aoai web browsing mcp server does with a few real requests.