openwifi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PATCH_SEARCH_URL | Yes | URL of the openwifi-kernel-patches service (e.g., http://<host>:20503) | |
| TICKET_INDEX_URL | Yes | URL of the openwifi-ticket-index service (e.g., http://<host>:20504) | |
| CLAUDE_OPENWIFI_ROOT | Yes | Absolute path to the Claude-OpenWiFi project directory |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_helpA | Print Claude-OpenWiFi's make help — the list of available build targets and their expected arguments. Use this before calling any other build tool if you're unsure of the syntax. |
| build_statusA | Show running builds and recently-finished artifacts. Includes per-build tags (used with build_tail / build_fetch / build_deploy). |
| build_startA | MUTATING — start a wlan-ap build. Every build parameter is explicit; nothing is defaulted. The build runs on the build host over SSH and takes 30-90 minutes. This tool returns as soon as the build is launched — poll with build_status or build_tail(tag) to track progress. |
| build_tailA | Show the tail of a build log. Use the tag returned by build_start or listed in build_status. |
| build_fetchA | Copy build artifacts (kernel + userspace image + build metadata) back to the Mac under Claude-OpenWiFi/artifacts//. Non-mutating on the build host; only touches local disk. |
| build_deployA | MUTATING — sysupgrade a real access point with the image built
under |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct and unambiguous purpose: help, status, start, tail, fetch, and deploy. No two tools overlap in functionality, ensuring an agent can easily select the correct one.
All tools follow a consistent 'build_<verb>' pattern with imperative verbs (help, status, start, tail, fetch, deploy). This makes the tool surface predictable and easy to navigate.
With 6 tools, the set is well-scoped for the domain of building and deploying OpenWiFi firmware. It covers the entire workflow without being excessively large or insufficient.
The tools cover the core lifecycle: help, start build, monitor progress (status, tail), fetch artifacts, and deploy. Minor omissions like a cancel or cleanup tool exist, but the essential path is complete.