Overview

The PrivadoVPN MCP server allows you to connect PrivadoVPN directly to your AI developer tools using the Model Context Protocol (MCP). This local integration enables your AI assistant to programmatically interact with your VPN connection via natural language or API calls - managing connections, switching servers, changing protocols, and performing diagnostics without needing to manually use the PrivadoVPN app.

The MCP server is implemented as a local HTTP API embedded within the PrivadoVPN client and is designed for advanced users, developers, and automation workflows.

 

Prerequisites

Before enabling to the PrivadoVPN MCP server:

• An MCP-compatible AI client that supports HTTP-based MCP servers

• An active PrivadoVPN installation (Windows \ macOS)

Enable MCP in PrivadoVPN:

1. Open the PrivadoVPN application

2. Navigate to Settings → Application

3. Enable the MCP Server option (note the port assigned - default is 5801)

4. Click Save

Once done, the MCP server runs locally in the background.

 

Connect your AI tool

The default MCP server endpoint is:

http://127.0.0.1:5801/mcp

If your application shows a different port, replace 5801 accordingly.

---

Claude Code

Run the following command:

claude mcp add --transport http privado-vpn http://127.0.0.1:5801/mcp

---

Codex

Add to your MCP configuration:

{
  "mcpServers": {
    "privado-vpn": {
      "url": "http://127.0.0.1:5801/mcp"
    }
  }
}

---

Cursor

Open Settings → Tools & MCP → Add custom MCP:

{
  "mcpServers": {
    "privado-vpn": {
      "url": "http://127.0.0.1:5801/mcp",
      "headers": {}
    }
  }
}

---

LM Studio

Go to Integrations → Edit mcp.json:

{
  "mcpServers": {
    "privado-vpn": {
      "url": "http://127.0.0.1:5801"
    }
  }
}

---

VS Code

Add to .vscode/mcp.json or global config:

{
  "servers": {
    "privado-vpn": {
      "type": "http",
      "url": "http://127.0.0.1:5801"
    }
  }
}

Available tools

After enabling MCP, your AI assistant can directly control and inspect your VPN state.

These tools expose core PrivadoVPN functionality through a simple HTTP interface.

---

TOOL	DESCRIPTION
Connectivity & Diagnostics
echo	Verifies MCP server availability. Returns the same message sent.
ping	Performs a network connectivity test to a specified host or IP.
VPN Connection
vpn_connect	Connects to PrivadoVPN. Without parameters, uses the current or optimal location.
vpn_disconnect	Disconnects from PrivadoVPN and drops the VPN tunnel.
Status & Monitoring
vpn_get_status	Returns a full real-time status report including connection state, IP address, geolocation, username, app version, and feature states (Kill Switch, Control Tower, Split Tunneling\Smart Route).
Server Management
vpn_get_status	Returns a real-time VPN status, including connection state, IP, location, and feature states.
Protocol Management
vpn_set_protocol	Sets or retrieves VPN protocols. Changes apply immediately or on next connection. Supported protocols: Automatic IKEv2 Wireguard OpenVPN
Security
vpn_toggle_kill_switch	Enables or disables Kill Switch, blocking internet traffic if the VPN disconnects.

---

How it works

The MCP server operates as a local control layer between external tools and the PrivadoVPN client.

• Runs locally on the user’s machine

• Listens for HTTP requests (default port 5801)

• Accepts commands from AI tools or scripts

• Communicates with the VPN client core

• Returns structured responses

Interaction flow: Client communicates with the MCP Server, which interfaces with the VPN Core and returns a response.

Workflow: Client → MCP Server → VPN Core → Response.

Use cases

The PrivadoVPN MCP server enables automation and AI-driven workflows directly inside development environments.

With MCP, you can:

• Connect or disconnect VPN programmatically

• Switch between server locations for geo-testing

• Retrieve real-time VPN state and metadata

• Automate protocol switching for performance validation

• Run connectivity diagnostics (ping tests)

• Enforce security policies such as Kill Switch

• Integrate VPN logic into AI agents and scripts

Example scenarios:

• Automatically connect to a specific region before running tests

• Validate geo-restricted content across multiple locations

• Verify VPN status before executing network operations

• Dynamically change protocols based on network conditions

• Perform automated troubleshooting using ping diagnostics

Technical benefits

• Local-only access: MCP server is bound to 127.0.0.1

• Standard HTTP API: Easy integration with any language or tool

• Real-time synchronization: Changes reflect instantly in the GUI

• Granular control: Direct access to connection, protocol, and security features

Product integration

All changes made via MCP are synchronized with the PrivadoVPN application interface.

The MCP server also exposes the state of advanced features such as:

• Kill Switch

• Control Tower

• Split Tunneling \ Smart Route

This ensures consistency between automated workflows and manual user actions.

Security

The PrivadoVPN MCP server is designed with strong local security guarantees:

• Localhost only: Not accessible from external networks

• No remote control exposure: Prevents unauthorized access

• Client-bound execution: All commands are executed through the official VPN client

• User-controlled activation: MCP must be explicitly enabled

This architecture ensures that all VPN control operations remain private and confined to the user’s device.