Skip to main content
Glama
zebbern

Zebbern Kali MCP

by zebbern
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

vpn_connect

Connect to a WireGuard or OpenVPN VPN by providing a config file path. Automatically detects VPN type and returns the assigned IP address.

Instructions

Connect to a VPN (WireGuard or OpenVPN) with a single call.

Places the config, brings the tunnel up, and returns the assigned IP address. Auto-detects VPN type from the config file contents unless explicitly specified.

Args: config_path: Absolute path to the VPN config file inside the container (e.g. /vpn/wg0.conf or /vpn/client.ovpn). Mount your config directory as a Docker volume to /vpn. vpn_type: 'wireguard', 'openvpn', or 'auto' (default). Auto reads [Interface]/[Peer] for WireGuard, or client/remote directives for OpenVPN. interface: WireGuard interface name (default wg0). Ignored for OpenVPN connections.

Returns: Connection result including success flag, assigned IP, interface name, and VPN type.

Example: vpn_connect(config_path='/vpn/wg0.conf') vpn_connect(config_path='/vpn/client.ovpn', vpn_type='openvpn')

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vpn_typeNoauto
interfaceNowg0
config_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It discloses actions (places config, brings tunnel up, returns IP) and auto-detection behavior, but does not mention side effects or prerequisites.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections for Args, Returns, and Example. No wasted words; concise yet comprehensive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and the description mentions return values (success, IP, interface, type), and all parameters are documented, the description is complete for a connection tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description compensates fully. Each parameter is explained with usage, default values, and type detection logic, adding significant meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool connects to a VPN (WireGuard or OpenVPN) with a single call, specifying the verb (connect) and resource (VPN). It distinguishes from siblings vpn_disconnect and vpn_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains the process and result of the tool, but does not explicitly state when to use this vs alternatives. However, the context from sibling tools makes usage clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zebbern/zebbern-kali-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server