wpa MCP

MCP浏览器工具

提供方 dogkeeper886

浏览器工具 未标注 无需鉴权 社区 / 第三方 Claude DesktopClaude

通过wpa_supplicant实现WiFi控制的MCP服务器,支持扫描、连接、断开、调试和自动化WiFi网络,适用于Linux系统。

一句话选型结论

按资料字段整理

wpa MCP 属于浏览器工具类 MCP 服务器,传输方式未标注,无需鉴权,可直接接入 Claude Desktop、Claude,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类浏览器工具 传输方式未标注 鉴权无需鉴权 部署方式未标注
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 23 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

浏览器工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量23暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

WiFi控制TypeScript本地部署网络管理浏览器自动化EAP-TLS支持MAC随机化

安装与配置

未标注 无需鉴权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 23 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
自动操作网页

打开页面、点击、填表,把浏览器动作交给模型执行。

抓取结构化数据

把页面内容整理成表格或 JSON,省掉手工复制粘贴。

关键流程回归

按步骤检查页面是否正常,回归时少漏环节。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 23 个工具,覆盖面较广,能满足多种调用。
  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在浏览器工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
wpa MCP当前 23 未标注 未标注 无 2026-05-17
Playwright MCP Server 21 stdio · 本地进程 本地部署 有 2026-05-18
Fetch 9a2682de 1 SSE · 服务端推送 支持远程部署 有 2026-05-18
Browser 738d52bc 未标注 stdio · 本地进程 本地部署 有 2026-05-17
MCP 40600ece 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Skyvern MCP 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

浏览器工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方dogkeeper886上游标注的维护方 dogkeeper886
分类浏览器工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

7.7 KB
来自项目仓库与上游目录的原文,未做删改

wpa-mcp

Control Linux WiFi from Claude and other MCP clients — scan, connect, debug, and automate networks (WPA-PSK, WPA2-Enterprise, EAP-TLS, Hotspot 2.0, captive portals, MAC randomization) over the Model Context Protocol.

wpa-mcp wraps wpa_supplicant and dhclient in 23 MCP tools, so an AI agent can drive a
real WiFi adapter — join networks, authenticate against enterprise RADIUS, work through
captive portals with a real browser, and diagnose failures from the supplicant logs. It
runs in a Docker container that holds the WiFi device in its own network namespace, so
none of that touches the host's routing table.```
"Scan for networks" → wifi_scan
"Connect to CoffeeShop" → wifi_connect → DHCP → ip address
"Why did that fail?" → wifi_get_debug_logs filter=eap


- How it works
- Features
- Quick start
- Register with an MCP client
- Tools
- Configuration
- EAP-TLS certificates
- Documentation

---

## How it works

Three ideas make wpa-mcp different from "shell out to `wpa_cli`". Each is worth a picture.

### 1. The WiFi device lives in the container's network namespace

The host moves the wireless **phy** into the container with `iw phy set netns`. The
interface disappears from the host; all of its routes, DHCP leases, and IP addresses exist
only inside the container. WiFi becomes the container's sole default route, while inbound
MCP traffic still arrives over the Docker bridge — the host routing table is never touched.

### 2. Two MCP servers behind one port

A single exposed port (3000) fronts two servers. `/mcp` is wpa-mcp itself, in-process and
stateless. `/playwright-mcp` is a reverse proxy to a Microsoft Playwright
MCP subprocess whose browser shares the
container's network namespace — so it can reach captive portals on the WLAN you joined with
`wifi_connect`.

### 3. Credentials by reference, not by value

EAP-TLS certificates are uploaded once (SCP), validated, and copied into a persistent store.
Tools then reference a credential by **id** instead of passing multi-kilobyte PEM blobs in
every call — faster, and the material survives container restarts on a Docker named volume.

---

## Features

| Category | Capabilities |
|----------|-------------|
| WiFi connection | WPA-PSK, WPA2-EAP (PEAP/TTLS), EAP-TLS, Hotspot 2.0 / Passpoint, open networks, BSSID targeting |
| Network management | Scan, status, list saved, forget, reconnect |
| Privacy | Per-connection MAC randomization, pre-association MAC, real-MAC restoration after netns move |
| Diagnostics | EAP state/decision, filtered supplicant logs (eap, state, scan, error) |
| Connectivity | Ping, DNS lookup, internet check, captive-portal detection |
| Browser automation | Scripted Playwright runner + proxied Playwright MCP for step-by-step browser control inside the container's netns |
| Persistence | Credential store + saved networks on a Docker named volume, across restarts and rebuilds |

---

## Quick start

### Prerequisites

- Docker, installed and running on a Linux host
- `iw` — `sudo dnf install iw` or `sudo apt install iw`
- A PCIe or USB WiFi adapter on the host

### 1. Find the WiFi interface and its phy```bash
ip link show | grep -E "^[0-9]+: wl"     # e.g. 3: wlp6s0
cat /sys/class/net/wlp6s0/phy80211/name  # e.g. phy0

2. Release the interface from NetworkManager```bash

sudo make nm-unmanage WIFI_INTERFACE=wlp6s0


### 3. Get the image and start

Pull the published image (recommended):```bash
docker pull dogkeeper886/wpa-mcp:2.0.0
echo "WPA_MCP_IMAGE=dogkeeper886/wpa-mcp:2.0.0" >> .env
sudo make docker-start

…or build it locally:```bash
make docker-build
sudo make docker-start


`make docker-start` runs the container with Docker bridge networking, moves the WiFi phy
into its namespace, waits for health, and deletes the bridge default route so WiFi is the
sole default.

### 4. Verify```bash
curl http://localhost:3000/health        # server is up
ip link show wlp6s0                       # host: gone (moved into container)
docker exec wpa-mcp ip link show wlp6s0   # container: present

To stop, make docker-stop (the phy returns to the host). To start on every boot, install
the systemd unit with sudo make install-systemd WIFI_INTERFACE=wlp6s0.


Register with an MCP client

The container exposes two MCP endpoints on port 3000:

Endpoint What it is
/mcp wpa-mcp — WiFi, credentials, connectivity, scripted Playwright
/playwright-mcp Proxied Playwright MCP — step-by-step browser control inside the container's netns

Project-scoped (this repo ships a .mcp.json pointing at localhost:3000,
so Claude Code auto-discovers both servers when opened here).

Claude Code (from the host or any machine that can reach port 3000):```bash
claude mcp add wpa-mcp --transport http http://<HOST_IP>:3000/mcp
claude mcp add wpa-playwright --transport http http://<HOST_IP>:3000/playwright-mcp


**Claude Desktop** — add to `claude_desktop_config.json`:```json
{
  &quot;mcpServers&quot;: {
    &quot;wpa-mcp&quot;: { &quot;url&quot;: &quot;http://&lt;HOST_IP&gt;:3000/mcp&quot; },
    &quot;wpa-playwright&quot;: { &quot;url&quot;: &quot;http://&lt;HOST_IP&gt;:3000/playwright-mcp&quot; }
  }
}

Tools

23 MCP tools across five areas. Full reference: docs/reference/01_WiFi_Tools.md.

WiFi management — wifi_scan, wifi_connect, wifi_connect_eap, wifi_connect_tls,
wifi_hs20_connect, wifi_disconnect, wifi_status, wifi_list_networks, wifi_forget,
wifi_reconnect

Diagnostics — wifi_eap_diagnostics, wifi_get_debug_logs

Browser automation — browser_open, browser_run_script, browser_list_scripts

Credentials — credential_store, credential_list, credential_get, credential_delete

Connectivity — network_ping, network_check_internet, network_check_captive,
network_dns_lookup


Configuration

Copy .env.example to .env. Key settings:

Variable Default Description
PORT 3000 HTTP server port
HOST 0.0.0.0 Bind address
WIFI_INTERFACE wlan0 WiFi interface name
WPA_CONFIG_PATH /etc/wpa_supplicant/wpa_supplicant.conf wpa_supplicant config
WPA_DEBUG_LEVEL 2 Debug verbosity (1–3)
WPA_MCP_BROWSER_LANG (unset) BCP-47 locale for the in-container browser, e.g. pt-PT
WPA_MCP_BROWSER_TZ (unset) IANA timezone for the in-container browser, e.g. Europe/Lisbon

The browser locale/timezone variables are read at container start and apply to
mcp__wpa-playwright__* and browser_run_script. See
docs/design/14_Browser_Locale_Timezone_Design.md.


EAP-TLS certificates

To use EAP-TLS or Hotspot 2.0, place certificate files in certs/ before building the
image — they are baked in and auto-imported on each container start:certs/ ├── &lt;identity&gt;_crt.pem # client certificate (required) ├── &lt;identity&gt;_prv.pem # private key (required) └── ca*.pem # CA certificate (optional)

Then make docker-build, sudo make docker-start, and connect with wifi_connect_tls or
wifi_hs20_connect. Credentials can also be added at runtime via the credential_store
tool. Full workflow: docs/design/11_Credential_Store_Design.md.


Documentation

Document Description
docs/README.md Documentation index, user flow, feature table
docs/reference/00_Architecture.md Component architecture
docs/reference/05_Docker_Netns_Isolation.md Netns architecture + route trace
docs/reference/01_WiFi_Tools.md WiFi tools + debug log filters
docs/reference/03_Browser_Tools.md Scripted runner + proxied Playwright MCP
docs/design/13_Dual_MCP_Playwright_Design.md Dual-MCP proxy design
docs/operations/20_Troubleshooting.md Docker + DNS troubleshooting
CHANGELOG.md Release history

License

MIT

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
wpa MCP 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

wpa MCP 怎么在 Claude Desktop、Claude 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

wpa MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

wpa MCP 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

wpa MCP 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

wpa MCP 能提供哪些能力?

资料显示约 23 个工具;能力标签包括 浏览器自动化、TypeScript、Claude、网络管理。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。