Skip to main content
Glama
luisriverag

homebox-mcp

by luisriverag

Related Servers

Alternatives to homebox-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      MCP server for Homebox home inventory, enabling natural language queries and management of items, locations, tags, warranties, maintenance, and attachments.
      39
      337 PyPI
      8
      MIT
    • F
      license
      C
      quality
      F
      maintenance
      An MCP server that exposes Homebox inventory management as tools for AI agents, enabling search, add, update, delete products, locations, tags, and maintenance entries.
      17
      2
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for managing Homebox inventory via AI assistants, enabling item management, location organization, and label categorization.
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage inventory items, locations, and labels in a self-hosted Homebox instance using natural language, with support for flexible URL configurations.
      21
      4
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with a Homebox inventory system to search, create, update, and manage items, locations, and labels.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural-language read and write access to a Homebox inventory, including searching and managing items, locations, tags, and attaching files such as receipts and warranties.
      MIT

    TDQS

    B3.3/5.0

    Scored across 25 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count3/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues