# Life OS

Life OS is a workspace platform exposed to agents as an MCP server. It gives
you tools for messaging, CRM, knowledge, files, automations and connected
devices, and it holds the credentials for them so you never handle a secret.

## Connect

MCP endpoint: https://mcp.archik.tech/mcp
Transport: streamable HTTP.

Authorization is OAuth 2.1 with dynamic client registration, so you do not
need a client id in advance. Request the endpoint, read the 401, register
yourself at the authorization server it names, then show the authorization
URL to your user and wait. They will pick, in a browser, which workspaces you
may use and which tool profile you get in each.

For Claude Code:

    claude mcp add --transport http lifeos https://mcp.archik.tech/mcp

Then run /mcp and follow the login.

## After connecting

Call platform_whoami first. It tells you which workspace you are in, your
role, and which connection you are using. Do not assume: an authorization may
cover several workspaces, and the tools you see are only those your user
selected.

Tool names are namespaced by module, for example telegram_get_history or
knowledge_search. The set you receive is the whole set you have; there is no
hidden capability to ask for. If a tool you need is missing, ask your user to
add it to your tool profile -- it appears in your next session, with no
reconnection.

If you have the devices_ tools, the workspace has real computers attached.
Call devices_list first and devices_describe before running anything: the
allowed commands differ per machine and per access level, and the answer is
readable rather than guessable. Commands are argv arrays and there is no
shell. A refusal is a boundary a person set, not an obstacle to work around.

## Rules that matter

You never receive tokens, passwords or sessions. You call a tool with a
connection id and Life OS supplies the credentials on the server. If a tool
returns something that looks like a secret, treat it as a mistake and report
it rather than storing it.

Destructive tools are marked as such. Some require an explicit human approval
that Life OS requests on its own; do not try to route around a pending
approval.

An authorization can be revoked by your user at any moment. Losing access
mid-task is normal and is not an error to retry around.

## Full documentation

https://docs.archik.tech/agents/self-connect  connecting yourself
https://docs.archik.tech/connections/from-your-service  connecting accounts
    on behalf of your own users
https://docs.archik.tech/  everything else
https://docs.archik.tech/llms-full.txt  the documentation as one text file