HortusFox MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HORTUSFOX_URL | Yes | Base URL of your HortusFox instance. | |
| CF_ACCESS_CLIENT_ID | No | Optional shorthand for Cloudflare Access Service Token Client ID. | |
| HORTUSFOX_API_TOKEN | Yes | HortusFox API token generated in Admin -> API. | |
| CF_ACCESS_CLIENT_SECRET | No | Optional shorthand for Cloudflare Access Service Token Client Secret. | |
| HORTUSFOX_CUSTOM_HEADERS | No | Optional JSON map of custom HTTP headers (e.g. reverse proxy or auth tokens). |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_plantsB | Retrieve active plants, species, locations, and care statuses from HortusFox. |
| get_plant_detailsB | Get deep plant information, care attributes, last watered/fertilized timestamps, and custom properties. |
| get_plant_historyA | Retrieve historical log events, care notes, watering records, and observations for a plant. |
| add_plant_logB | Log watering, repotting, fertilization, or observation notes for a plant directly from conversation. |
| search_plantsA | Search for plants across all locations by name, scientific name, or tag. |
| list_locationsA | List all growing locations (e.g. Balcony, Indoor, Garden) in HortusFox. |
| update_plant_attributeC | Directly update a plant default attribute (e.g., last_watered, last_fertilised, last_repotted, health_state, notes). |
| list_inventoryA | Retrieve inventory items (fertilizers, substrates, pest control, supplies) and stock counts from HortusFox. |
| update_inventory_amountB | Increment or decrement the stock count of an inventory item in HortusFox. |
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 9 tools
Most tools map to clearly distinct resources and actions: plants, plant history, locations, and inventory. The only minor ambiguity is between search_plants and list_plants, which both return plant collections but differ in query flexibility.
All tool names follow a consistent lowercase snake_case verb_noun pattern, with clear verbs like search, list, get, add, and update. There is no mixing of styles or vague names.
Nine tools is a well-scoped set for a plant management server, covering retrieval, updates, logging, and inventory without unnecessary redundancy. Each tool has a clear role.
The read, update, and logging operations are solid, but the set lacks create or delete operations for plants, locations, and inventory items. This creates a notable lifecycle gap for agents managing a HortusFox collection.