# 0xtmm > Agent-first task manager. There is no web app — the only interface is an MCP > server your agent drives. Capture, prioritize, plan, journal, search, and > report on tasks entirely through MCP tool calls. Each user has an isolated > space; projects can be shared with others. ## Connect (MCP) - MCP endpoint (streamable HTTP): https://0xtmm.com/mcp - Auth: send `Authorization: Bearer ` on every request. - One-line install for Claude Code: `curl -fsSL https://0xtmm.com/install.sh | sh` ## Self-serve onboarding (no admin, no password) A token is obtained via an OAuth 2.0 device-authorization grant (RFC 8628) whose login step is an email magic link. The magic link proves email ownership and auto-creates the account on first use, so an agent can onboard a user on its own (fully autonomous if it has inbox access; otherwise a human clicks the link once): 1. `POST https://0xtmm.com/auth/device/start` → JSON `{ device_code, user_code, verification_uri, interval, expires_in, mcp_url }` 2. `POST https://0xtmm.com/auth/verify` with JSON `{ "code": "", "email": "" }` → emails a magic link to that address (`{ "status": "email_sent" }`) 3. The recipient opens the magic link to confirm — this creates the account and approves the device. 4. `POST https://0xtmm.com/auth/device/poll` with `device_code=` repeatedly (respect `interval` seconds). Returns `{ "status": "authorization_pending" }` until approved, then once `{ "status": "approved", "token": "tmm_…", "mcp_url": "…" }`. 5. Use `token` as the Bearer credential against `https://0xtmm.com/mcp`. The token is shown exactly once (step 4); store it securely. ## Tools The MCP server exposes (all scoped to the authenticated user): - Tasks: `add_task`, `list_tasks`, `search_tasks`, `update_task`, `complete_task`, `reopen_task`, `delete_task` - Views: `agenda` (ordered open tasks across projects), `completed` (date-ranged, with plan/outcome) - Projects: `list_projects`, `create_project`, `rename_project`, `delete_project` - Sharing: `share_project`, `unshare_project`, `list_members` (roles: owner, member, viewer) Tasks carry: title, priority (none|low|medium|high|urgent), due date, status (open|done), source (human|agent), a one-line note, a multi-line plan, and a multi-line outcome. `search_tasks` is ranked full-text over title/note/plan/outcome. List tools are paginated via `limit`/`offset` and return `has_more`/`next_offset`.