openwebnet-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_documentationA | Fuzzy and keyword search across OpenWebNet protocol specifications and Home Assistant MyHOME guides. |
| get_who_specA | Retrieve full technical specification, WHAT commands, and DIMENSIONS for an OpenWebNet WHO family. |
| list_who_catalogA | Return complete inventory table of all 20+ OpenWebNet WHO families with archive status and HA platform. |
| get_ha_guideB | Fetch complete markdown guide for configuring and troubleshooting Home Assistant entities. |
| lookup_frame_syntaxB | Look up OpenWebNet message grammar, regex templates, and parameter formats. |
| parse_and_validate_frameA | Parse a raw OpenWebNet frame string and perform semantic protocol validation. |
| draft_own_frameC | Construct and validate a syntactically correct OpenWebNet frame. |
| draft_ha_configA | Generate production-ready Home Assistant YAML configuration for any MyHOME entity. |
| get_code_signatureB | Inspect Python AST signatures, public methods, and docstrings from custom_components/myhome or OWNd. |
| rescan_documentationA | Flush caches and reload all OpenWebNet specifications, markdown documents, and codebase AST models. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| boost | Context boost for AI agents: OpenWebNet protocol syntax, WHO subsystem mappings, and Home Assistant integration standards. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resource_who_catalog | Read-only catalog of all OpenWebNet WHO families. |
| resource_protocol_grammar | Read-only OpenWebNet formal grammar and frame templates. |
| resource_docs_toc | Read-only table of contents for OpenWebNet & MyHOME documentation. |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: search, retrieve specs, list catalog, get guide, lookup syntax, parse, draft, generate config, inspect code, and refresh caches. There is no overlap in functionality.
All tools use snake_case with consistent verb-noun patterns (e.g., search_, get_, list_, lookup_, draft_, rescan_). The naming is predictable and uniform.
With 10 tools, the set is well-scoped for a documentation and frame utility server, covering search, retrieval, parsing, drafting, and maintenance without redundancy or bloat.
The surface covers search, spec lookup, catalog listing, guides, syntax reference, parsing/validation, frame drafting, HA config generation, code inspection, and cache management. Minor gaps like a tool for comparing frames or bulk operations exist, but core workflows are complete.