Allourthings

io.allourthingsPublished by allourthings.iov0.2.0Updated Oct 24, 2026

AI-powered household inventory — query everything you own via natural language

VerifiedSTDIODesktop onlyProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

A local household inventory server that lets an AI assistant add, search, update and delete items you own, with attachments like manuals and receipts.

What you can do
Add, retrieve, update and delete inventory items with fields such as category, brand, purchase price, warranty and location, plus custom fields. List items filtered by category, location or tags, and run full-text search across all item fields. Attach local files or files downloaded from a URL to an item, retrieve attachments as base64, and remove them. Store everything in a plain vault directory of per-item folders that can be browsed and edited directly.
When to use it
Useful when you want to catalog possessions — appliances, electronics, collections — and ask plain-language questions about them, such as what you own in a room, when a warranty expires, or how much you spent on a category.
Requirements
Runs as a local process via npx on macOS, Windows or Linux with an MCP-compatible desktop client such as Claude Desktop. Node.js is needed for npx. Data is stored in a vault directory, set by the ALLOURTHINGS_DATA_DIR environment variable or the --data-dir argument, defaulting to ~/Documents/AllOurThings. No authentication is declared.
Before you install
The assistant can write, change and delete inventory items and attachments, and attach_from_url downloads files from arbitrary URLs into your vault. The vault holds personal purchase details, receipts and photos in plain files on disk, so anyone with filesystem access can read them. Point the data directory at a location you are comfortable exposing, and review deletions.

Installation

In SourceWeft

  1. Open Allourthings in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

AllOurThings

Your things, understood by AI.

AllOurThings is an inventory system that works the way you do. Catalog anything you like from your home appliances to your Pokémon cards — then ask plain-English questions and get instant answers.

Website: allourthings.io

Packages

PackagenpmDescription
packages/mcp-server@allourthings/mcp-serverMCP server — connects your inventory to Claude Desktop and other MCP clients
packages/cli@allourthings/cliCLI — manage your inventory from the terminal

Quick start

Desktop only. Requires macOS, Windows, or Linux with Claude Desktop or another MCP-compatible client.

1. Add to Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "allourthings": {      "command": "npx",      "args": ["-y", "@allourthings/mcp-server", "--data-dir", "~/Documents/AllOurThings"]    }  }}

Restart Claude Desktop. Your inventory vault will be created automatically on first use.

2. Start asking questions

  • "Add my Bosch washing machine, bought from John Lewis for £649 in January 2024 with a 2-year warranty"
  • "What appliances do I own?"
  • "What's in the kitchen?"
  • "When does my TV warranty expire?"
  • "Search for anything Samsung"
  • "How much have I spent on electronics?"

How it works

The MCP server exposes your inventory to any MCP-compatible AI client via 11 tools:

ToolDescription
add_itemAdd a new item (names must be unique)
get_itemGet an item by ID or name
list_itemsList items, optionally filtered by category, subcategory or tags
update_itemUpdate fields on an item; set a field to null to clear it
delete_itemDelete an item by ID
search_itemsSearch field values; every word must match
get_item_fieldsList the field names in use across your catalog
add_attachmentAttach a base64-encoded file (manual, receipt, photo, warranty, other) to an item
attach_from_urlDownload a file from a URL and attach it to an item
get_attachmentGet an attachment as base64
delete_attachmentRemove an attachment from an item

Failures return isError: true with a message. See the MCP server README for parameters, validation rules and configuration.

Data

Vault structure

Your inventory lives in a vault — a plain directory on your filesystem. Each item gets its own folder:

~/Documents/AllOurThings/  items/    dyson-v15-detect-a1b2c3d4/      item.json      manual.pdf      receipt.jpg    samsung-65-qled-tv-b5c6d7e8/      item.json      warranty.pdf

Attachments (manuals, receipts, photos) sit alongside the item JSON. You can browse and edit the vault directly in Finder or File Explorer.

Item schema

Every item has required fields (id, name, created_at, updated_at) and well-known optional fields:

category subcategory brand model purchase_date purchase_price currency warranty_expires retailer location features notes tags attachments

The attachments field links PDFs and images stored in the item's folder:

json
{  "attachments": [    { "filename": "manual.pdf",  "type": "manual"   },    { "filename": "receipt.jpg", "type": "receipt"  },    { "filename": "photo.jpg",   "type": "photo"    }  ]}

You can also add any custom fields you like — they are preserved as-is.

CLI

A standalone terminal tool for power users and scripting. Works on macOS, Windows, and Linux. No AI client required.

bash
# Run without installingnpx @allourthings/cli list
# Or install globallynpm install -g @allourthings/cli

Commands

bash
allourthings init                                    # choose your vault folder (run once)allourthings search <query>                          # search field valuesallourthings list [-c <category>] [-s <subcategory>] [-t <tag>]allourthings get <id-or-name>                        # show full item detailallourthings add <name> [options]                    # add a new itemallourthings update <id> [options]                   # update fields; --unset to clearallourthings delete <id>                             # delete an item (asks to confirm)allourthings attach add|url|get|rm ...               # manage attachments

Add --json for machine-readable output. See the CLI README for every option.

Examples

bash
# Add an itemallourthings add "Bosch Washing Machine" --brand Bosch --model "WGG244A9GB" \  --category appliance --location kitchen \  --purchase-date 2024-01-15 --price 649 --currency GBP \  --warranty 2026-01-15 --retailer "John Lewis"
# Search and pipe to jqallourthings search "warranty" --json | jq '[.[] | {name, warranty_expires}]'
# Attach a manualallourthings attach add 6164c373 ~/Downloads/bosch-manual.pdf --label "User manual"
# Update a fieldallourthings update 6164c373 --warranty 2027-01-15
# Use a custom data directoryallourthings --data-dir ~/Dropbox/AllOurThings list

Development

Prerequisites

  • Bun — brew install bun
  • Task — brew install go-task

Install dependencies

bash
bun install

Tasks

TaskDescription
task devSeed vault + open MCP Inspector — fastest way to test
task dev:mcpStart MCP server in watch mode (stdio)
task test:runRun automated tests
task seedAppend test items to dev vault
task seed:resetClear dev vault and re-seed
task inspectOpen MCP Inspector (dev mode, no build required)
task inspect:prodBuild, then open MCP Inspector against compiled dist
task buildCompile MCP server to dist/
task build:cliCompile CLI to dist/
task cli -- <args>Run CLI from source against dev vault, e.g. task cli -- list
task typecheckRun TypeScript type checking
task cleanRemove dist/
task clean:vaultDelete local dev vault

All tasks use ./dev-vault by default. Override with DATA_DIR=/your/path task <command>.

License

MIT — see LICENSE.

Source: README.md at commit 1048882

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts