Mistgate MCP server
Commit 16 Nov 2026Memungkinkan AI agent untuk mengelola fleet VPN self-hosted, menguji network path, dan merencanakan perubahan konfigurasi.
Juga dikenal sebagai Mistgate/mistgate
- Stars
- 306
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- —
- Commit terakhir
- 16 Nov 2026
- Lisensi
- AGPL-3.0
Apa itu Mistgate MCP?
Memungkinkan AI agent untuk mengelola fleet VPN self-hosted, menguji network path, dan merencanakan perubahan konfigurasi.
Ringkasan dibuat dari README proyek
Tentang Mistgate MCP server
Mengelola fleet VPN pribadi menjadi otomatis saat Anda menggunakan Mistgate untuk mengawasi node self-hosted. Tool ini memungkinkan administrator untuk men-deploy dan memonitor server yang menjalankan protokol Hysteria2, VLESS, dan AmneziaWG melalui panel terpusat. Alat ini dirancang untuk individu yang menjalankan sejumlah kecil server untuk teman atau keluarga, dengan menyediakan satu link langganan per orang yang otomatis diperbarui di berbagai aplikasi client yang kompatibel seperti Mihomo atau AmneziaVPN.
Developer dapat menghubungkan AI agent via MCP untuk memeriksa seluruh fleet, menguji network path antar node, dan menyiapkan perubahan konfigurasi. Meskipun agent dapat merencanakan update yang kompleks, modifikasi berisiko tetap memerlukan persetujuan manual di dalam interface admin. Sistem ini sangat ringan, dapat berjalan pada single vCPU dengan penggunaan memori minimal, serta tidak memerlukan Docker atau server database terpisah. Sistem ini menggunakan SQLite dan systemd untuk menjaga stabilitas, memastikan tunnel VPN tetap berfungsi meskipun panel utama sedang offline.
Apa yang bisa Anda lakukan dengannya
- 1Audit kesehatan fleet VPNMinta AI agent untuk memeriksa status dan konektivitas dari semua node VPN yang aktif.
- 2Merencanakan update konfigurasi jaringanGunakan AI assistant untuk membuat draf perubahan pada pengaturan node atau konfigurasi protokol Anda.
- 3Verifikasi jangkauan jaringanGunakan agent untuk menentukan apakah server tertentu dapat diakses dari berbagai lingkungan jaringan yang berbeda.
- 4Otomatisasi deployment nodeTambahkan server VPN baru ke panel manajemen menggunakan kredensial SSH.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Belum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkaumistgate/mistgate is public and reachablegithub.com/mistgate/mistgate ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-11-12github.com/mistgate/mistgate ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di GitHubWhat it does
You put the panel on one server and add your VPN servers to it as nodes. Each person gets one subscription link, and their app picks up every server they may use. The panel keeps the nodes configured and checks them.
- Add a node from the browser by its IP with the panel's own SSH key (added once at your hoster) or the root password. The panel pins the SSH host key, checks the server, opens the ports in an active UFW or firewalld and installs the signed agent; the node's card changes the password and manages the server's SSH keys. A one-time install command works too. Add a node
- One link per person. Mihomo apps (kl!ck, FlClash, Clash Verge Rev) get all three protocols from it, Happ gets Hysteria2 and VLESS, and AmneziaVPN takes a key per device from the person's page. The Mihomo and sing-box apps move to a working server by themselves. Client apps
- Every 5 minutes the panel connects to every server the way an app does. A doctor on each node runs 21 host checks and offers eight fixes that run only after you confirm. Alerts go to the admin and to Telegram. Health
- When some networks cannot reach a server, people get to it through another of your nodes, which only forwards the encrypted traffic. The panel checks the path before switching it on and watches it afterwards; Ways in on the node page is a graph of how people reach the server, and the Nodes page maps the whole fleet. Relays
- Optional checks of whether your servers open from inside a country, network by network: Globalping probes on home and mobile networks over IPv4 and IPv6, volunteer and SIM probes, block lists and a TSPU probe from your own node. Most sources work only in Russia. Reachability
- No Docker, no database server. The panel idles at 16-20 MiB of memory on a 1 vCPU / 1 GB server. Benchmarks, including where Mistgate is slower.
- Strangers who open the panel's address see a decoy site; the admin is behind a secret path or host name.
- A built-in assistant (a cloud model you connect with your own key) answers about your nodes and people and prepares changes you apply. MCP lets an outside AI agent read the fleet, test paths between your nodes and plan changes; risky ones wait for your approval in the admin. An API token can disable or rewrite at most 10 people an hour unless you lift the limit for it. Assistant, MCP
Not there yet: an app of our own (planned), a Telegram bot beyond alerts, and the Cloudflare Workers edition is still a preview. Some defaults lean towards users in Russia; all of them are settings.
Protocols
| Protocol | On the node | What you can set |
|---|---|---|
| Hysteria2 | The official Hysteria2 core | UDP (QUIC). Salamander obfuscation (Gecko is experimental), port hopping, a Let's Encrypt or a pinned self-signed certificate. |
| VLESS | xray-core | REALITY over XHTTP or TCP (RAW + Vision); TLS over XHTTP or WebSocket, direct or behind a CDN. |
| AmneziaWG | amneziawg-go in userspace, or the kernel module | Versions 3.1 (the default) and 2.0, a separate key per device. 1.5 and 1.0 are not offered. |
| MTProto | Mistgate's own MTProto core | Experimental. A proxy for the Telegram app only: Fake TLS with the node's own domain or another site as the name, a key per person, the decoy site for everyone else. |
Hysteria2 and VLESS can share a node, TCP 443 included. Not every app format carries every profile: see what works where.
Not supported yet: VMess, Trojan, Shadowsocks, TUIC and plain WireGuard. More protocols are planned; each new one plugs into the same subscription link through the contract below.
A protocol is two halves compiled into the binaries. On the panel, one Go interface: a JSON Schema for its settings (the admin builds the form from it), validation, the spec a node runs, credential issuing, and its piece of each subscription format. On the node, an engine that runs the spec, swaps credentials without a restart and reports traffic and health. A new protocol goes only to agents that announce it, so older agents keep working. See the protocol plugin contract.
Is it stable?
It is beta, and young: v0.1.0 was tagged on 2026-10-03, and v0.1.81 is the 82nd tag. Until 1.0 the API, the stored settings and the node protocol may still change. Releases do not go through an automated upgrade test from older versions yet; that is one of the conditions for 1.0.
I run it on my own six servers for family and friends.
The tunnels do not depend on the panel: a node keeps serving its last applied configuration while the panel is down, a user change does not restart the server, and older agents work with a newer panel. In the benchmark, adding and removing users and restarting the panel dropped no connection.
Checks:
- CI on every push and pull request (ci.yml): Go tests and vet, the race detector on the panel-agent session,
govulncheck, the admin's lint and tests, the docs build, the installer on Debian and Ubuntu. - An end-to-end run (scripts/e2e-wsl.sh): a real panel and node with real Hysteria2, AmneziaWG, Xray, mihomo and sing-box clients, plus agent updates, rollbacks and an install over SSH. It runs by hand before every release, in WSL or a VM, not in CI.
- GitHub Actions builds each tag as a draft. I rebuild it from the tag on a machine with the offline release key and sign only binaries that match byte for byte; nodes and the panel install only signed builds. Releases and signing
Updating (Updates):
- Nodes never update on their own. A rollout updates one canary node first and gives it 5 minutes to pass a health gate, then goes on in batches of one or two. A node that fails gets its previous build back, and the rollout pauses.
- The agent also rolls itself back if a new build does not connect within 5 minutes or keeps crashing. Any node can be rolled back by hand.
- A node whose link to the panel stalls can finish the download from GitHub. The panel offers it as a second source only when the release there is signed by the panel's own key and has the same files; it is on by default, a switch in Settings turns it off, and GitHub sees the node's address.
- The panel updates itself only when you confirm. It backs up its data first and restores the old binary and data if the new one does not stay up for 45 seconds.
- Keep encrypted backups of
/var/lib/mistgateanyway.
Mistgate is written with AI coding agents. I review what they write and decide what is merged and released; the checks above are the same for their code as for anyone's. Commits made with an agent carry a Co-Authored-By line, and the rules agents follow in this repository are in AGENTS.md.
Screenshots
The screenshots use invented demo data.
Quick start
You need a fresh Linux server (amd64 or arm64) with systemd, a domain that points directly at it (here panel.example.com), TCP ports 80 and 443 free, and either openssh-client with ssh-keygen -Y verify support or OpenSSL 3.2 or newer. On the server, run:
curl -fsSL https://mistgate.app/install.sh | sudo bash -s -- --public-url https://panel.example.com
The installer verifies the signed panel manifest, starts Mistgate under systemd and prints the admin URL with a one-time setup link (valid for 30 minutes). It leaves the firewall alone. --yes skips the questions, --dry-run only verifies the release; manual installation and other options are in Install the panel.
Then:
- Open the setup link and create the owner: a passkey, or a password with an authenticator code.
- Add servers in Nodes → Add node, over SSH or with a one-time command (Add a node).
- Add people: First users.
An AI agent that can run ssh can do these steps with the prompt in the AI agent guide; you still create the owner account yourself.
Compared with other panels
| Mistgate | 3x-ui | Remnawave | Hiddify | PasarGuard | s-ui | |
|---|---|---|---|---|---|---|
| Runs without Docker | ✅ | ✅ | ❌ | ✅ | 🟡 partial | ✅ |
| Database | SQLite | SQLite or PostgreSQL | PostgreSQL + Redis | MySQL + Redis | SQLite, MySQL, MariaDB or PostgreSQL | SQLite |
| Panel RAM, idle | 16-20 MiB¹ | 68-74 MiB¹ | 426-454 MiB¹ | not measured | 262-265 MiB¹ | not measured |
| Add a node from the panel (SSH) | ✅ | ❌ | ❌ | ❌ | ❌ | ? |
| Hysteria2 | ✅ | ✅ | 🟡 partial | ✅ | ✅ | ✅ |
| VLESS REALITY | ✅ | ✅ | ✅ | ✅ | ✅ | ? |
| AmneziaWG | ✅ 2.0 and 3.1 | ✅ 3.1 | ? | ? | ? | ? |
| VMess, Trojan, Shadowsocks | ❌ | ✅ | 🟡 partial | ✅ | ✅ | ✅ |
| Xray JSON or sing-box subscriptions | ✅ both | Xray JSON | ✅ both | ✅ both | sing-box | sing-box |
| Health checks and alerts | ✅ client-eye checks, node doctor, reachability from a country | ✅ tunnel monitor (opt-in) | ✅ status, Prometheus | 🟡 partial | 🟡 partial | ? |
| Telegram bot | 🟡 alerts only | ✅ | 🟡 partial | ✅ | ✅ | ? |
| Built-in MCP server for AI agents | ✅ | ? | ❌ | ? | ? | ? |
¹ Private memory of the whole panel group, idle, 0 to 200 users, no node attached, on a 1 vCPU / 1 GB test server (3x-ui includes its Xray core and fail2ban). Method, versions and limits: Benchmarks. "?" means the project's own README and docs do not say.
Others are ahead in protocol breadth, community size and full Telegram bots. The full table with sources, checked on 2026-10-09, is in Comparison with other panels.
Documentation
Everything is at mistgate.app and in docs/. Good places to start:
- Overview and Requirements
- Install the panel, Install a node over SSH, First users
- Health, Updates, Encrypted backups, Troubleshooting
- CLI, API, MCP, Architecture
Contributing
Bug reports, fixes and documentation are welcome. CONTRIBUTING.md has the build, the code map, the checks CI runs and the conventions. Coding agents start with AGENTS.md; the AI agent guide has a ready prompt for contributing.
Security
Report vulnerabilities privately: see SECURITY.md. Back up the panel's data directory (/var/lib/mistgate): it holds the database, the master key and the CA your nodes trust.
Licence
Mistgate is free software under the GNU Affero General Public License v3.0 only. If you run a modified panel for others, its admin shows a "Source code" link (serve --source-url) that should point to your source.
Star History
Pertanyaan tentang Mistgate MCP
Apa yang bisa dilakukan AI agent dengan Mistgate melalui MCP?
AI agent eksternal dapat membaca data fleet VPN, menguji path antar node, dan merencanakan perubahan konfigurasi.
Bagaimana cara menambahkan node VPN ke panel?
Anda dapat menambahkan node melalui browser menggunakan alamat IP-nya via SSH key atau password root pada panel.