Ai Vpn Mcp

Created By
Alexjef9 months ago
Allow your agent to access multiple geolocation, API and catalogs by changing its IP.
Overview

What is Ai Vpn Mcp?

Ai Vpn Mcp is an AI-powered VPN orchestration layer that allows agents to access multiple geolocations, APIs, and catalogs by changing their IP addresses seamlessly.

How to use Ai Vpn Mcp?

To use Ai Vpn Mcp, install the software on your system, configure the mcp.json file with your directory path, and launch the AI agent CLI to discover the MCP automatically.

Key features of Ai Vpn Mcp?

  • On-demand provisioning of VPN tunnels
  • Control over tunnel lifecycle (start/stop/status)
  • Traffic routing through global endpoints
  • Real-time connection health monitoring

Use cases of Ai Vpn Mcp?

  1. Accessing region-restricted content
  2. Scraping data from websites with geolocation restrictions
  3. Enhancing privacy and security for AI agents

FAQ from Ai Vpn Mcp?

  • Is Ai Vpn Mcp easy to install?

Yes! Installation is straightforward with provided packages for various operating systems.

  • Can I use Ai Vpn Mcp for multiple users?

Yes! It can be configured to support multiple agents accessing different geolocations.

  • What are the prerequisites for installation?

You need Python 3.9+, UV package manager, and WireGuard installed on your system.

Server Config

{
  "mcpServers": {
    "AI VPN": {
      "command": "uv",
      "args": [
        "--directory",
        "/opt/ai-vpn-mcp",
        "run",
        "--with",
        "fastmcp",
        "fastmcp",
        "run",
        "server.py"
      ],
      "env": {},
      "transport": "stdio"
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
Alexjef
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago