Lific

io.github.VoidNullable由 GitHub 账号 VoidNullable 发布v2.11.1更新于 Oct 24, 2026

Local-first, lightweight issue tracker. Single binary, SQLite-backed, MCP-native.

已验证STDIO仅桌面效率与工作流知识与记忆开发者工具

概览

AI 生成的概览

Lific 是一个本地优先、以 SQLite 为存储的问题跟踪器，其 MCP 工具让助手跨会话管理问题、计划、页面、评论和附件。

可以做什么
Lific 把项目、问题、计划和页面存放在单个 SQLite 文件中，并通过 31 个 MCP 工具提供给助手。工具涵盖问题（列表、获取、创建、更新、批量更新、编辑、看板）、关系与等待、页面、计划、评论、附件、搜索与历史、结构以及导出。助手可用 get_briefing 恢复项目上下文，查找可执行的问题，创建嵌套步骤计划，把问题关联到人员或时间窗口，并在关闭问题时附上验证证据。每个 AI 工具以用户账号下独立的机器人身份连接，历史记录会显示是哪个工具做了改动。
适用场景
适合一个人指挥多个助手、并希望计划和问题存放在服务器而不是上下文窗口中的场景，使工作成果不随会话结束而消失。它面向小型自托管使用；README 说明它不适合需要 SSO、冲刺或甘特图的大型团队，不适合把问题存放在仓库本身，也不适合多台服务器互相同步。
运行要求
以本地进程通过 stdio 运行，可用 cargo 安装或下载二进制文件；不需要 Docker 或 Postgres。初始化运行 lific init，创建配置、数据库、管理员账号和监听 3456 端口的后台服务，随后 lific connect 为支持的客户端写入 MCP 配置。远程 Streamable HTTP 方式使用 Authorization Bearer API 密钥，密钥由 lific key create 创建；不带 LIFIC_TOKEN 的 stdio 会话以实例操作员身份运行。使用 Docker 时首次启动需要 LIFIC_INIT_ADMIN_NAME 和 LIFIC_INIT_ADMIN_PASSWORD。
安装前请注意
不带 LIFIC_TOKEN 的 stdio 会话以实例操作员身份运行，该模式下访问基本不受限制。HTTP 端点使用 Authorization Bearer API 密钥，Docker 首次启动需要 LIFIC_INIT_ADMIN_NAME 和 LIFIC_INIT_ADMIN_PASSWORD。工具可以创建、更新、批量更新、编辑和删除问题、页面、评论与资源，并可上传附件。Web UI 监听 localhost:3456；在对外暴露之前应设置 server.public_url。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Lific，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

[Lific: an issue tracker for prolific agents]

[CI] [crates.io] [Release] [License] [Discord]

An issue tracker for prolific agents.
One binary. One SQLite file. MCP built in.

lific.dev  ·  Docs  ·  Discord

Plans and issues live on your server instead of in the context window, so work outlives the session. Agents use it over MCP; you use the web UI.

  • 31 MCP tools in 5,781 tokens, about one long file read.
  • One 25 to 32 MB binary with SQLite, the web UI and backups built in. No Docker, no Postgres.
  • lific connect writes MCP config for 11 AI clients.
  • Identifiers like APP-42, never UUIDs.

60-second setup

bash
cargo install lific   # or Homebrew (below), or download a binary from Releaseslific init            # config, database, admin account, background service on :3456lific connect         # MCP config for your AI clients

Restart your AI client. The web UI is at http://localhost:3456. lific doctor checks config, database, server and an MCP round trip, and exits nonzero if anything is broken.

  • brew install voidnullable/tap/lific replaces cargo install on macOS and Linux: a release binary in seconds, no Rust toolchain.
  • lific init --here keeps config and database in the current directory.
  • lific init --no-service skips the background service; run lific start yourself.
  • lific service status | restart | stop | uninstall manages the service.

More: Installation · Quickstart

What your agent can do

CallWhat it does
get_briefing(project="APP")Resume a project: plans and next steps, blocked and workable issues, and with since, what changed
list_issues(project="APP", workable=true)Open issues whose blockers are all resolved
list_issues(members=["me"])Your active work across the projects you belong to
create_plan / get_planNested step plans that survive the session; a step and its issue close together
link_issues(target="APP-9", relation_type="blocks", user="ada")Block an issue on a person or a date window, not only another issue
update_issue(assignees=["human"])Mark work a person must do; agents take unassigned issues
update_issue(status="done", evidence="cargo test: 412 passed")Close with the proof saved as a verification comment
edit_issue / edit_pageChange one string without resending the document
get_activity(identifier="APP", since="2026-10-01")Who changed what while you were away

Each AI tool connects as its own bot under your account. The history says "OpenCode closed APP-42", and you can revoke one tool without touching the others.

MCP tools

FamilyTools
Issueslist_issues · get_issue · create_issue · update_issue · bulk_update · edit_issue · get_board
Relations and waitslink_issues · unlink_issues
Pagesget_page · create_page · update_page · edit_page
Planscreate_plan · get_plan · edit_plan_step · update_plan_step
Commentsadd_comment · list_comments · edit_comment · delete_comment
Attachmentsupload_attachment · get_attachment · list_attachments
Search and historyget_briefing · search · get_activity
Structurelist_resources · manage_resource · delete
Exportexport

The 5,781 tokens are the tools/list definitions as compact JSON, counted with tiktoken's o200k_base. Parameters and output: MCP tools.

Connect your AI tools

lific connect supports opencode · claude-code · claude-desktop · cursor · vscode · codex · zed · gemini · windsurf · goose · crush.

bash
lific connect                                          # pick from the clients it findslific connect --client opencode --client cursor --yes  # no promptslific connect --client claude-code --scope project     # repo-local .mcp.jsonlific connect --client zed --stdio                     # no server: direct SQLite over stdio

It merges into existing config, and leaves a file it can't parse alone and prints the snippet instead. OAuth sign-in from the client and lific login for headless machines also work: Connect agents.

Manual config for any MCP client

Remote, over Streamable HTTP:

json
{  "lific": {    "type": "remote",    "url": "http://localhost:3456/mcp",    "headers": { "Authorization": "Bearer your-api-key" }  }}

Local, over stdio with no server:

json
{  "lific": {    "type": "local",    "command": ["lific", "--db", "path/to/lific.db", "mcp"]  }}

Create a key with lific key create --name my-key --user <you>. A stdio session without LIFIC_TOKEN acts as the instance operator.

CLI

bash
lific issue list --project APPlific issue create --project APP --title "Fix login bug" --priority highlific issue update APP-42 --status donelific search "authentication" --project APPlific --backend http --url https://lific.example.com issue list --project APP   # after lific login

The CLI reads the database directly, or a remote server with --backend http. Output is JSON when piped. lific agents-md adds a short Lific section to a repo's AGENTS.md. Full reference: CLI.

When Lific is the wrong tool

  • You coordinate a large team and need SSO, sprints or Gantt charts. Use Linear or Plane.
  • You want issues stored in the repo itself. Use a git-native tracker such as beads.
  • You need several servers syncing with each other. One Lific instance is one SQLite file.

It's built for one person directing several agents.

Running it

Access. New installs check project membership on every call, reads included. Add people with lific member add --project APP --user sam --role maintainer. See Self-hosting.

Backups. Lific writes an archive every hour and keeps 24. For a one-off:

bash
lific dump                                    # database plus attachments, safe while runninglific restore lific_20260703_141500.tar.gz    # stop the server first

Config. lific init writes lific.toml. Set server.public_url before exposing the server beyond localhost. See Configuration.

Docker. Optional; the binary needs nothing else.

bash
docker build -t lific .docker run -p 3456:3456 -v lific-data:/data \  -e LIFIC_INIT_ADMIN_NAME="Your Name" \  -e LIFIC_INIT_ADMIN_PASSWORD="a long password" \  lific

Both variables are required on first boot and ignored after it.

Upgrading. Read Upgrading before you skip versions.

Build from source

bash
git clone https://github.com/VoidNullable/lific && cd lificdevenv allow && devenv shelldevenv tasks run lific:debug-build

CONTRIBUTING.md covers tests and release builds.

Community

Questions, bug reports and release announcements: Discord. Support questions get answered fastest in #support.

Contributing

Issues and PRs welcome. For anything large, open an issue first.

MCP Registry

Lific publishes server.json to the MCP Registry.

  • mcp-name: io.github.VoidNullable/lific

License

Apache-2.0

来源：README.md，提交 7526f40

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

4
  1. v2.11.1最新Oct 14, 2026
  2. v2.11.0Oct 13, 2026
  3. v2.10.0Sep 23, 2026
  4. v2.9.0Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分