Provision static IP tunnel for agent
An automated agent obtains a static IP address and a working WireGuard configuration file, enabling persistent outbound or inbound connectivity for infrastructure tasks without manual intervention.
How it works
The agent first calls list_plans to identify available options. It then executes order_lease with the 'trial' plan to acquire an access token. After retrieving the token, it calls lease_status to verify the lease. Finally, it calls create_tunnel with the appropriate routing_mode (checking if the target is Linux to use 'source' or 'destinations') to generate the configuration file. The agent must ensure the access token and private key are securely passed to the user or stored, as they are not recoverable.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
List available plans, order a trial lease for organization 'TestOrg' in 'US', check the lease status, and create a tunnel with routing_mode 'destinations' for destinations ['10.0.0.0/8']. Return the final configuration.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
An assistant can buy an address and bring up a tunnel without a human in the loop.MCP — let an assistant order and provision a static IP for you | AnchoredIP