Show HN: Edi Life OS – self-hosted life dashboard with an MCP server for AI

Most of us run our lives throughout a to-do app, a habit tracker, a budgeting spreadsheet, a Pomodoro timer and a notes app — and none of them cognize concerning all other. Edi Life OS puts all of it in one calm, personal dashboard and connects the small things you do today to the direction you desire your existence to take.

• Everything in one place. Ten workspaces portion one design, one sign-in and one database.
• Connected, not fair collected. Habits run goal progress, Kanban cards display up in the calendar, and the Overview turns it all into one regular score.
• Yours. Runs on any PHP + MySQL host, equal cheap shared hosting. No subscription, no tracking, no vendor lock-in.
• AI-ready. A built-in MCP server lets Claude and another assistants peruse your dashboard, scheme goals, log habits and track expenses for you.

Growth — Six existence dimensions, all connected to long-term goals, SMART goals, habits and tasks. Guided weekly, monthly and quarterly reviews.	Focus — Pomodoro sessions alongside breaks, a built-in concentration soundtrack and a landscape that follows the period of day.
Habittify — Small regular habits, streaks and a seven-day image of your consistency.	Kanban — Boards alongside labels, priorities, due dates, checklists, comments and attachments.

Dates prosecute Asia/Tehran. The climate cardstock shows Qeshm Island via Open-Meteo; its tide fig is a modeled estimate, not for navigation.

Edi Life OS ships alongside an optional MCP server that exposes 26 tools throughout your dashboard, goals, tasks, habits, finances and notes. Connect it to Claude Desktop, Claude Code or any MCP client and ask in plain language:

"Show me my LifeOS dashboard."

"Create a SMART goal called Build a residence studio, due in three months, and add Buy acoustic panels as a task."

"Mark Reading complete for today."

"Log a 450,000 Toman food disbursal and display my balance."

The MCP server talks to your app lone through its token-protected HTTP API. It never touches your repository or credentials. Setup takes a infinitesimal — see MCP server below.

git copy https://github.com/edrisranjbar/lifeos.git && cd lifeos cp .env.example .env # set your sign-in and passwords docker create up -d

Open localhost:8080 and sign in. MySQL, the app and your attachments all live in their own volume, so docker create up -d --build following a git drag upgrades without losing data.

Download lifeos-<version>.zip from the latest release and extract it into your hosting home directory, so public_html/ becomes your web base and the backend sits safely complete it. Copy config.example.php to config.php, inhabit in your MySQL details, and open your site. See the deployment guide for details.

You need PHP 8.1+ (with pdo_mysql and mbstring) and MySQL 8+ (or MariaDB 10.4+).

git copy https://github.com/edrisranjbar/lifeos.git cd lifeos cp config.example.php config.php # PowerShell: Copy-Item config.example.php config.php

Edit config.php alongside your repository association and the username and password you desire to sign in with, afterward commencement the server:

php -S localhost:8000 -t public_html server.php

Open localhost:8000 and sign in. The repository and tables are created on archetypal use. You can alter your sign-in afterward in Settings.

A personal /api/v1 API covers the dashboard, goals, tasks, habits, finances and sticky notes. It uses its own transporter token, distinct from your browser sign-in.

php -r "echo bin2hex(random_bytes(32));"

Set the outcome as api_token in config.php (or the LIFEOS_API_TOKEN surroundings variable), then:

curl -H "Authorization: Bearer $LIFEOS_API_TOKEN" https://your-host/api/v1/dashboard

See the API reference for endpoints, payloads and errors.

cd mcp npm ci cp .env.example .env # set LIFEOS_BASE_URL and LIFEOS_API_TOKEN npm start

The server runs complete stdio; there is no hosted MCP endpoint. The MCP guide lists all tool and shows client configuration for Claude and Codex.

• Everything lives in your MySQL database. Habits use dedicated tables; another workspaces shop JSON documents in app_state.
• Saves use revision checks, so a old tab can't silently overwrite newer changes. API writes use transactions and row locks.
• Data from older browser-only versions is imported once; conflicting copies are archived as legacy_backup_* records.
• Back up the database, attachment records and your configuration together.

Moving from the old Habittify SQLite database? See migrating Habittify.

Edi Life OS is built for a single owner.

• The API token grants peruse and compose admission to all supported domain. Token scopes and app-level charge limiting are not implemented, so set petition limits at the hosting layer.
• Use HTTPS anyplace another than localhost, and keep tokens out of URLs, frontend code, screenshots and logs.
• Secret notes are hidden from API says by default. The concealed emblem controls visibility; it is not distinct encryption.

public_html/ Browser workspaces, shared resources and Apache admission points lib/ API domains, reply helpers and province transactions mcp/ Optional Node.js stdio MCP server tests/ Timer, API, MySQL and integration checks docs/ Guides, affirmative README screenshots in docs/media config.example.php Configuration template (no genuine credentials) server.php Development router and use routing api.php HTTP API admission point 

Built alongside PHP, MySQL and vanilla JavaScript — no frontend build step, no framework.

Dockerfile, docker-compose.yml and docker/config.php run the app alongside configuration from surroundings variables.

• API reference — authentication, routes, data formats and concurrency
• MCP guide — tools, surroundings settings and client setup
• Deployment guide — Apache, shared hosting, backups and migration
• Development guide — local checks and available integration fixtures
• Growth workspace · Debts and credits

MIT © 2026 Edris Ranjbar. Use it, fork it and build on it.

Ideas, bug reports and drag requests are welcome. Open an issue to commencement a conversation, and see the development guide to run the checks locally.