aevra
Current source release: 1.3.0. Standalone browser and desktop source releases: 1.0.0 each.
エージェントを強化
公開元自身のコマンドです。PlugMCP のエンドポイントではありません。
キーとログ付きでコピーをホスト。
npx -y @the-long-ride/[email protected]Claude Code にはローカルコマンド用のインストールリンクがありません。下のコマンドをコピーして、ターミナルで実行してください。
claude mcp add the-long-ride-aevra -- npx -y @the-long-ride/aevra@1.3.1ターミナルで実行します。
{ "mcpServers": { "the-long-ride-aevra": { "command": "npx", "args": [ "-y", "@the-long-ride/[email protected]" ] } }}claude_desktop_config.json
リモート URL か、手元のマシンのコマンドか 2 つのインストール方法の違い
PlugMCP で実行
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
起動aevra is a local MCP execution gateway that lets AI assistants (such as ChatGPT, Claude, and Grok), any AI platform with an MCP connector, and all AI coding agents (such as Cursor, Windsurf, Claude Code, Cline, Roo Code, and Copilot) work directly on your machine: edit files, run commands, manage Git repositories, automate desktop software, drive browsers, and bridge upstream MCP servers under explicit security boundaries.
As a unified MCP gateway, aevra acts as both a secure execution host and an upstream proxy aggregator. It serves 74 built-in system tools while republishing external downstream MCP servers under collision-resistant namespaces (server__tool). When an AI client requests an action, aevra validates the request against your configured capability profile, enforces fine-grained path and command policies, prompts for human approval on sensitive operations, and records each action to a tamper-evident audit log.
It supports any client or platform using the Model Context Protocol (MCP) standard, runs on Windows, macOS, and Linux, and connects over local loopback, private networks, or public tunnels with floating-IP session continuity.
Ingress Clients:
- AI Web Clients & Assistants (ChatGPT, Claude, Grok, Gemini, Langdock, Manus)
- AI Coding Agents & Other MCP Platforms (Cursor, Windsurf, Claude Code, Cline, Roo Code, any MCP connector)
- Remote Supervisor Devices (Phones, tablets, secondary browsers accessing Admin Web UI)
│
Public MCP Gateway (Port 47830 - Direct HTTPS / Cloudflare / Tailscale / ngrok / SSH)
│
┌─────────────────────────┴─────────────────────────┐
│ │
MCP Data Plane (Port 47832) Admin Control Plane (Port 47831)
aevra Core Daemon React Web UI
(policy · sessions · floating-IP continuity (approvals · live activity · settings · MCP upstreams
· token metering · result shaper) · token usage analytics · tool surface controls)
│
Local IPC (named pipe / unix socket)
│
Execution Worker
├─ Filesystem & Git repositories
├─ Shell execution & managed background processes
├─ Desktop control (Windows UIA · macOS AX · Linux AT-SPI semantic actions)
├─ Browser control (Chromium MV3 extension & CDP)
└─ Upstream MCP proxies & container sandbox
The central invariant: The Core decides authority. The Worker executes only the exact authority it receives.
Run aevra agent list to see which of Codex, Claude Code, OpenCode and Antigravity
Aevra detects, then aevra agent install to connect them: it lists the detected
agents and asks to confirm (--yes skips the question). You can also name targets,
for example aevra agent install codex or aevra agent install all. stdio is the
default; --transport http selects native HTTP for global connections. Add
--workspace <name> to connect an agent to one registered workspace only (stdio,
no skill). Settings offers the same controls, including a Connect dialog.
Each target gets its own credential, and existing gateway approvals and access
policy apply through either transport.
Skills live in ~/.agents/skills/aevra, with managed links into agent-specific
folders. aevra agent uninstall <target|all> removes owned registration/link
resources and revokes credentials. aevra uninstall --purge additionally removes
owned service/state resources; user changes and the other product's shared files
are preserved. Use --dry-run to inspect an installation or removal first.
A single loaded extension serves both products. Pair with root Aevra's port
47831, or standalone Browser's port 47841, using a fresh code. One server is
active at a time. See the local agent guide
for transport, shared installation, cleanup and TLS details.
Keep using your mouse and keyboard while an agent works through supported background actions in another application or browser tab. Desktop semantic operations address controls through UIA, AX or AT-SPI; browser actions address a selected tab through the extension or CDP. These paths avoid driving the system cursor or typing into whichever application you happen to be using.
For desktop work, prefer desktop_describe(mode:"background") with desktop_invoke, desktop_set_value, desktop_select and desktop_toggle. For browser work, keep the agent pinned to its task tab while you use another tab or application. Coordinate edits to the same document, page or field: background targeting avoids input-device conflicts but does not merge simultaneous edits.
Explicit desktop foreground click/type/key/scroll tools use shared OS input and need a coordinated turn. An application can also change focus or open a modal after a semantic action; a reported focusChanged suspends the desktop lease until a fresh describe. Explicit browser tab-focus commands change the selected tab, and the extension's visible-tab screenshot path requires an active tab rather than activating a background tab silently.
Shared engine, different products: root Aevra and Aevra Desktop use the same canonical native desktop implementation, including the background semantic path. Root runs it through a helper process under gateway policy; standalone runs it in-process under its app allowlist. They have independent sessions, grants and configuration. The common engine does not coordinate competing operations from both hosts on the same target.
Choose the gateway when browser and desktop actions belong to a wider workspace workflow with centralized policy and audit. Choose either standalone project when its focused toolset is all you need. Their access models and configuration are independent of the gateway.
These changes are tracked under 1.3.0; source versions are Aevra 1.3.0 and both standalone packages 1.0.0. Native macOS, physical-GPU capture and production Wayland approval/lock acceptance remain open. See desktop platform support and Wayland setup. Aevra Browser retains its separately pinned driver/extension snapshot.
Most local MCP servers do one job (files, a shell, or a browser) and trust whichever client launched them. aevra puts one policy layer in front of all of it.
server__tool, and aevra stops serving one if its schema changes unexpectedly.file_read_many, file_write_many, command_run_many) and bounded browser and desktop plans do in one call what would otherwise take many.maxOutputChars) enforced. Connectors can toggle tool groups off to send only the tools that model needs.heuristic-v1). Non-sensitive metrics accumulate in memory and persist to SQLite (token_usage table) with automatic 7-day roll-up. The React Admin Dashboard features live stat cards and an interactive historical SVG chart (24h to all-time), and an All-time statistics modal with totals and tool/connector breakdowns. See the token usage and tool surface guide.files, commands, git, changes, skills, browser, desktop, control, upstream) per AI client to drastically reduce session token overhead. Select between dual both, text-only, or structured MCP result formats.desktop_invoke, desktop_set_value, desktop_select, desktop_toggle, desktop_release_window, and background desktop_describe use native accessibility providers (UIA / AX / AT-SPI) without moving physical pointers, synthesizing host mouse or keyboard input, or stealing window focus. Windows keeps its additional integrity/secure-desktop defenses; macOS/Linux surface permission/provider failures explicitly. Strict isolated control never downgrades to the host session and is refused until a separately qualified runner is available. See the desktop control guide.browser_* tools drive Chromium browsers through the Aevra MV3 browser extension or Chrome DevTools Protocol (CDP) under capability, risk, approval, DLP, and audit controls. It operates as a true background auto-clicker: CDP actions are target-pinned without activating another tab, and extension interactions work seamlessly in background tabs without stealing focus. Enhanced canvas and WebGL handling: drives HTML5 canvas viewports and web games with high-reliability vision coordinate mapping and native browser mouse clicks and drags (Input.dispatchMouseEvent via Chrome debugger or CDP) instead of brittle synthetic DOM events. Extension snapshot refs resolve through isolated-world opaque element identities rather than page-writable DOM attributes. browser_execute_script accepts a bounded Playwright-like action grammar for single-call multi-step interaction without exposing arbitrary JavaScript evaluation, and credential fields remain refused. The Web UI and aevra status report pairing state, with download and load-unpacked instructions via aevra extension install. See the browser control guide.control_observe, control_execute, owner-bound status/cancel, and desktop_act_many let Aevra validate, schedule, dispatch, and verify bounded browser/desktop workflows locally. Durable request IDs prevent blind replay after reconnect/restart, and compact deltas reduce model round trips.claimExecution) to prevent double execution, shares connection rate limiters, and retains runner origin IPs in audit logs for 24 hours.429 with Retry-After, the login page shows a countdown, and each lockout is audited as a security event and raised as a desktop notification. See the security guide.aevra_status MCP tool reports toolchains, available shells, and execution defaults to models and the Admin UI.aevra://skill/<source>/<name>) and instruction prompts parsed from AGENTS.md and CLAUDE.md.aevra mcp. Upstream tools republish under collision-resistant namespaced identifiers, with secret-backed credentials and catalog fingerprinting that pauses serving if schemas change unexpectedly. Servers can be disabled and re-enabled from the Admin UI or aevra mcp enable|disable <id> without losing their configuration. When a server changes its catalog, aevra mcp list marks it with ! and prints a next-step hint; aevra mcp review <id> shows what changed and aevra mcp accept <id> --yes accepts it. See the MCP upstreams guide.aevra.json): Workspaces can advertise build, test, and lint commands, and declare sensitive or secret path globs that feed directly into the file security boundary. See the manifest design specification./api/data/export and /api/data/import), excluding machine-specific secrets for safe portability.Install aevra globally via npm and start the gateway on your operating system:
# 1. Install aevra globally
npm install -g @the-long-ride/aevra@latest
## Choose 2.1 or 2.2:
# 2.1 Configure admin credentials for User scope (persists across sessions):
[System.Environment]::SetEnvironmentVariable('AEVRA_USERNAME', 'admin', 'User')
[System.Environment]::SetEnvironmentVariable('AEVRA_PASSWORD', 'YourSecurePassword', 'User')
# 2.2. Apply to current session only:
# $env:AEVRA_USERNAME = 'admin'
# $env:AEVRA_PASSWORD = 'YourSecurePassword'
# Start aevra with dashboard in browser
aevra start --ui
# If a default port is occupied, move all listeners to 50000 through 50003:
aevra start --ui --basePort=50000
# 1. Install aevra globally
npm install -g @the-long-ride/aevra@latest
# 2. Configure admin credentials and launch daemon with Web UI
export AEVRA_USERNAME="admin"
export AEVRA_PASSWORD="YourSecurePassword"
aevra start --ui
# Or select ports individually (the aliases are --gp, --up, --mp and --wp):
aevra start --ui --gateway-port=50000 --ui-port=51000 --mcp-port=52000 --ws-port=53000
(Optional) Run aevra automatically as a user-level background service:
aevra service install
aevra service start
aevra exposes a standard MCP endpoint (/mcp) that can be accessed directly over HTTPS (such as https://localhost:47830/mcp or direct IP/domain) or exposed to the internet through a tunnel (Cloudflare Tunnel, ngrok, Tailscale Funnel, Caddy, FRP, reverse SSH).
aevra (or any custom name)https://<your-aevra-host>/mcp (your tunnel or public URL)OAuthhttps://localhost:47831) and click Allow on the pairing request.Claude example:
aevra (or any custom name)https://<your-aevra-host>/mcp (your tunnel or public URL)OAuthAevra cannot guarantee that an HTTP or MCP transport remains open indefinitely. It maintains logical continuity across reconnects by accepting short-lived access tokens and rotating refresh tokens against the same connection record.
Access tokens expire after 60 minutes by default, refresh token families last up to 30 days, and interrupted MCP sessions retain a 15-minute grace window for reconnects. Durable connections preserve remembered workspace grants and connection-level policies, while session-only leases expire on disconnect.
Aevra does not automatically replay a lost mutating request after reconnection. Call operation_get or operation_list to inspect the status of a previous operation before issuing another write, commit, delete, or command.
desktop_describe(mode: 'background') with action tools (desktop_invoke, desktop_set_value, desktop_select, desktop_toggle). These operate as a background auto-clicker using native UI Automation control patterns without moving the mouse cursor, typing into the active window, or stealing keyboard focus. You can continue using the computer while the agent works in the background, and tasks continue even when physical displays turn off.desktop_click, desktop_type, desktop_key, desktop_capture). Foreground actions require identifiable windows and prompt for user approval before clicks and keystrokes.DESKTOP_FOCUS_CHANGED. The agent should call desktop_describe to inspect the new layout before continuing.browser_act_many coordinate clicks (op: "click") and drags (op: "drag"). Aevra delivers calibrated browser-native mouse input (Input.dispatchMouseEvent via Chrome debugger or CDP) directly to canvas targets rather than synthetic DOM events.browser_snapshot rather than taking full-page screenshots. DOM accessibility snapshots cost fewer tokens and give reliable element references for browser_act_many.--remote-debugging-port.chrome:// settings pages, and local file:// URIs to prevent prompt injection attacks against the host.AEVRA_USERNAME and AEVRA_PASSWORD in your user environment or shell profile, then restart aevra.publicUrl) for AI clients. Keep the Admin UI local unless you configure an explicit HTTPS adminPublicUrl with trusted Admin origins.Read-Only or Safe Dev for AI web clients, reserving Full Access for trusted local sessions.search with explicit include and exclude glob patterns. Target specific subdirectories in large repositories to keep searches fast.process_start and process_wait rather than blocking terminal commands. Aevra tracks them across reconnects.aevra service install && aevra service start so the gateway starts on boot and reconnects automatically.file_write to save images, diagrams, or generated data directly into your local project folder.search, summarize the findings, and write the report to a local file.publicUrl for AI clients while keeping adminPublicUrl restricted to a private VPN or trusted origin.hooks.pre and hooks.post in aevra.config.json to run scripts before or after specific MCP tool calls, such as linting before a commit or notifying a webhook after a file write.GitHub Actions uses Node.js 24 and GitHub-maintained actions at @v6; the third-party Rust cache keeps its own supported version. .node-version selects Node 24 for local development.
Pull requests, pushes to main and manual dispatch run the quality gate. The native helper matrix checks Rust formatting and strict Clippy before release builds/tests; GNOME/KDE acceptance runs separately. Version-tag or manual releases wait for a successful push-triggered quality run on the exact release commit and reuse its artifacts. See release CI.
MIT (c) aevra Contributors
Workspace-scoped local MCP execution gateway for AI web interfaces with policy, recovery, and audit controls.
{ "mcpServers": { "the-long-ride-aevra": { "command": "npx", "args": [ "-y", "@the-long-ride/[email protected]" ] } }}ツール
ツール一覧はまだありません。リモートサーバーは、最初のヘルスチェック後に取得されます。
よくある質問
このページで Cursor、Claude Desktop、Claude Code、VS Code 用の stdio 設定をコピーできます。PlugMCP のプロキシではなく、公開元のインストール方法を使います。
このレコードに必須の環境変数は記載されていません。
@the Long Ride/aevra は stdio 経由でローカル実行されます。
最終チェックは 2026-10-28 です。 Workspace-scoped local MCP execution gateway for AI web interfaces with policy, recovery, and audit controls.