Airsc miễn phí cho tất cả. Nếu nó giúp bạn, hãy ủng hộ $2–$20.

Ủng hộ
ENĐăng nhập
MCP serverCẩn thậnTự động trình duyệt & dữ liệu webCần cài đặt chút Đã chạy thử thật

RPA

A9T9 · A9T9/RPA

Máy chủ MCP này cho phép các tác nhân AI tự động hóa các tác vụ trình duyệt và máy tính để bàn bằng cách sử dụng macro, JavaScript, OCR và nhận dạng hình ảnh.

Tự động hóa trình duyệt và máy tính để bàn với MCP server dành cho trợ lý AI. Ghi macro hoặc viết JavaScript để tự động hóa trang web, trích xuất dữ liệu và điều khiển ứng dụng máy tính để bàn bằng OCR và nhận dạng hình ảnh.

2.1k sao415Giấy phép: Không có giấy phépCập nhật 13 ngày trước0 lượt mở

Xem trước

▍

Bạn có thể làm gì với nó

  • Tự động trích xuất dữ liệu từ các trang web.
  • Điều khiển các ứng dụng máy tính để bàn cho các tác vụ lặp đi lặp lại.
  • Kiểm tra chức năng trang web bằng cách phát lại các tương tác.

Đã chạy thử thật · 25 tool

Chúng tôi đã khởi động MCP server này trong máy ảo cách ly, và nó cung cấp các tool sau:

  • bridge_status

    Reports whether the Ui.Vision browser extension is currently connected to this bridge. Call this first if other tools fail — it tells you whether the extension side panel is open and the bridge is ena

  • run_status

    What the macro runner is doing RIGHT NOW: whether a run is in progress, which macro the editor holds, and the freshest log lines. Unlike every other tool, this ANSWERS WHILE run_macro is still executi

  • select_browser

    Switches which connected browser the other tools talk to. Several browsers (or several instances of one browser) can hold a bridge connection at the same time; bridge_status lists their labels. Pass a

  • open_panel

    Opens the Ui.Vision panel when the extension is NOT connected: signals the browser over a background wake channel (extension 10.0.170+) to open the Ui.Vision app in a tab. This is the ONLY way the pan

  • list_macros

    Lists all macros stored in Ui.Vision (name and id). Use open_macro to load one into the editor before reading or running it.

  • open_macro

    Opens the macro with the given name in the Ui.Vision editor and returns its JSON. Subsequent get_macro/set_macro/run_macro calls operate on it. Note: unsaved editor changes may be discarded.

  • get_authoring_guide

    Returns the Ui.Vision macro authoring guide: the uiv.* JavaScript API for JS script macros (finders, actions, OCR, vision), the classic command table, locator rules and best practices. CALL THIS ONCE

  • get_macro

    Returns the macro currently loaded in the Ui.Vision editor, as Ui.Vision JSON. A JS script macro comes back with a "Script" field (its program) instead of Commands.

  • send_chat

    Sends a message to the REAL in-panel AI Chat — the configured chat model runs it with its own agent tools, exactly as if a user had typed it. Returns immediately; a chat run takes minutes, so poll get

  • get_chat

    Returns the in-panel AI Chat transcript and whether a run is in progress (running:true/false). Poll this after send_chat; the transcript is text-only (inline images are omitted).

  • reload_extension

    Reloads the Ui.Vision extension from disk (same as the chrome://extensions reload button) — the way to load a freshly built version without a human click. The bridge connection dies with the panel; on

  • run_selftest

    Runs every self-test of Settings > Desktop Automation in one go: native host connection, WASM image-search engine, desktop screenshot, real mouse input delivery, home-directory read/write, visual comp

  • get_ai_settings

    Reports the ACTIVE AI provider/model as the chat will resolve it, which providers have keys stored (booleans only — keys never cross the bridge), the per-provider model settings, computer-vision scope

  • set_ai_settings

    Switches AI settings for independent runs (e.g. benchmark sweeps): provider (uivision | openrouter | anthropic | local), uivision_tier (free | pro), openrouter_model / anthropic_model / local_model /

  • set_macro

    Apply changes to the macro in the Ui.Vision editor — pass the complete Ui.Vision JSON. PREFER the JS script form {"Name": "name", "Script": "<JavaScript using the uiv.* API>"} over the classic Command

npx -y uivision-mcp-bridge · 6/10/2026

Kiểm tra an toàn

Cẩn thận

Dùng được, nhưng nên đọc ghi chú trước.

  • ●Không có giấy phép rõ ràng: hỏi tác giả trước khi dùng cho sản phẩm thương mại.

Quét tự động các file trong repo. Luôn xem lại code trước khi chạy.

Trích từ README

Ui.Vision - Browser and Desktop Automation

Automate websites and desktop applications with macros, JavaScript, or an AI assistant. Ui.Vision combines browser automation, OCR and image recognition, with an MCP server that lets AI agents create, edit and run reusable macros in your browser.

Install the extension · Connect an AI assistant with MCP · API reference · User forum

What can you automate?

  • Browser tasks: fill forms, extract web data, download reports and repeat workflows in your existing browser session.
  • Website testing: record and replay interactions, use Selenium IDE commands, and run checks with different input data.
  • Visual tasks: find on-screen text with OCR and locate controls by image when HTML selectors are unavailable.
  • Desktop workflows: automate applications and remote desktop interfaces using visual recognition and mouse and keyboard input. Desktop automation requires the additional Ui.Vision desktop components (XModules).
  • AI-assisted automation: ask the built-in AI assistant or an external MCP client to write and run macros, then inspect the resulting script, logs and screenshots.

Use the macro recorder and command table, write JavaScript with the uiv.* API, or let an AI assistant author the macro. The resulting automation can be saved and run again.

Get started

Install the browser extension; you do not need to build this repository:

Open Ui.Vision and record a browser task, or start with a macro from the extension's demos. For desktop input and additional native capabilities, see the XModules installation guide.

The browser extension is open source and free for personal and commercial use. See the Ui.Vision website for desktop components and available editions.

Connect an AI assistant with MCP

Ui.Vision provides a Model Context Protocol (MCP) server through the uivision-mcp-bridge package. It connects MCP clients such as Claude Code, Claude Desktop and Cursor to the Ui.Vision browser extension.

An agent can inspect a page, create or edit a macro, run it, and use logs and screenshots to check the result. The automation executes through Ui.Vision in your browser.

Start with the MCP setup guide. The installer command is:

npx uivision-mcp-bridge --setup

The installer registers Ui.Vision with supported MCP clients found on your machine. Then enable the MCP bridge in Ui.Vision → Settings → AI, complete the connection steps in the guide, and restart your MCP client. Node.js and npm are required to run the installer.

For a first task, ask your connected assistant:

Use Ui.Vision to open https://example.com, read the page heading, and save a reusable macro for this task.

See mcp/README.md for bridge source, configuration and troubleshooting.

JavaScript automation and documentation for AI assistants

The uiv.* JavaScript API covers page elements, visual matching, OCR, browser and desktop input, screenshots, tabs, CSV files and downloads. Ui.Vision macros execute sequentially: write API calls without async or await.

When asking an AI assistant to write a macro, give it the API reference below so it uses Ui.Vision's supported methods and runtime conventions.

Help and support

Ask questions and share automation examples in the Ui.Vision user forum, where users, support staff and developers participate.

Build from source

Building the extension is not required if you "only" want to use it.

You can install UI.Vision directly from the Chrome, Edge or Firefox stores, which is the easiest and the recommended way of using the Ui.Vision browser extension. Older versions can be found in the RPA software archive.

The information below is only required and intended for developers:

The project uses Node V20.11.1 and NPM V10.2.4

If you have any questions, please contact us at TEAM AT UI.VISION - Thanks!

Build the extension bundle

npm i -f

npm run build

npm run build-ff

npm run build creates the Chrome/Edge build in dist, npm run build-ff creates the Firefox build in dist_ff.

Develop

npm i -f

npm start

Use npm run start-ff for the Firefox variant. Both run webpack in watch mode, so the bundles in dist (Chrome/Edge) and dist_ff (Firefox) are rebuilt on every change.

Once done, the ready-to-use extension code appears in the /dist directory (Chrome, Edge) or /dist_ff directory (Firefox). Load it via chrome://extensions → "Load unpacked" (Chrome/Edge) or about:debugging → "Load Temporary Add-on" (Firefox).

Repository layout

  • src/ - the extension source (React UI, side panel, macro player, commands)
  • extension/ - static extension assets and manifest.json (Manifest V3)
  • mcp/ - the Ui.Vision MCP bridge, which lets Claude Code an
Xem mã nguồn trên GitHub