How do I install Vpn Bypass?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Vpn Bypass need an API key?

The publisher lists these environment variables: VPNB_SOCKET, VPN_BYPASS_MCP_READ_ONLY.

What transport does Vpn Bypass use?

Vpn Bypass runs locally over stdio.

Vpn Bypass

Q: When was Vpn Bypass last checked?

Last checked 2026-10-16. Read and change VPN Bypass (macOS) routing: domain lists, services, modes, kernel routes, logs

by io.github.GeiserX

Read and change VPN Bypass (macOS) routing: domain lists, services, modes, kernel routes, logs

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Local command

npx -y [email protected]

Credentials from the publisher

VPNB_SOCKET — Path of the VPN Bypass control socket (default ~/Library/Application Support/VPNBypass/control.sock)
VPN_BYPASS_MCP_READ_ONLY — Set to 1 to register only the tools that change nothing

Provider

Claude Code

VPNB_SOCKET=<value> VPN_BYPASS_MCP_READ_ONLY=<value> claude mcp add io.github.geiserx-vpn-bypass-mcp -- npx -y [email protected]

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "io.github.geiserx-vpn-bypass-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "VPNB_SOCKET": "<value>",
        "VPN_BYPASS_MCP_READ_ONLY": "<value>"
      }
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

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.

Launch

Related MCP

Related skills

View all

23 tools, one per app action: status, domain lists, services, routing mode, kernel routes, DNS refresh, the log, and Custom-mode routes and rules.
Every tool returns the app's own JSON unchanged, so fields a newer app adds reach the agent.
Tool descriptions tell an agent that has never seen the app what each mode does, and keep kernel routes apart from Custom-mode egress routes.
MCP hints on every tool (readOnlyHint, destructiveHint, idempotentHint), so a client can ask before a destructive call.
VPN_BYPASS_MCP_READ_ONLY=1 registers only the 8 tools that change nothing.
Errors an agent can act on: the app is not running, the app is older than 4.9.0 (with its version when it reports one), or the app's own error code.
A proxy password travels in a separate field and is never returned, echoed or logged.
stdio only; the server opens no network port.

Quick start

npx -y vpn-bypass-mcp --version

Then add the server to your MCP client (Claude Desktop, Cursor, or any client that reads mcpServers):

{
  "mcpServers": {
    "vpn-bypass": {
      "command": "npx",
      "args": ["-y", "vpn-bypass-mcp"]
    }
  }
}

VPN Bypass must be open. The domain, service, active-route, refresh and log tools need VPN Bypass 4.9.0 or newer; status, set_mode and the Custom-mode tools work with older versions. Claude Code, the release binaries and building from source are in Getting started.

Documentation

The full documentation is at geiserx.github.io/vpn-bypass-mcp.

Getting started: requirements, npm, release binary, source, first run
Configuration: environment variables, read-only mode, timeouts, security
Usage: modes, the two kinds of route, every tool, errors
Development: build, test, release
Related projects: the VPN Bypass app, its vpnb command line, and where this server is listed

Related projects

VPN Bypass, the app, and its Homebrew tap.

License

MIT