Skip to main content
Glama
Sign In
Junk Drawer MCP Server

Junk Drawer MCP Server

by OpenCode-Projects-AtlasRearden8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Junk Drawer MCP Server

No user-submitted related servers found.

    Related Servers

    • AllOurThings MCP Server

      matt-harding
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables cataloging and managing personal inventory (items, attachments) through natural language, allowing users to add, search, update, and retrieve item details and attachments via MCP tools.
      1
      MIT

    • Hoardo MCP server

      Johanduus
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets AI apps search and manage a home inventory of numbered boxes, rooms and lists, so users can find where an item is stored, add or move items and boxes between rooms, and work through packing, lending, rental and stocktake lists from chat. Changes made through the connected app apply to the user's account immediately.
      CC BY-4.0

    • inventory-mcp

      golem15com
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Inventory (whereiput.it) that enables searching, full CRUD operations on items/locations/areas, and AI-powered photo recognition flow from MCP-compatible clients.
      -

    • lists

      perintyler
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables creating and managing collections of items by adding entries, checking them off, and deleting them through MCP tools.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target distinct intents: fuzzy lookup (search), detail retrieval (where_is), browsing (list_by_room), mutation (mark_moved, remove_item, add_item), and history (move_history). The one soft overlap is where_is, which promises 'moves' in its answer, versus move_history which returns the full hop log — an agent may hesitate between them. search vs list_by_room also brush against each other but the descriptions make the fuzzy-vs-enumerated distinction clear.

    Naming Consistency3/5

    All names are snake_case, but the verb_noun convention is only partially followed: add_item, remove_item, list_kinds, list_by_room, mark_moved are clean, while search and summary are bare nouns and where_is / move_history break the verb_noun pattern. Readable overall, but not a predictable schema an agent can pattern-match on.

    Tool Count5/5

    Nine tools is well within a healthy range and each covers a distinct slice of the household-catalogue lifecycle (capture, find, browse, relocate, remove, report). Nothing feels padded or missing at the count level.

    Completeness4/5

    The surface covers capture (add_item), retrieval (search, where_is, list_by_room), location mutation (mark_moved), history (move_history), deletion (remove_item), and reporting (summary, list_kinds) — a full lifecycle for the stated domain. The notable gap is editing item metadata (typo in name, corrected tags or photo_hint); the only workaround is remove_item plus re-add, which destroys move history.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources