homebox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| READONLY | Yes | Y for read-only mode, N for full read & write access. | |
| HOMEBOX_URL | Yes | Base URL of your Homebox instance, e.g. http://homebox:7745 | |
| HOMEBOX_PASSWORD | Yes | Password for the Homebox account. | |
| HOMEBOX_USERNAME | Yes | Login for a Homebox account the agent uses. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| items_listC | List/search items in the Homebox inventory. Supports free-text search and filtering by label, location, or parent item. |
| items_getA | Get full details of a single item by ID. |
| items_pathA | Get the breadcrumb path (ancestor locations) of an item. |
| items_fieldsA | List the distinct custom field names used across all items. |
| items_field_valuesB | List the distinct values used for a given custom field name. |
| items_exportA | Export the full inventory as a CSV string. |
| items_attachment_getB | Get metadata for a single item attachment. |
| items_maintenance_listA | List maintenance log entries for an item. |
| locations_listB | List all storage locations. |
| locations_treeA | Get the full nested tree of locations (and optionally items within them). |
| locations_getB | Get details of a single location, including items stored in it. |
| labels_listA | List all labels/tags. |
| labels_getA | Get details of a single label, including items tagged with it. |
| notifiers_listA | List configured notifiers (e.g. Shoutrrr/Apprise notification URLs for maintenance reminders). |
| users_self_getA | Get the profile of the currently authenticated Homebox user. |
| group_getA | Get the current Homebox group's settings (name, currency, etc). |
| group_statisticsA | Get high-level inventory statistics for the group (total items, total value, etc). |
| group_statistics_labelsA | Get item-count statistics broken down by label. |
| group_statistics_locationsA | Get item-count statistics broken down by location. |
| group_statistics_purchase_priceC | Get total purchase price statistics over time. |
| status_getA | Get the Homebox server status/version/health info. |
| currency_listA | List the currencies Homebox supports. |
| assets_get_by_idB | Look up an item by its short numeric asset ID (as printed on asset labels/QR codes). |
| qrcode_generateA | Generate a QR code image encoding the given data. Returns base64-encoded JPEG bytes. |
| reporting_bill_of_materialsA | Export a full bill-of-materials report of the inventory as a CSV string. |
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 25 tools
Most tools are clearly separated by resource and action, such as items_, locations_, labels_, and group_statistics_ prefixes. A few pairs could be confused—items_list vsocations_get both surface items in locations, and items_export vs reporting_bill_of_materials both produce CSV exports—but descriptions generally disambiguate them well.
The naming is mostly snake_case with resource-first prefixes, which gives a predictable feel. However, action ordering is inconsistent: items_fields and items_attachment_get are noun_y action, assets_get_by_id uses plural asset, qrcode_generate reverses the verb_noun convention, and reporting_bill_of_materials doesn't match the resource prefix pattern.
At 25 tools, this is on the heavy end of the spectrum. Many tools are granular read-only endpoints such as multiple group_statistics_* variants, which makes the set feel broad but not bloated; still, it is more than typically needed for a focused MCP server and could have been consolidated.
The read/query/reporting surface is comprehensive: search, get, paths, fields, statistics, exports, QR codes, and status all exist. However, there are no create, update, or delete operations for items, locations, labels, attachments, or maintenance entries, which is a significant gap for an inventory management domain and will cause dead ends for agents trying to modify data.