AgentHubAgentHub

Arc Control (macOS) MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.DB-25/arc-control-mcp · v0.4.0

Arc browser MCP for macOS: agent window, snapshots, DevTools input, guardrails

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

Arc browser MCP for macOS: agent window, snapshots, DevTools input, guardrails Arc Control (macOS) is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-25
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from official-mcp-registry
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.

Copy by platform

Choose your platform

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window

Pre-fill Environment Variables (Optional)

Privacy Guarantee: Keys are replaced 100% locally in your browser memory and are NEVER uploaded or stored on any server.
Click to copy snippet
{
  "mcpServers": {
    "arc-control-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "arc-control-mcp"
      ]
    }
  }
}

Setup tutorial

  1. Open the Arc Control (macOS) page and confirm this MCP Server (source: MCP Registry).
  2. Copy the Cursor, Claude Code, or VS Code snippet.
  3. Merge it into mcpServers and replace env placeholders with real secrets.
  4. Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (local)

  1. Install Claude Code CLI
  2. Copy the command below, replace <placeholders> with real env values, then run in terminal
  3. See Environment variables below if listed
claude mcp add arc-control-mcp -- npx -y arc-control-mcp

Cursor — .cursor/mcp.json (local)

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window
{
  "mcpServers": {
    "arc-control-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "arc-control-mcp"
      ]
    }
  }
}

VS Code — .vscode/mcp.json (local)

  1. Install GitHub Copilot in VS Code with MCP support
  2. Open or create .vscode/mcp.json in your project root
  3. Click Copy config and paste; merge only this mcpServers entry if others exist
  4. Replace <placeholders> in env with real secrets
  5. Save and Developer: Reload Window
{
  "mcpServers": {
    "arc-control-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "arc-control-mcp"
      ]
    }
  }
}

Claude Desktop — claude_desktop_config.json (local)

  1. Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
  2. Click Copy config and merge under mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Fully quit and restart Claude Desktop
{
  "mcpServers": {
    "arc-control-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "arc-control-mcp"
      ]
    }
  }
}

Trae — .trae/mcp.json (local)

  1. Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Save and reload Trae
{
  "mcpServers": {
    "arc-control-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "arc-control-mcp"
      ]
    }
  }
}

Cherry Studio — MCP settings (local)

  1. Cherry Studio → Settings → MCP Servers → Add (STDIO)
  2. Or import JSON: click Copy config and merge mcpServers
  3. Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
  4. Enable the server and check tools load
{
  "mcpServers": {
    "arc-control-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "arc-control-mcp"
      ]
    }
  }
}

Tongyi Lingma — MCP config (local)

  1. Lingma Settings → MCP → + → STDIO or config file
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
  4. Confirm connected before using tools in agent chat
{
  "mcpServers": {
    "arc-control-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "arc-control-mcp"
      ]
    }
  }
}

Windsurf — mcp_config.json (local)

  1. Edit ~/.codeium/windsurf/mcp_config.json
  2. Click Copy config and merge mcpServers (stdio same as Cursor)
  3. Replace <placeholders> in env, save, refresh Cascade
{
  "mcpServers": {
    "arc-control-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "arc-control-mcp"
      ]
    }
  }
}

Cline — MCP Servers (local)

  1. Cline panel → Settings → MCP Servers
  2. Click Copy config and merge
  3. Replace <placeholders> in env, then save
{
  "mcpServers": {
    "arc-control-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "arc-control-mcp"
      ]
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (local)

  1. Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
  2. Or Plugins → MCP Servers → Configure MCP and paste the JSON below
  3. Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
  4. Save, restart WorkBuddy, confirm connector status is green
{
  "mcpServers": {
    "arc-control-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "arc-control-mcp"
      ]
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for Arc Control (macOS)

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for Arc Control (macOS)?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Missing required environment variable or authentication failure?

Arc Control (macOS) requires environment variables (ARC_MCP_LABEL、ARC_MCP_SPACE、ARC_MCP_STATE_DIR、ARC_MCP_WINDOW、ARC_MCP_WINDOW_PLACEMENT、ARC_MCP_IDLE_MS、ARC_MCP_IDLE_WAIT_MS、ARC_MCP_ARC_DATA_DIR、ARC_MCP_ALLOW_HISTORY、ARC_MCP_CDP、ARC_MCP_CDP_PORT、ARC_MCP_ALLOWED_ORIGINS、ARC_MCP_BLOCKED_ORIGINS、ARC_MCP_BLOCK_READS、ARC_MCP_READ_ONLY、ARC_MCP_AUDIT_LOG). Ensure you have added valid keys under the 'env' object in your config file without trailing whitespace.

Fix Snippet
// .cursor/mcp.json 或 claude_desktop_config.json
{
  "env": {
    "API_KEY": "your_actual_key_here"
  }
}

Tool Mock Playground

Sandbox

Arc Control (macOS) Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: arc_control_mcpExecute the core tool interface of Arc Control (macOS)
Request ArgumentsJSON Schema
{
  "target": "Arc Control (macOS)",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • PR review
  • Changelog generation
  • Cross-repo issue search
When NOT to Use
  • Replacing human security audit
  • Unauthorized repo access
Recommended Workflow Pairing:View Scenario →

Arc Control (macOS) + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

中文公文写作

v2.0.46

SkillClawHub7210.6k

io.clawhub.gongyu0918-debug/chinese-official-writing

用于中文公文、事务性材料和新闻稿件的起草、改写、压缩、润色、审校、文种核对、去口语化、降 AI 味及 Word 格式处理,适用于机关、企事业单位、学校和新闻机构。涵盖申请、请示、报告、通知、通告、意见、决定、决议、议案、公报、命令、函、复函、批复、说明、方案、纪要、公告、公示、通报、制度、规定、办法、细则、操作规程、工作要点、总结、调研、讲话、致辞、主持词、述职、可研、审查材料、技术需求、新闻消息、编者按、新闻评论,以及采购、整改、反馈和 AI 算力等场景。

source

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: Arc Control (macOS)
HTML
<a href="https://myagenthub.cn/p/io.github.DB-25/arc-control-mcp" title="Listed on AgentHub: Arc Control (macOS)" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.DB-25/arc-control-mcp?lang=en" alt="Listed on AgentHub: Arc Control (macOS)" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: Arc Control (macOS)](https://myagenthub.cn/badge/io.github.DB-25/arc-control-mcp?lang=en)](https://myagenthub.cn/p/io.github.DB-25/arc-control-mcp)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.DB-25/arc-control-mcp",
  "type": "mcp-server",
  "version": "0.4.0",
  "displayName": "Arc Control (macOS)",
  "description": "Arc browser MCP for macOS: agent window, snapshots, DevTools input, guardrails",
  "repository": {
    "url": "https://github.com/DB-25/arc-control-mcp",
    "source": "github"
  },
  "homepage": "https://github.com/DB-25/arc-control-mcp",
  "distribution": {
    "packages": [
      {
        "registryType": "npm",
        "identifier": "arc-control-mcp",
        "version": "0.4.0",
        "transport": "stdio",
        "environmentVariables": [
          {
            "name": "ARC_MCP_LABEL",
            "description": "Names this agent's tab ownership. Two agents with different labels never see each other's owned tabs. Defaults to \"default\"."
          },
          {
            "name": "ARC_MCP_SPACE",
            "description": "With ARC_MCP_WINDOW=space, the Arc space new tabs open into, when a space with that name exists. Arc will not let a script create a space, so make it by hand. Defaults to \"Agent\"."
          },
          {
            "name": "ARC_MCP_STATE_DIR",
            "description": "Directory where per-session tab ownership is recorded, so a restarted agent can clean up the tabs its previous run left behind. Defaults to ~/Library/Application Support/arc-control-mcp."
          },
          {
            "name": "ARC_MCP_WINDOW",
            "description": "\"dedicated\" keeps agent tabs in one separate agent window, never the user's own. \"space\" puts them in the Agent space of the user's window. Defaults to \"dedicated\"."
          },
          {
            "name": "ARC_MCP_WINDOW_PLACEMENT",
            "description": "Where the agent window goes once, at creation: \"auto\" (largest non-main display, else where Arc puts it), \"second-display\", \"minimized\" (experimental) or \"none\". Needs Accessibility. Defaults to \"auto\"."
          },
          {
            "name": "ARC_MCP_IDLE_MS",
            "description": "How many milliseconds the user must have been idle before the server does anything visible. 0 turns the activity gate off. Defaults to 1500."
          },
          {
            "name": "ARC_MCP_IDLE_WAIT_MS",
            "description": "How many milliseconds to wait for that pause before failing with userActive true. Defaults to 15000."
          },
          {
            "name": "ARC_MCP_ARC_DATA_DIR",
            "description": "Directory the local data tools (sidebar_tree, find_stale_tabs, search_archive, search_history) read Arc's files from. Defaults to ~/Library/Application Support/Arc."
          },
          {
            "name": "ARC_MCP_ALLOW_HISTORY",
            "description": "Set to 1 to let search_history run. Off by default, and any other value leaves it off."
          },
          {
            "name": "ARC_MCP_CDP",
            "description": "Set to 0 to disable the DevTools engine (trusted input, screenshots, console and network capture). On by default, and inert until Arc is launched with --remote-debugging-port."
          },
          {
            "name": "ARC_MCP_CDP_PORT",
            "description": "The DevTools port to probe on 127.0.0.1. The host is fixed. Defaults to 9222."
          },
          {
            "name": "ARC_MCP_ALLOWED_ORIGINS",
            "description": "Guardrail. Comma list of origins the agent may touch (host, *.host, scheme://host[:port], file://, about:). Anything not listed is refused. Unset means no allow list."
          },
          {
            "name": "ARC_MCP_BLOCKED_ORIGINS",
            "description": "Guardrail. Comma list of origins the agent may not touch. Wins over the allow list. Unset means no block list."
          },
          {
            "name": "ARC_MCP_BLOCK_READS",
            "description": "Set to 1 to apply the origin lists to read tools as well as changing ones. Off by default."
          },
          {
            "name": "ARC_MCP_READ_ONLY",
            "description": "Set to 1 to expose only the read-only tools. Off by default."
          },
          {
            "name": "ARC_MCP_AUDIT_LOG",
            "description": "Path of a file that gets one JSON line per changing call (time, tool, tab, origin, ok, error), never typed values or script code. Unset means no audit log."
          }
        ]
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.DB-25/arc-control-mcp",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.DB-25%2Farc-control-mcp/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}
Arc Control (macOS) MCP Setup & Guide - AgentHub