# Edi Life OS combines personal planning tools with a local AI interface

An open-source project called Edi Life OS has launched as a self-hosted dashboard that combines several kinds of personal organization software and lets compatible AI assistants act on the data through the Model Context Protocol. The project is designed for people who would otherwise divide their planning among task managers, habit trackers, budgeting files, timers and note-taking applications.

The software groups its features into a single web interface. Its growth section connects six life areas to long-term goals, shorter SMART goals, habits and individual tasks. It also includes guided weekly, monthly and quarterly reviews. Other modules provide Kanban boards, a Pomodoro-style focus timer, habit streaks, personal-finance records and sticky notes.

A key part of the release is an optional MCP server exposing 26 tools. MCP-compatible clients can use those tools to create goals and tasks, record expenses, inspect balances, update habits and work with notes. The server communicates with the application through a token-protected HTTP API and runs over standard input and output rather than as a hosted internet endpoint. According to the project documentation, it does not directly access the application's database or user credentials.

That design gives users a way to connect an assistant while keeping the primary installation under their control. The API token is separate from the browser login, and configuration files containing credentials are excluded from version control by default. Operators still need to protect the host, token and web deployment as they would for any application holding private planning and financial information.

Edi Life OS can be deployed with Docker or on a conventional PHP host. The documented requirements for the latter are PHP 8.1 or newer and MySQL 8 or MariaDB 10.4 or newer. A Docker Compose setup separates the application, database and attachments into persistent volumes so upgrades do not erase stored information. The non-Docker route creates the database tables on first use after configuration.

The project uses PHP, MySQL and vanilla JavaScript, without a front-end build step or framework. Its code is distributed under the MIT license, allowing users to inspect, modify and redistribute it. The initial release is best understood as a developer-led open-source product rather than a hosted consumer service: installation, maintenance, backups and access controls remain the operator's responsibility.

The release adds to a growing class of self-hosted tools that pair private personal data with standardized AI integrations. Its practical appeal will depend on whether users value one integrated dashboard enough to administer their own server, but its MCP interface provides a concrete bridge between personal records and assistant-driven workflows.