Lifeos

What the lifeos MCP server does

The lifeos MCP server gives an AI assistant access to a self-hosted personal dashboard covering daily planning and long-term tracking. The underlying Life OS application includes workspaces for overview data, growth, focus sessions, habits, Kanban work, calendar items, goals, finances, Markdown notes, and sticky notes.

Through MCP, an assistant can work with information from the dashboard, goals, tasks, habits, finances, and notes. Example interactions described by the project include viewing the dashboard, creating a SMART goal with a task, marking a habit complete, and recording an expense before checking the balance.

How it works

The lifeos MCP server communicates with the application through its token-protected HTTP API. It does not connect directly to the MySQL database and does not handle the application’s database credentials. This separates assistant access from the storage layer while allowing supported reads and updates through the same API used by the application.

The MCP component is optional. You first run the Life OS application and then connect an MCP-compatible client to its MCP server. The README describes support for Claude Desktop, Claude Code, and MCP clients generally, but the supplied material does not specify a client-specific configuration format or endpoint.

Setup and configuration

Life OS can be started with Docker Compose, installed on PHP-based shared hosting, or run locally with PHP. The local requirements are PHP 8.1 or newer with pdo_mysql and mbstring, plus MySQL 8 or MariaDB 10.4 or newer. Docker Compose starts the application and MySQL with persistent volumes for the database and attachments.

For a local installation, copy the example PHP configuration file, add the database connection and sign-in credentials, and start PHP’s built-in web server. Shared-hosting deployments use the release archive, a copied configuration file, and a MySQL database. The project warns that configuration files contain real credentials and should not be committed.

After the application is available, configure an MCP client to use the Life OS MCP server as described in the project’s MCP documentation. Authentication is token-based, so the client must have the access details required by that server. Exact token names and client configuration fields are not provided in the supplied README excerpt.

Tools and capabilities

The README identifies 15 MCP tools distributed across the main dashboard areas. Supported capabilities include:

• Reading dashboard information.
• Creating and working with SMART goals.
• Managing tasks and Kanban-related work.
• Recording habit completion.
• Logging expenses and checking financial balances.
• Reading and updating supported notes.

The application itself also tracks income, budgets, debts, credits, recurring financial entries, habit streaks, goal measures, checklists, due dates, and Markdown notes. The excerpt does not map each of these application features to an individual MCP tool, so they should not be assumed to be separately exposed through MCP.

Limitations and notes

The lifeos MCP server is designed for a Life OS instance that you host and configure; it is not described as a standalone hosted finance service. Its available data depends on the connected application and its token-protected API. The server does not access the database directly.

The README names Claude Desktop and Claude Code as supported clients and refers to other MCP clients, but it does not list tested configurations for every client. The application’s dates use the Asia/Tehran timezone. Its weather card concerns Qeshm Island, and the displayed tide value is a modeled estimate rather than navigation data.