Mcp Aoai Web Browsing

Created By
kimttha year ago
A minimal Model Context Protocol 🖥️ server/client🧑‍💻with Azure OpenAI and 🌐 web browser control via Playwright.
Overview

what is Mcp Aoai Web Browsing?

Mcp Aoai Web Browsing is a project that implements a Model Context Protocol (MCP) server/client application utilizing Azure OpenAI to enable web browser control through Playwright.

how to use Mcp Aoai Web Browsing?

To use the project, set up the server by configuring the Azure OpenAI parameters in the .env file, and run the chatgui.py script to launch the client interface that navigates to specified URLs.

key features of Mcp Aoai Web Browsing?

  • Integration of Azure OpenAI with custom server-client architecture.
  • Usage of Playwright for web testing and automation.
  • Ability to navigate and interact with web pages programmatically.

use cases of Mcp Aoai Web Browsing?

  1. Automating browser interactions for testing web applications.
  2. Interacting with dynamic web content based on AI-generated commands.
  3. Creating automated reports or summaries from web page content.

FAQ from Mcp Aoai Web Browsing?

  • What is the Model Context Protocol (MCP)?

MCP is an open protocol that facilitates secure communication between AI applications and other resources.

  • Is there any specific Python version requirement?

It is advised to use Python with support for the required dependencies and libraries during setup.

  • How can I contribute to the project?

Contributors can check the official repository for guidelines on contributing and expanding functionalities.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kimtth
Star
20
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago