Eleven tools, one API
Full client lifecycle over the wg-easy v15 REST API — including .conf files, QR codes and one-time download links — with partial updates that merge into the current client state instead of overwriting it.
An MCP server for wg-easy v15: list, create and revoke VPN clients, pull configs and QR codes, and read server status — from Claude, Codex or any MCP client.

A client that cannot spawn a local process — ChatGPT connectors, Claude on the web, Cursor, LibreChat — cannot start wg-easy-mcp the way Claude Code does. mcp-hub is the bridge: one container serves many stdio MCP servers over Streamable HTTP, with an OAuth 2.1 login behind a single password and long-lived tokens for the clients that cannot do OAuth. Its /hub endpoint puts every server behind six meta-tools, so one connector reaches all of them without N×tool schemas in the model's context, and it speaks both protocol revisions — a question this server asks travels through it to the person at the far end instead of ending at the gateway.
Its configuration is Claude Code's mcpServers format, so the entry you already have is the entry it takes: Through mcp-hub.