ApexMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APEX_HOST | Yes | The Apex controller host, e.g. http://apex.local or an IP. .local names need working mDNS on the machine running the server. | |
| APEX_PASSWORD | No | The Apex admin password. Or use APEX_PASSWORD_FILE to read it from a file. Needed for any write. | |
| APEX_USERNAME | No | The Apex username. | admin |
| APEX_BACKUP_DIR | No | Where old programs are saved before an edit. | backups |
| APEX_ALLOW_WRITE | No | Enables write tools: apex_set_outlet, apex_start_feed, apex_cancel_feed. | false |
| APEX_PASSWORD_FILE | No | Path to a file containing the password. One line is the password, two lines are username then password. Needed for any write. | |
| APEX_TIMEOUT_SECONDS | No | Timeout in seconds. | 10 |
| APEX_PROTECTED_OUTLETS | No | Comma-separated device IDs or names (e.g. ReturnPump,2_8). These accept only AUTO and their programs cannot be edited. | |
| APEX_ALLOW_PROGRAM_WRITE | No | Also enables apex_update_program. Requires APEX_ALLOW_WRITE. | false |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| apex_system_infoB | Controller identity, firmware, modules, feed state, power-failure times, network quality. |
| apex_get_probesC | Current readings. probe_type filters, e.g. Temp, pH, Amps, pwr, volts, digital, Cond. |
| apex_get_outletsC | Every outlet with mode (AUTO/ON/OFF), whether it is energized, power level and pump mode. |
| apex_water_parametersB | Temp, pH, ORP, salinity and any Trident chemistry (alk, Ca, Mg, NO3, PO4) in one short answer. |
| apex_power_summaryB | Total watts and amps, line voltage and the top consumers. Needs an energy bar such as the EB832. |
| apex_digital_inputsB | Float switches and other digital inputs as OPEN or CLOSED. |
| apex_feed_statusA | Whether a feed cycle (A to D) is running and how many seconds remain. |
| apex_module_healthB | Aquabus module presence, firmware status and packet error rate. |
| apex_get_configC | One config section: oconf, iconf, pconf, mconf, dconf, clock, misc, season or cal. Credentials are always redacted. |
| apex_probe_historyB | Probe history from the controller's log (default Temp and pH), downsampled to max_points. |
| apex_probe_statsB | min/mean/max, daily means and day-over-day drift for one probe (name or device id). |
| apex_outlet_eventsC | Exact outlet on/off times (second resolution). Only outlets with logging enabled appear. |
| apex_duty_cycleB | Percent of time an outlet was on, run count and mean run length. Good for heaters and ATO pumps. |
| apex_get_programC | The Apex program text for one outlet, or all outlets when outlet is omitted. |
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 14 tools
Most tools target clearly different facets: live outlet state vs. event log vs. duty-cycle aggregates vs. probe history vs. probe stats are well separated. The notable overlaps are apex_water_parameters versus apex_get_probes (curated chemistry summary vs. filtered raw readings) and apex_power_summary versus probes with pwr/Amps filters, but the descriptions make the intended split reasonably clear.
All names share the apex_ prefix and consistent snake_case, and the noun phrases are descriptive (probe_history, outlet_events, duty_cycle). The only inconsistency is verb style: some use get_ (get_program, get_outlets, get_config) while equally retrieval-oriented tools use bare nouns (system_info, water_parameters, feed_status).
Fourteen tools is well within the sweet spot and each one covers a distinct slice of controller telemetry (state, config, history, aggregates, health). Nothing looks like padding or a near-duplicate kept just to fill space.
For a monitoring surface it is thorough: identity, config sections, probe readings, history, stats, outlet state, event timing, duty cycle, feed status and module health are all covered. The obvious gap is any control operation — no setting outlet modes, triggering a feed cycle, or rebooting modules — so agents hit a dead end if the task requires action rather than observation.