SkillFoxx

Type a name, a task or a service

AIPex

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

MCP server

High risk

We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.

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, checks the risk and pins the version.

Other ways to install

This entry is high risk, so there is no one-click install. Review the code and add the config by hand.

Run in a terminal

claude mcp add --transport stdio aipex-browser -- npx -y aipex-mcp-bridge

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "aipex-browser": {
      "command": "npx",
      "args": [
        "-y",
        "aipex-mcp-bridge"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "aipex-browser": {
      "command": "npx",
      "args": [
        "-y",
        "aipex-mcp-bridge"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Run in a terminal

code --add-mcp '{"name":"aipex-browser","type":"stdio","command":"npx","args":["-y","aipex-mcp-bridge"]}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "aipex-browser": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "aipex-mcp-bridge"
      ]
    }
  }
}

If the file already exists, add the server inside the servers key.

Run in a terminal

codex mcp add aipex-browser -- npx -y aipex-mcp-bridge

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.aipex-browser]
command = "npx"
args = ["-y", "aipex-mcp-bridge"]

If the file already exists, append the block to the end.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "aipex-browser": {
      "command": "npx",
      "args": [
        "-y",
        "aipex-mcp-bridge"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "aipex-browser": {
      "command": "npx",
      "args": [
        "-y",
        "aipex-mcp-bridge"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "aipex-browser": {
      "command": "npx",
      "args": [
        "-y",
        "aipex-mcp-bridge"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "aipex-browser": {
      "command": "npx",
      "args": [
        "-y",
        "aipex-mcp-bridge"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "aipex-browser": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "aipex-mcp-bridge"
      ]
    }
  }
}

If the file already exists, add the server inside the mcp key.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "aipex-browser": {
      "command": "npx",
      "args": [
        "-y",
        "aipex-mcp-bridge"
      ]
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "aipex-browser": {
      "command": "npx",
      "args": [
        "-y",
        "aipex-mcp-bridge"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit 4173fa8.

Text for your agent

Install the AIPex extension in your browser, then add the MCP server: claude mcp add aipex-browser -- npx -y aipex-mcp-bridge, or set command npx with args -y aipex-mcp-bridge in your client config.

Other ways from the author
claude mcp add aipex-browser -- npx -y aipex-mcp-bridge

Adds the MCP bridge that talks to the extension.

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

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.

MCP

Transport
stdio
Authentication
not required

Security check

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

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.

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.

Editors’ pick

CLI, skill and Python library for browser control: the agent clicks, fills forms and reads pages over CDP

CLIHigh risk116.6K
Editors’ pick

A skill that gathers the last 30 days of discussion on a topic from Reddit, X, YouTube, HN, Polymarket and GitHub into one brief

SkillHigh risk63.1K
Official

The Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces

MCP serverMedium risk52.7K
Official

A fast Rust CLI for agent browser automation: accessibility snapshots with element refs, an MCP server and skills

CLIHigh risk43.3K
Foxx AIAIPex

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.