ascended-browser MCPサーバー
コミット 2026年11月9日AIエージェントがインタラクティブな自動化、フロントエンドのQA、および検証済みのウェブ操作を実行するための、セキュリティを強化したブラウザを提供します。
別名 AceAtDev/ascended-browser
- スター
- 3
- ツール
- 11
- ダウンロード数(30日間)
- —
- 最新バージョン
- —
- 最終コミット
- 2026年11月9日
- ライセンス
- MIT
ascended-browser MCPとは
AIエージェントがインタラクティブな自動化、フロントエンドのQA、および検証済みのウェブ操作を実行するための、セキュリティを強化したブラウザを提供します。 11個のツールを提供しており、browser_open, browser_observe, browser_actなどがあります。
プロジェクトのREADMEから生成された概要
ascended-browser MCP server について
ascended-browserは、AIエージェントによるインタラクティブなウェブ自動化とフロントエンドの品質保証を可能にします。このローカルのオープンソースMCP serverは、ウェブサイトに対して人間が操作しているように見せるよう設計されたFirefoxのバージョンであるCamoufoxを使用し、セキュリティを強化したブラウザ環境を提供します。Claude Code、Codex CLI、Cursorなどのクライアントを使用する開発者が、探索的テストを実施し、ウェブ操作を検証するために構築されています。
ユーザーは、フォーム全体の入力、カスタムReactドロップダウンからのアイテム選択、座標ではなく特定の名称によるナビゲーションといった、検証済みの操作を通じて複雑なタスクを管理できます。このサーバーには、コンソールログ、ネットワークリクエスト、レスポンシブレイアウトの検査機能を含む、デバッグ用の専用ツールが含まれています。また、保存されたログインシステムを通じて安全なセッション管理をサポートしており、パスワードやTOTPシークレットなどの機密性の高い認証情報がAIエージェントに公開されないことを保証します。
セットアップはnpmまたはPython経由で行い、サーバーはxvfbを使用した仮想ディスプレイサポートにより、Linuxの開発環境で実行できます。操作後に何が変更されたかを報告することで詳細なフィードバックを提供し、TurnstileやreCAPTCHAなどのボット検知の課題にも対応可能です。
できること
- 1フロントエンドエラーのデバッグエージェントがネットワークリクエストの失敗やコンソールエラーを特定し、アプリケーションのバグを診断できます。
- 2レスポンシブデザインの検証開発者はエージェントに対し、異なるデバイスのブレークポイントでウェブサイトがどのように表示されるかを確認するよう指示できます。
- 3複雑なフォーム入力の自動化エージェントは、検証済みの操作を使用して、複数のフィールドを持つフォームを一度の操作で完了できます。
- 4認証フローの安全なテストエージェントは、実際のパスワードを見ることはなく、保存された認証情報を使用して保護されたページにサインインできます。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
ascended-browser MCPツール 11
READMEから検出browser_openbrowser_observebrowser_actbrowser_extractbrowser_screenshotbrowser_viewportbrowser_evaluatebrowser_tabsbrowser_flowbrowser_loginwait_for_bot_wall
| browser_open | — | |
| browser_observe | — | |
| browser_act | — | |
| browser_extract | — | |
| browser_screenshot | — | |
| browser_viewport | — | |
| browser_evaluate | — | |
| browser_tabs | — | |
| browser_flow | — | |
| browser_login | — | |
| wait_for_bot_wall | — |
自動チェック
実行日 2026年11月14日完全なレポート →まだ検証されていません。サーバーには80点のスコア、重大な問題がないこと、および検証に必要な十分なデータが必要です。 チェックの仕組み · 点数を上げるための改善点
- ソースリポジトリがリンクされており、アクセス可能aceatdev/ascended-browser is public and reachablegithub.com/aceatdev/ascended-browser ↗合格
- パッケージがこのリポジトリをソースとして指定未チェック
- ビルドの来歴 (Sigstore 証明)未チェック
- オープンソースライセンス (OSI)MITspdx.org/licenses/MIT.html ↗合格
- 過去1年以内にコミットまたはリリースありLast commit or release 2026-11-09github.com/aceatdev/ascended-browser ↗合格
- OpenSSF Scorecard未チェック
- パッケージ名が有名なパッケージに酷似していない未チェック
- パッケージおよびその依存関係に重大な勧告なし未チェック
- モデルへの隠れた指示がない11 tool descriptions and the README read; no override phrases, credential paths or hidden characters合格
- 破壊的なツールがラベル付けされているNo tool named like delete, drop or exec合格
- リモートエンドポイントが MCP ハンドシェイクに応答未チェック
README
GitHubで見るA local, open-source browser MCP server for Codex CLI, Claude Code and other MCP clients. Use it for interactive browser automation and front-end QA: inspect console logs and network requests, check responsive layouts, and collect screenshots alongside what happened on the page.
Your agent opens pages, reads them, and acts on them through verified actions: it fills a whole form in one call, picks "Mrs." from a custom React dropdown by name, and is told what the page did in response, instead of clicking coordinates and hoping.
Ascended is my own private agent workspace; this package extracts its browser so it can run on its own: Camoufox (a hardened Firefox that looks like a person's browser to the sites it visits) behind the same tool dispatcher, page reading and result formatting Ascended's own agent uses.
Start with a QA check
Read the documentation site: QA setup and interrupted-action reproduction.
Running Codex CLI over SSH and missing a browser? Connect a browser MCP on your Linux dev box with setup commands, localhost guidance and alternatives.
Practical recipes with real local-fixture screenshots:
- Find console errors and failed requests.
- Check responsive layouts.
- Test login-protected pages and session reuse.
Set up a browser MCP for Codex CLI or Claude Code and check your app. The guide covers installation, a copy-paste QA prompt, console and network inspection, bug-report structure, and what to do after an interrupted action.
- Check a local app: walk through a flow and report errors before changing code.
- Inspect the evidence: read failed requests and console errors, then capture the broken state.
- Use a Linux dev box: run the client, MCP server and app on the same machine; the guide explains how localhost behaves when you connect over SSH.
This is agent-assisted exploratory QA, not a replacement for deterministic regression tests or a validated CI integration. Browser MCP tools are also available from projects such as Playwright MCP and Chrome DevTools MCP; console and network inspection are not exclusive to this server.
See it work
Three real runs of Claude Code with only this server attached, on live sites.
The panel on the side is Claude Code's own transcript: every tool call it made
and what came back, errors included, with the real elapsed time. Waiting is
cut and tool time plays faster; the pointer, device frames, devtools panels
and outlines are drawn afterwards from the server's event log
(demo/record_demo.py), so they sit on what the agent really touched and read.
The full unedited screen recordings are in videos/unedited/
(the browser is driven through Playwright, so no OS pointer appears in them).
Front-end QA. react.dev on a phone and a tablet, dark/light, before/after screenshots, an audit outlining the real offending elements, console and network.
Browsing. Types into Wikipedia's search, finds a fact in the article, then searches YouTube and plays the first video.
Real forms. booking.com: popup, destination autocomplete, date picker, search, sort by price.
Saved logins. You save a login once; the agent signs in with it and never sees it. Built from a real run (demo/login_demo.py, then demo/login_explainer.py): the CLI's output, the screen, and the exact text and pictures the agent got back.
Click any clip for the full-quality MP4.
Install
From Python (3.11 or newer) or from npm; both run the same server.
uvx ascended-browser doctor # checks the machine; downloads nothing
uvx ascended-browser fetch # downloads the browser now (~700 MB; otherwise on first use)
npx -y ascended-browser doctor # the same, from npm
The browser is Camoufox 135.0.1-beta.24, the build every test here ran on; it is
pinned, so a newer Camoufox release never changes what your agent drives, and
any other Camoufox you have installed is left as it is. Run fetch once before
adding the server to an agent, so its first tool call does not wait for the
download.
The npm package is a small launcher: it runs the Python package with uvx
when uv is installed (uv brings its own Python),
else pipx, else a private venv made with your Python 3.11+. Use whichever
command you prefer in the configs below (npx -y ascended-browser in place of
uvx ascended-browser).
Linux: install xvfb to keep the browser on a virtual display (closest to a
real screen); without it the browser runs headless. On a display,
browser_viewport resizes the real window, so phone and tablet checks reflow
the page at true breakpoints.
Add it to your agent
Claude Code
claude mcp add ascended-browser -- uvx ascended-browser
# or: claude mcp add ascended-browser -- npx -y ascended-browser
Codex
codex mcp add ascended-browser -- uvx ascended-browser
Whether Codex asks before each browser action follows the permission mode you
pick in Codex: under Full access it just runs them; under Ask for approval
it asks first. In a sandboxed mode, codex exec cannot ask and fails every
call: use Full access, or pre-approve this server's tools by adding
default_tools_approval_mode = "approve" under [mcp_servers.ascended-browser]
in ~/.codex/config.toml.
opencode (opencode.json)
{
"mcp": {
"ascended-browser": { "type": "local", "command": ["uvx", "ascended-browser"], "enabled": true }
}
}
Cursor, Windsurf, Claude Desktop and other clients: a stdio server with
command uvx and args ["ascended-browser"], or command npx and args
["-y", "ascended-browser"].
Tools
| Tool | What it does |
|---|---|
browser_open |
Open a URL (or several at once) and return what is on the page, each control with a ref |
browser_observe |
Look at the page again, or narrow to a region, a query or a filter |
browser_act |
navigate, click, fill, fill_form, select, check, date, press, upload, scroll, wait, sequence: each verified, each answered with what changed |
browser_extract |
Read the page's text and field state, find a phrase, list every match of a CSS selector with its text and attributes (every product link, every price), or read=console, read=network, read=inspect, read=audit, read=design to debug a page |
browser_screenshot |
A picture, when an observation cannot describe it: canvas, charts, visual layout; compare_with diffs against an earlier picture or another tab |
browser_viewport |
Resize to phone/tablet/desktop (Linux), emulate dark mode, reduced motion, forced colors or offline |
browser_evaluate |
Read-only JavaScript, policy-checked |
browser_tabs |
List, close or sleep tabs |
browser_flow |
Record a task once, replay it on the next page with new values |
browser_login |
Sign in with a login you saved (see Saved logins); the agent never sees its values |
wait_for_bot_wall |
Wait out a "checking your browser" page; press a Turnstile/reCAPTCHA checkbox if one blocks a form |
Long results come back clipped, with an evidence_ref that
browser_extract pages through, so a huge page cannot flood the agent's
context.
Every action waits for the page to settle, under a hard timeout, and says
when its effect could not be confirmed. If a turn ends while one is still
running, the next turn is told instead of finding a page it cannot explain:
an interrupted click (you stopped the turn) is named in the next result for
that tab, and an action whose server died (claude -p ending, an SSH session
dropping) is listed with the first result of the next session, so the agent
checks before it repeats an order or a form.
Saved logins
Save a login once and the agent can sign in with it, without ever seeing it.
uvx ascended-browser login add github.com --username you@example.com # prompts for the password
uvx ascended-browser login add accounts.example.com --name Work --totp # also a TOTP secret (or otpauth:// URI)
uvx ascended-browser login list # names, usernames, sites; never passwords
uvx ascended-browser login edit Work --password # change only what you pass
uvx ascended-browser login remove Work
The site is the host of the sign-in page (accounts.example.com, not
example.com, when they differ); pass several for one account on several
hosts. Passwords and TOTP secrets come from a hidden prompt, or from stdin
with --password-stdin, never from the command line, where they would end up
in shell history and the process list.
Then ask your agent to sign in. browser_open tells it a saved login exists
for the page, and browser_login finds the username, password and
one-time-code fields and types the values in (submit: true also presses
the button). What the agent gets:
- Every tool result is scrubbed of every saved username, password and TOTP
secret, also URL-encoded, JSON- or HTML-escaped:
browser_observe,browser_evaluate(readinginput.valuereturns[redacted]),browser_extract(page text, field values, network bodies) and action results. A page that prints "Signed in as you@example.com" reads as "Signed in as [redacted]". - Every screenshot is masked before it reaches the agent: password, card and one-time-code fields, username and email fields, and any saved value shown as page text.
For sites a saved login cannot fill (single sign-on, passkeys, a CAPTCHA, a code sent by email), sign in by hand once:
uvx ascended-browser signin https://example.com/login # opens the browser; sign in, then press Enter
The cookies stay in the browser profile that every later agent session starts from. Close running agent sessions first, so the sign-in lands in the saved profile rather than a session's copy.
The vault is logins.db in the data directory, readable only by your user,
and not encrypted (like gh or aws credentials files). The scrubbing and
masking cover what the browser tools return. An agent that also has a
shell or file tools (Claude Code, Codex) runs as you and can read any file you
can, this one included. Deny its file tools the path (in Claude Code,
"deny": ["Read(~/.local/share/ascended/**)"] under permissions in
~/.claude/settings.json) and keep shell commands on approval; an agent free
to run any command can still reach the file. Values shorter than 4 characters
are not scrubbed, and a value the page changes (the last four digits of a
card, say) is not matched.
Settings
| Variable | Default | |
|---|---|---|
ASCENDED_BROWSER_WINDOW |
hidden | show opens a visible window |
ASCENDED_DATA_DIR |
~/.local/share/ascended/browser |
Browser profile (sign-ins persist), saved logins (logins.db), session files |
ASCENDED_RESULT_MAX_CHARS |
24000 |
Longer results are clipped with an evidence_ref |
ASCENDED_SETTING_<KEY> |
Any browser setting, e.g. ASCENDED_SETTING_BROWSER_WORKSPACE_OBSERVE_FORMAT=outline |
|
ASCENDED_LOG_LEVEL |
WARNING |
Logs go to stderr |
Limits
- Window resizing (
browser_viewportphone/tablet/desktop presets or any width and height) works on Linux: on the package's own virtual display by default, or on your X11 display withASCENDED_BROWSER_WINDOW=show. On macOS and Windows the window keeps its launch size; emulation (dark mode, reduced motion, forced colors, offline) works everywhere. Screenshot grids across several sizes in one call are not included. - Schema-shaped extraction (a model reads the page into your JSON shape) is an Ascended app feature that needs a model, so it is not in this package and its parameters are not exposed. Everything listed under Tools runs without a model.
- One server process is one browser session: tabs and refs last until your client disconnects; the profile (cookies, sign-ins) lasts across sessions. Several sessions can run at once: the first one uses the saved profile, and any other one started while it runs gets its own copy, already signed in to whatever the saved profile was. Sign-ins made in a copy end with that session.
How it is built
src/ascended_browser/_app is generated from my Ascended app by
scripts/sync_from_ascended.py: the browser modules taken unchanged, the
browser tool dispatcher and result formatter extracted by reachability, and
every import of the rest of the app rewritten to runtime/ (small standalone
stand-ins). The sync refuses any app import it cannot map.
Tested with Ascended's own stress harnesses run against this package
(tests/stress/), a client-side MCP smoke test (tests/smoke_mcp.py), and
live-website tasks given to real agents (tests/agents/). Saved logins have
their own: tests/test_logins.py (the vault CLI and the scrubber),
tests/login_redaction_mcp.py (a real client signs in on a page that echoes
the login into its text, DOM and network, and no tool may show it; with
tesseract installed it also reads the screenshots) and
tests/signin_persists.py.
What has been verified so far: Linux (Python 3.11, 3.12 and 3.14), with Claude Code and Codex (0.160) on live-site tasks, opencode on a navigation task, and the npm launcher through uvx and through its own venv. macOS and Windows should work headless or with a visible window, but are untested.
License
MIT. The bundled axe-core (_app/browser_vendor/axe-core) is MPL-2.0 and keeps
its notice in the file.
ascended-browser MCPのよくある質問
ascended-browser MCPが提供するツールは
11個のツールを提供しており、browser_open, browser_observe, browser_act, browser_extract, browser_screenshotなどがあります。
エージェントは保存されたパスワードを見ることができますか?
いいえ、エージェントがパスワードの値を見ることはありません。ツールの実行結果からは、保存されたユーザー名、パスワード、およびTOTPシークレットはすべて削除されます。
Pythonを使用してインストールするにはどうすればよいですか?
uvxを使用して、マシンを確認するための doctor コマンド、またはブラウザをダウンロードするための fetch コマンドを実行できます。
これは回帰テストの代わりになりますか?
いいえ、これは決定論的な回帰テストやCI統合のためではなく、エージェントによる探索的なQAを目的としています。