Arc Control (macOS) MCP Server

What this does

Arc Control (macOS) exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server declares the following environment variables. Set only the ones the maker requires for your setup; this listing does not flag any of them as required:

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

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install Arc Control (macOS)?

Run the Claude Code command in the install section to add Arc Control (macOS) to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Arc Control (macOS)?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Arc Control (macOS) as well.

Does Arc Control (macOS) need an API key?

This listing does not flag an API key as required. The server can use these 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; the maker's docs say which of them your setup needs. They go in the env block of your MCP config.