Ask your home.
Your AI assistant's memory for everything in and around your home.
▶ Watch the 1-minute demo on YouTube
Home Memory is an MCP server that gives your AI assistant structured, persistent knowledge about your home: every room, every device, every pipe and cable, every item you own.
It works with AI clients on your computer that support MCP, including Claude Desktop, Claude Code, Codex App, Codex CLI, and others. You talk naturally; the AI reads and writes your home data through Home Memory's tools.
Document what exists, plan what's coming, and keep track of what's been removed.
No app to learn. No forms to fill out. Your home data stays in a single file on your machine, and the AI is your interface.
Tell your AI about your heat pump, your car, your power tools, or your wine collection, and it extracts the relevant details and stores them as structured data in your local database. Snap a photo of a device or hand it an invoice. Same result. Ask "What's in the basement?" or "When is my car due for inspection?" and get answers from real data.
Document anything by just talking:
"I have a Daikin Altherma heat pump in the utility room."
Your AI finds the right category, resolves the location, and creates the element. No manual data entry.
"My car is a 2023 Toyota Corolla Hybrid, next inspection is due in March."
Not just building infrastructure: vehicles, tools, appliances, valuables, anything that belongs to you.
Ask questions about your home:
"What's in the basement?" · "Show me all planned purchases." · "Where is my washing machine?"
Upload a photo and let your AI identify it:
(attach a photo of a device) "What is this? Add it to the utility room."
Vision-capable AIs recognize the device and create the element via MCP.
Read an invoice and extract devices:
(attach a PDF invoice) "Extract the installed devices and add them to my home."
Track connections between elements:
"The circuit breaker panel feeds the kitchen outlet via NYM-J 3x1.5."
Cable routes, pipe runs, duct paths, all documented as connections between elements.
Plan renovations:
"We're planning a PV system on the roof." · "The old oil heater was removed last year."
Track what's planned, what exists, and what's been removed.
The release ZIP is self-contained. No .NET, no Firebird, no other software to install.
- Download the latest release ZIP from GitHub Releases
- Extract to a folder, e.g.
C:\HomeMemory\
Choose one of the following clients:
Codex App (OpenAI)
- Open the Codex App
- Click File > Settings, then select MCP servers on the left
- Click + Add server
- Name:
home-memory - Command to launch:
C:\HomeMemory\HomeMemoryMCP.exe - Leave transport on STDIO (default)
- Click Save, then restart the app if needed
Or via Codex CLI:
codex mcp add home-memory -- "C:\HomeMemory\HomeMemoryMCP.exe"Claude Desktop
- Open Claude Desktop
- Click the Claude menu → Settings → Developer → Edit Config
- This opens the config folder with
claude_desktop_config.jsonselected. Open it in any text editor - Add
home-memoryinside the"mcpServers"object:
{
"mcpServers": {
"home-memory": {
"command": "C:\\HomeMemory\\HomeMemoryMCP.exe"
}
}
}If you already have other MCP servers configured, add the "home-memory" entry next to them inside the existing "mcpServers" block.
- Save the file and restart Claude Desktop
Home Memory is available in both the Chat tab and the Code tab. The Code tab is recommended: it runs in agentic mode with no tool-call limits, which works much better for MCP-heavy workflows.
Claude Code (CLI)
claude mcp add home-memory --scope user -- "C:\HomeMemory\HomeMemoryMCP.exe"On first launch, Home Memory automatically creates a local database with over 100 categories and a default house structure (floors, rooms, garage, outdoor areas). No setup wizard needed.
Try these prompts in order:
"Show me the structure of my home."
You should see your default house structure: ground floor, upper floor, basement, each with rooms. This confirms everything is working.
"I have a Bosch washing machine in the basement."
Your AI creates the element, finds the right category, and places it in the basement, all in one step. Ask "What's in the basement?" to verify.
"We're planning to install a heat pump in the utility room."
Creates a planned element, so you can track what exists and what's coming.
If it works, you're done. Everything from here is just talking to your AI. Add rooms, rename floors, document your electrical panel, upload a photo of a device. The AI handles the rest.
Home Memory runs locally, but you can use it from your phone through the remote access features that Claude Code and Codex offer. In both cases your Home Memory database and MCP server stay on your machine; the phone is just a remote window into a session running on that host.
Handy whenever you are away from your computer and want to look something up or capture it on the spot, whether at the fuse box, out in the garden, or snapping a photo of a new appliance.
- Claude Code: start a local session, enable Remote Control, then continue it from the Claude mobile app or
claude.ai/code. Requires a signed-in Claude account. - Codex: enable remote connections in the Codex App on your host machine, then scan the QR code from the ChatGPT mobile app.
Requires .NET 10 SDK and Firebird 3.0.
git clone https://github.com/impactjo/home-memory.git
cd home-memory
dotnet publish HomeMemoryMCP -c ReleaseSee Setup Guide for details on Firebird configuration and environment variables.
You ──── AI Assistant ──── Home Memory MCP ──── Local Database
(natural language) (20+ tools) (Firebird, single file)
Home Memory implements the Model Context Protocol (MCP), an open standard that lets AI assistants use external tools. When you talk to your AI about your home, it calls Home Memory's tools behind the scenes to read, create, update, and search your home data.
Your data stays local. The database is a single file on your machine. Nothing is sent anywhere except to the AI you're already talking to.
| Tools | What they do | |
|---|---|---|
| Explore | get_structure_overview, find_element, list_elements, get_element_details, get_recent_changes |
Browse your home, search by name/path/status, get full details |
| Manage Elements | create_element, update_element, delete_element, move_element |
Add devices, furniture, fixtures, or entire rooms and floors |
| Connections | get_connections, get_connection_details, create_connection, update_connection, delete_connection |
Document physical lines: cables, pipes, ducts, conduits |
| Categories | list_categories, get_by_category, get_category_details, create_category, update_category, delete_category |
Over 100 built-in, editable categories across all domains |
| Status | list_statuses, create_status, update_status, delete_status |
Track what's existing, planned, or removed |
Electrical (circuits, PV, wallbox, home automation) · HVAC · Plumbing · IT & Communications · Security (alarm, fire, surveillance) · Building Materials · Landscaping (garden, pool, irrigation) · Household (appliances, furniture, valuables) · Vehicles · Tools · Health · Sports & Leisure
Every category, every element, every status is editable. Rename, add, or remove anything to match how you think about your home.
- Over 100 categories organized by trade and domain, from circuit breakers to garden sprinklers to vehicles
- Default house structure with floors, rooms, garage, and outdoor areas, customizable by talking to your AI
- Auto-setup on first run, no manual database creation needed
- Flexible naming: your AI can use "Ground Floor" or "GF", the server resolves both
| Client | Status |
|---|---|
| Codex App (OpenAI) | Tested |
| Claude Desktop (Chat tab + Code tab) | Tested |
| Claude Code (CLI) | Tested |
| Codex CLI (OpenAI) | Tested |
| Any MCP-compatible client | Should work (stdio transport) |
The release ZIP is a self-contained Windows build with all dependencies included (no .NET or Firebird installation required). On macOS and Linux, you can build from source with .NET 10 and Firebird 3; see the Setup Guide for details.
| Environment Variable | Purpose | Default |
|---|---|---|
HOME_MEMORY_DB_PATH |
Database file location | %LOCALAPPDATA%\HomeMemory\homememory.scd (Windows) · ~/.local/share/HomeMemory/homememory.scd (Linux) · ~/Library/Application Support/HomeMemory/homememory.scd (macOS) |
HOME_MEMORY_FBCLIENT |
Path to Firebird client library | Bundled with release / Firebird installation |
Stdio is the default and works for almost everyone. HTTP mode lets you run Home Memory as a persistent service on a NAS, homelab box, or another machine on your LAN. See docs/HTTP-MODE.md for setup, database locking, LAN access, and optional Bearer authentication.
- .NET 10 with ModelContextProtocol SDK
- Firebird Embedded: local database engine, single-file storage
- Raw SQL with recursive CTEs, no ORM overhead, transparent and auditable
Home Memory is early-stage. Feedback is welcome. Right now, the best way to contribute is:
- Open an issue for bug reports, feature ideas, or questions
- Share your use case: how are you using Home Memory? What's missing?
- Spread the word if you find it useful
If you'd like to build and explore the code locally, see the Setup Guide.
Home Memory builds on a proven data model from Smartconstruct, a desktop application for documenting physical assets, refined through real-world use in residential construction projects.