SkillFoxx

AIPex MCP

An MCP bridge to control your browser from a coding agent: a Chrome extension and a set of tab and page automation tools

  • 1,285 ★ on the repository
  • Last commit
  • MIT
MCP server

Broad access

Why this level

  • It controls your real browser with open sessions
  • It can perform on-page actions and read page content
All reasons and checks

aipexstudio/aipexAuthor:AIPexStudio

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/aipex

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • It controls your real browser with open sessions
  • It can perform on-page actions and read page content

This is third-party code. Review the repository files before installing.

What it does

AIPex gives a coding agent access to your browser through an MCP bridge. The agent runs over stdio, the bridge talks to the extension over WebSocket, and through it a set of automation tools is available: working with tabs, history, pages and on-page actions. Data stays on your machine, and you bring your own model key. The same bridge provides a browser CLI, so the browser can be driven from scripts and from agents like Cursor, Claude Code and VS Code Copilot.

Who it is for. For developers and testers who need to automate an existing browser from an agent.

Good fit when

  • You need to drive an already open browser from an agent
  • You need tab, page and action automation without a separate browser
  • You want one bridge for agents and scripts via a CLI

Not a fit when

  • You cannot install a browser extension
  • You need isolated headless automation rather than driving your personal browser

Example request

Open these tabs, collect the needed data from them and compile it into a table

MCP

Transport
stdio
Authentication
not required

Limitations

You must install the AIPex extension in Chrome or Edge; the MCP bridge alone does not launch a browser. Automation runs in your real browser, so actions are visible and affect open sessions. You bring your own model key.

How to disable. Remove the aipex-mcp-bridge entry from your MCP client config and uninstall the AIPex extension from the browser.

FAQ

Do I need a separate browser app?

No, AIPex works in your normal browser through an extension, with no separate browser to install.

Can I drive the browser from scripts?

Yes, the bridge ships a browser CLI that talks to the same local daemon as MCP.

Discussion

No questions or reviews yet.

MCP servers
Official

An MCP server and Chrome extension that let the agent drive your already open browser with your logged-in sessions, all locally

MCP serverBroad access7.3K

A CLI and MCP server that lets an agent drive your real Chrome with its logged-in sessions: 103 commands across 36 platforms plus browser automation

CLIBroad access6.3K

An MCP server that drives your already open Chrome and stops to ask you about a 2FA code, a CAPTCHA, or a choice only you can make

MCP serverBroad access62

A Chrome extension with an MCP server: the agent drives your everyday browser with its sessions, tabs, bookmarks and history

MCP serverBroad access12.5K
Official

A local browser automation platform: MCP server, CLI and skills so an agent can drive Chrome, fill forms and pull data from pages

MCP serverBroad access1.4K

README in short

The README describes AIPex as an open-source browser automation tool that lives in your normal browser. For coding agents there is the aipex-mcp-bridge MCP: the agent talks over stdio to the extension over WebSocket and gets a set of browser automation tools. Data stays on the machine, and the user brings the model key. The same bridge provides a browser CLI. MIT licensed.

README badge

Report a problem