# Lific > A free, self-hosted issue tracker built for coding agents. Single Rust binary, SQLite storage, a built-in MCP server with 31 tools, REST API, CLI, and web UI. Full documentation content: https://lific.dev/llms-full.txt Comparison with other MCP issue trackers (beads, Vikunja, Gitea, Plane, Linear): https://lific.dev/compare # Docs - **Get started** - [Introduction](/docs): What Lific is, how its interfaces share one database, and which page to read first for your goal. - [Installation](/docs/installation): Get the lific binary from a GitHub release, from crates.io with Cargo, or by building the source tree. - [Quickstart](/docs/quickstart): Create a Lific instance on your machine, sign in, connect your AI tools, and create a first project and issue. - [Connect agents](/docs/connect): lific connect detects installed AI tools and writes MCP configuration for them. - [Windows](/docs/windows): Run Lific natively on Windows, where lific init installs a per-user background service that starts at sign-in, or use the Linux binary under WSL 2. - **Guides** - [Web UI guide](/docs/web-ui): How to triage issues, edit them, write pages, run plans, handle files and change settings in the Lific browser app. - [Self-hosting](/docs/self-hosting): Run Lific for a team: sign-in mode, the server process, reverse proxies and TLS, accounts, backups, and day-to-day operation. - [Repository bindings](/docs/repository-bindings): Tie a git checkout to a Lific project so agents working in it find their project without being told, locally or against a remote server. - [Git hooks](/docs/git-hooks): Close issues from commit messages with lific git-hook, locally or in CI, and tell a repository's agents about Lific with lific agents-md. - [Public projects](/docs/public-projects): Publish one project's current issues, pages, comments and files for anyone to read without an account, and know what stays private. - [Project archives](/docs/project-archives): Move one project to another Lific instance with its content, files and history, then check the new private copy before switching over. - [Archiving projects](/docs/archiving-projects): Take a project you no longer use out of Lific without losing it, then bring it back later with its members and history. - [Upgrade from 2.0 through 2.10](/docs/upgrading): Back up a Lific 2.x instance, read the notes for each newer version, replace the binary, and check the result, with release notes from 2.10 back to 2.1. - **Concepts** - Concepts - [Concepts](/docs/concepts): A map of Lific's data model, the identifiers that name each piece, who can change what, and what happens when something is deleted. - [Projects](/docs/concepts/projects): What a project holds, how its identifier is built, what each member role can do, and what deleting a project destroys. - [Issues](/docs/concepts/issues): What an issue holds, what Lific does with each status, how blockers decide which work is ready, and what happens when an issue is deleted. - [Modules and labels](/docs/concepts/modules-and-labels): How modules divide a project into areas and labels tag issues and pages, what each status and field does, and what deleting or merging them changes. - [Pages](/docs/concepts/pages): Project and workspace pages, folders, what each page status does, labels and pinning, and what happens when a page is deleted. - [Plans](/docs/concepts/plans): Nested step trees for multi-session work, how step ids differ from positions, and exactly when a step and its mirrored issue update each other. - [Comments and activity](/docs/concepts/comments-and-activity): How comments are identified, linked, mentioned, edited and deleted, how to read a long thread, and what the activity log records. - [Attachments](/docs/concepts/attachments): How uploaded files are stored beside the database, how Markdown references link them to issues, pages and comments, who can read them, and when they are removed. - **Reference** - MCP - [MCP](/docs/mcp): How an MCP client reaches Lific, how each transport authenticates, and the response conventions every tool shares. - [Working with Lific as an agent](/docs/mcp/agents): Conventions for an MCP client using Lific: resuming with a briefing, identifiers, triaging workable and waiting issues, closing with evidence, edit versus update, long pages, plans, paging, errors and attribution. - [Multi-instance MCP](/docs/mcp/multi-instance): Route one agent connection to named Lific servers, with separate credentials and explicit write destinations. - [MCP tools](/docs/mcp/tools): Every MCP tool Lific exposes, with each parameter, its default and its limits. - REST API - [REST API](/docs/rest-api): How to get a token and make a first call, what each credential and role may do, and how errors, edit conflicts and paging behave across Lific's HTTP API. - [Accounts and access](/docs/rest-api/identity): Instance settings, signing in and out, sessions, API keys, connected tools and user administration over REST. - [Projects](/docs/rest-api/projects): Create and configure projects, publish them, manage members and roles, arrange your sidebar, keep saved views, read the board and insights, and import from GitHub. - [Issues, pages and plans](/docs/rest-api/work): Create, update, link, delete and restore issues; park issues on a person or a date; write comments; manage pages, plans, modules, labels and folders; read each item's activity. - [Attachments](/docs/rest-api/attachments): Upload files, link them to issues, pages and comments, download them with thumbnails and previews, and list a project's files and pending cleanups. - [Search, sync and realtime](/docs/rest-api/sync): Search across projects, keep a local copy of a project current with the index and changes endpoints, and listen for updates on the realtime WebSocket. - [Exports and archives](/docs/rest-api/export): Download issues, pages and projects as Markdown, JSON or ZIP, and move a whole project between instances as an archive. - [Repositories and commits](/docs/rest-api/repositories): Bind git repositories to projects so tools can find the right project from a checkout, and close issues from commit messages in CI. - [Public read API](/docs/rest-api/public): The anonymous, read-only routes that serve a published project, what they leave out, and the limits that protect the instance from them. - [OAuth and discovery](/docs/rest-api/oauth): The OAuth 2.1 routes Lific serves for MCP clients and the CLI, including discovery metadata, client registration, browser approval, device login, tokens and revocation. - [CLI reference](/docs/cli): Every lific command and flag, grouped by what you are trying to do, and how each command reaches your data. - [Configuration](/docs/configuration): Where Lific looks for lific.toml, what every setting does and its default, and the environment variables Lific reads. - [Limits](/docs/limits): Every fixed limit in Lific that a person, script or agent can run into, what it applies to, and what happens when it is exceeded.