English Français العربية

VPN Bypass

Registre officiel Autres

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

Code source Site web Documentation

Que pouvez-vous faire avec VPN Bypass ?

  • 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.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package vpn-bypass-mcp
Claude Code 
claude mcp add vpn-bypass -e 'VPNB_SOCKET=<VPNB_SOCKET>' -e 'VPN_BYPASS_MCP_READ_ONLY=<VPN_BYPASS_MCP_READ_ONLY>' -- npx -y vpn-bypass-mcp@0.2.0
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "vpn-bypass": {
            "command": "npx",
            "args": [
                "-y",
                "vpn-bypass-mcp@0.2.0"
            ],
            "env": {
                "VPNB_SOCKET": "<VPNB_SOCKET>",
                "VPN_BYPASS_MCP_READ_ONLY": "<VPN_BYPASS_MCP_READ_ONLY>"
            }
        }
    }
}

Variables d'environnement

  • 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 8 read tools and the diagnose_site prompt; any value except empty, 0, false or no turns it on

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. vpn-bypass-mcp
  2. Features
  3. Quick start
  4. Documentation
  5. Related projects
  6. License

vpn-bypass-mcp

vpn-bypass-mcp is an MCP server for VPN Bypass, the macOS menu bar app that decides which traffic uses the VPN and which goes around it. An AI agent uses it to read the app's state and change its routing through the app's local control socket. It runs on macOS only.

Features

  • 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

VPN Bypass, the app, and its Homebrew tap.

License

MIT

Questions fréquentes

Qu'est-ce que VPN Bypass ?

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

Comment installer VPN Bypass ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add vpn-bypass -e 'VPNB_SOCKET=<VPNB_SOCKET>' -e 'VPN_BYPASS_MCP_READ_ONLY=<VPN_BYPASS_MCP_READ_ONLY>' -- npx -y vpn-bypass-mcp@0.2.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour VPN Bypass ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

VPN Bypass est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient VPN Bypass ?

Il est publié par GeiserX. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.