Mcp Server
Wire your agent to query a local AllOurThings household inventory folder in plain English instead of digging through files manually.
Overview
io.allourthings/mcp-server is a Build-phase MCP server that exposes your local AllOurThings household inventory to an AI agent for natural-language search and answers.
What is this MCP server?
- Stdio MCP server `@allourthings/mcp-server` (v0.2.0) for Model Context Protocol clients
- Natural-language questions over everything stored in your AllOurThings household inventory
- Data rooted at `~/Documents/AllOurThings` or custom path via `--data-dir` / `ALLOURTHINGS_DATA_DIR`
- npm registry install with named package argument for data directory configuration
- GitHub source at matt-harding/allourthings-mcp for self-hosted or fork workflows
- Server version 0.2.0 per server.schema.json
- Single npm package `@allourthings/mcp-server` with stdio transport
- Default data path `~/Documents/AllOurThings` when env var unset
Community signal: 1 GitHub stars.
What problem does it solve?
Household inventory lives in a structured local dataset that agents cannot see unless you build a custom bridge or copy-paste item lists into every chat.
Who is it for?
Builders and homeowners who already use AllOurThings on disk and want Claude Code or Cursor to query what they own without leaving the editor.
Skip if: Teams needing multi-user cloud inventory, ecommerce catalog management, or warehouse systems with no AllOurThings data layout.
What do I get? / Deliverables
After you register the stdio server and set the data directory, your agent can answer inventory questions from the same AllOurThings files on your machine.
- MCP-registered stdio bridge from agent to on-disk inventory
- Natural-language inventory answers via agent tool calls
- Configurable local data directory for dev and backup paths
Recommended MCP Servers
Journey fit
Skillselion shelves MCP servers where builders attach external capabilities to Claude Code, Cursor, or Codex; inventory lookup is an integration layer, not a launch or growth tactic. Natural-language access to on-disk inventory JSON fits the integrations subphase because it extends the coding agent with a dedicated stdio MCP bridge to personal data.
How it compares
Local household-inventory MCP bridge, not a general-purpose agent skill or hosted SaaS API.
Common Questions / FAQ
Who is io.allourthings/mcp-server for?
Solo builders and households using AllOurThings locally who want MCP-enabled agents to query owned items in natural language.
When should I use io.allourthings/mcp-server?
When you are in the build/integrate step and need your coding agent to read inventory from `~/Documents/AllOurThings` or a custom data dir via stdio MCP.
How do I add io.allourthings/mcp-server to my agent?
Install `@allourthings/mcp-server` from npm, set `ALLOURTHINGS_DATA_DIR` or `--data-dir`, and add a stdio MCP server entry in Claude Code, Cursor, or another MCP client.