Back to Browse

Portveil MCP Server

Developer ToolsScan in ProgressMCP RegistryLocal
Free

Server data from the Official MCP Registry

MCP server for Portveil: let AI assistants see your devices and move them between VPN locations.

About

MCP server for Portveil: let AI assistants see your devices and move them between VPN locations.

Security Report

0.0
Use Caution0.0Moderate Risk

14 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Remote servers are capped at 8.0 because source code is not available for review. The score reflects endpoint verification only.

What You'll Need

Set these up before or after installing:

Your Portveil account ID (acct_…), shown in the dashboardOptional

Environment variable: PORTVEIL_ACCOUNT_ID

A Portveil API token from the dashboard; control scope to move devices, read to only lookRequired

Environment variable: PORTVEIL_TOKEN

API base URL (default https://api.portveil.com)Optional

Environment variable: PORTVEIL_API

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-roybogs-portveil-mcp": {
      "env": {
        "PORTVEIL_API": "your-portveil-api-here",
        "PORTVEIL_TOKEN": "your-portveil-token-here",
        "PORTVEIL_ACCOUNT_ID": "your-portveil-account-id-here"
      },
      "args": [
        "-y",
        "portveil-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Portveil MCP server

Let an AI assistant see the devices on your Portveil account and move them between VPN locations.

"Move my scraper box to Finland." "Rotate every agent to a new location." "Which of my devices aren't protected right now?" "Rotate the scraper between the US and Finland every 15 minutes."

Moves are verified: a tool only reports success after the device has switched and the exit server in the new location confirms it sees that device.

Tools

ToolWhat it doesNeeds
list_devicesEvery device: protected or not, where it exits, live speed (↓/↑ Mbps), remote control on/offread
list_locationsThe locations you can move toread
get_deviceOne device's current state, including live speed and any rotationread
get_accountPlan and devices usedread
list_activityRecent moves, reconnects and changes, and which token made themread
move_deviceMove a device to a country or city ("Finland", "US", "Helsinki")control
rotate_deviceMove a device once to the next locationcontrol
start_rotationMove a device automatically every N minutes (5–10080), optionally among chosen locations. Portveil runs the schedule, so the assistant can closecontrol
stop_rotationTurn scheduled rotation offcontrol
reconnect_deviceRe-establish a device's tunnelcontrol
disconnect_deviceTurn a device's VPN off (flagged destructive: a hint that tells well-behaved assistants to check with you first)control
add_deviceAdd a device. Phones and laptops (WireGuard app): creates it and saves its tunnel files locally, key never shown in chat. Linux servers and agent machines: gives the exact commands to run on that machine, which makes its own key and registers itselfadmin (phones/laptops)
update_deviceRename a device and/or turn its remote control on or offadmin
remove_deviceRemove a device for good (flagged destructive)admin

Tool names changed in 0.3.0 to one verb_noun pattern: device_status → get_device, account_info → get_account, recent_activity → list_activity, set_rotation → start_rotation.

Devices can be named loosely ("scraper" finds "Scraper box"); an ambiguous name returns the choices instead of guessing.

Setup

No account yet? Start free with just an email, no card.

  1. In the Portveil dashboard, create an API token. Choose control scope to let the assistant move devices, or read to let it only look. Don't give it your account key.
  2. Note your account ID (acct_…).
  3. Add the server to your assistant:

Claude Code

claude mcp add portveil -e PORTVEIL_ACCOUNT_ID=acct_… -e PORTVEIL_TOKEN=clt_… -- npx -y portveil-mcp

Claude Desktop (claude_desktop_config.json), Cursor (.cursor/mcp.json) and most other clients:

{
  "mcpServers": {
    "portveil": {
      "command": "npx",
      "args": ["-y", "portveil-mcp"],
      "env": { "PORTVEIL_ACCOUNT_ID": "acct_…", "PORTVEIL_TOKEN": "clt_…" }
    }
  }
}

Hermes Agent: Hermes only installs npm packages older than 14 days, so install into its own folder and run it with node:

cd ~ && npm install --prefix ~/.hermes/mcp-servers/portveil portveil-mcp@0.4.3
echo 'PORTVEIL_TOKEN=clt_…' >> ~/.hermes/.env
hermes mcp add portveil --command node \
  --env PORTVEIL_ACCOUNT_ID=acct_… 'PORTVEIL_TOKEN=${PORTVEIL_TOKEN}' \
  --args ~/.hermes/mcp-servers/portveil/node_modules/portveil-mcp/dist/index.js

For Hermes to use it well (when to act, what to confirm first, how to add devices), also install the Portveil skill from ClawHub:

hermes skills install roybogs/portveil

(Source: skills/portveil/SKILL.md.)

Devices must be running the Portveil app or the Portveil agent with remote control on. Devices using the plain WireGuard app are shown but can't be moved.

Security

  • Use a scoped API token. Every action it takes is recorded in your account's activity log with the token that made it, and you can revoke it in the dashboard at any time.
  • The server talks only to https://api.portveil.com (override with PORTVEIL_API). It stores nothing.

Development

npm install
npm test        # builds, then runs the tests against a fake Portveil API

Reviews

No reviews yet

Be the first to review this server!