AI desktop integration

Codex / Claude + WiFi Lens

Connect a compatible desktop AI client to live Wi-Fi scan data through the local MCP server. Review the client and model provider settings to understand how they process returned data.

Local MCPHistory and analysisCheck client data settings

Open WiFi Lens and enable MCP

Start a scan, open Settings, turn on the MCP server, and confirm its port. The server stays on 127.0.0.1.

Send one setup prompt

Copy the prompt below into Codex Desktop or Claude Desktop. It asks the client to add only this local MCP entry and verify the tools.

Universal MCP setup prompt for Codex Desktop and Claude Desktop

Two desktops, one target state

The same prompt describes the goal. Each client uses its own configuration format.

Manual fallback · TOML

Codex Desktop

Codex supports Streamable HTTP servers in ~/.codex/config.toml.

~/.codex/config.toml
[mcp_servers.wifi-lens]
url = "http://127.0.0.1:19840/"
Manual fallback · JSON

Claude Desktop

Claude Desktop uses an mcpServers JSON entry for Streamable HTTP servers.

{
  "mcpServers": {
    "wifi-lens": {
      "url": "http://127.0.0.1:19840/"
    }
  }
}

What the AI can inspect

Nearby networks

SSID, BSSID, RSSI, band, channel, PHY, security, and capability flags.

Channel occupancy

Network counts by channel and band to spot crowded spectrum.

One AP in focus

Look up a network by BSSID when the answer needs one device, not the whole list.

Local by default

MCP is off by default. When enabled, the server binds to 127.0.0.1 and does not itself upload scan data. A connected client may send returned data to its model provider; review the client and provider settings. Do not tunnel or forward the server.

WiFi Lens is independent software. Codex and Claude are supported through the standard MCP interface, not through an official partnership.