Getting started
Three steps: sign in, save your SmartZone credentials, add the connector to Claude. Before any of them, check your controller’s certificate — it is what stops most first attempts.
0. Check your controller’s TLS certificate first
Section titled “0. Check your controller’s TLS certificate first”Your SmartZone controller must present a publicly trusted TLS certificate on
the port you expose. SmartZone ships with a self-signed certificate.
Cloudflare Workers validate certificates on every outbound fetch and expose no
skip-verify option, so a self-signed controller cannot be reached at all — not
in a degraded way, not at all.
If your controller still has its default certificate, install one from a public CA before going further. Let’s Encrypt with a DNS-01 challenge is the simplest route, because it does not require inbound port 80.
If the controller is on a private network, or you cannot replace its certificate, the alternative is the controller tunnel: a Cloudflare Tunnel that SZ-MCP creates and you run next to the controller, set up on the Private controller (tunnel) card under Configure › Controller. It is in limited rollout; contact support to have it enabled. A controller behind the tunnel does not need a public certificate.
1. Sign in
Section titled “1. Sign in”-
Go to sz-mcp.lanpulse.com.
-
Accept the Terms of Service and Privacy Policy, then continue with Google.
-
That Google account is your SZ-MCP identity — the same account backs both the web dashboard and the Claude connector.
Your session lasts 30 days.
2. Save your SmartZone credentials
Section titled “2. Save your SmartZone credentials”In the dashboard, open Configure › Controller (/settings/controller) and
fill in the SmartZone login card. The login belongs to your organisation, and
only an organisation admin can save, test or delete it.
| Field | What it takes |
|---|---|
| Host / FQDN | The controller’s bare hostname or IP — sz.example.com. No scheme, no path, no port |
| Port | A choice of two: 8443 (the default, SmartZone’s API port) or 443 (behind NAT, a reverse proxy or the controller tunnel). No other port is allowed |
| Username | A SmartZone admin username |
| Password | That admin’s password. Never shown again once saved |
| Label | Optional. Your own nickname for this controller |
Then click Save & detect.
What “Save & detect” actually does
Section titled “What “Save & detect” actually does”It logs in to your controller for real. SZ-MCP first asks the controller which
API versions it supports (GET /wsg/api/public/apiInfo, which needs no
password), picks the newest, and logs in once with that version — so a pass
means the whole chain works: the certificate, the host, the port, the username
and the password.
On success the dashboard names the controller and the version it settled on,
for example Saved: sz.example.com:8443. Detected API version v14_0.
If it fails, the message reads Not saved: followed by the error code and its
detail. See
Troubleshooting — and read
SmartZone credentials for what each
error code means and how version detection works.
3. Copy your MCP URL and connect Claude
Section titled “3. Copy your MCP URL and connect Claude”Copy the MCP URL from the dashboard — it is https://sz-mcp.lanpulse.com/mcp/
— then follow Connecting to Claude.
The URL is the same for every user. What identifies you is the OAuth token Claude obtains when it connects, which is bound to your account.
4. Try it
Section titled “4. Try it”Ask Claude something concrete:
List the AP zones on my SmartZone.
Then something that needs discovery:
Find the SmartZone endpoint that creates a WLAN, and tell me which fields it requires.
If both work, the connector is healthy end to end. Move on to the examples.