AI Skill Hub 推荐使用:本地问题跟踪器 是一款优质的MCP工具。AI 综合评分 7.5 分,在同类工具中表现稳健。如果你正在寻找可靠的MCP工具解决方案,这是一个值得深入了解的选择。
轻量级、单文件的MCP工具,支持SQLite
本地问题跟踪器 是一款遵循 MCP(Model Context Protocol)标准协议的 AI 工具扩展。通过 MCP 协议,它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务,实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用,都可以通过自然语言在 AI 对话中直接触发,极大提升生产效率。
轻量级、单文件的MCP工具,支持SQLite
本地问题跟踪器 是一款遵循 MCP(Model Context Protocol)标准协议的 AI 工具扩展。通过 MCP 协议,它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务,实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用,都可以通过自然语言在 AI 对话中直接触发,极大提升生产效率。
# 方式一:通过 Claude Code CLI 一键安装
claude skill install https://github.com/VoidNullable/lific
# 方式二:手动配置 claude_desktop_config.json
{
"mcpServers": {
"-------": {
"command": "npx",
"args": ["-y", "lific"]
}
}
}
# 配置文件位置
# macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
# Windows: %APPDATA%/Claude/claude_desktop_config.json
# 安装后在 Claude 对话中直接使用 # 示例: 用户: 请帮我用 本地问题跟踪器 执行以下任务... Claude: [自动调用 本地问题跟踪器 MCP 工具处理请求] # 查看可用工具列表 # 在 Claude 中输入:"列出所有可用的 MCP 工具"
// claude_desktop_config.json 配置示例
{
"mcpServers": {
"_______": {
"command": "npx",
"args": ["-y", "lific"],
"env": {
// "API_KEY": "your-api-key-here"
}
}
}
}
// 保存后重启 Claude Desktop 生效
<p align="center"> <img src="LificHero.png" alt="Lific Issue tracking built for AI-driven development" width="800"> </p>
<p align="center"> <a href="https://github.com/VoidNullable/lific/actions/workflows/ci.yml"><img src="https://github.com/VoidNullable/lific/actions/workflows/ci.yml/badge.svg" alt="CI"></a> <a href="https://crates.io/crates/lific"><img src="https://img.shields.io/crates/v/lific" alt="crates.io"></a> <a href="https://github.com/VoidNullable/lific/releases"><img src="https://img.shields.io/github/v/release/VoidNullable/lific" alt="Release"></a> <a href="LICENSE"><img src="https://img.shields.io/github/license/VoidNullable/lific" alt="License"></a> </p>
<p align="center"> <strong>Lightweight issue tracking built for AI-driven development.</strong><br> Single binary. MCP built in. Clean web UI. </p>
---
Lific's full MCP schema fits in roughly 3,000 tokens. It uses human-readable identifiers (APP-42, not UUIDs), runs as a single binary with an embedded SQLite database, and includes a web UI for when you want to look at things yourself.
| Category | What you get |
|---|---|
| **Issue tracking** | Status, priority, modules with icons, labels, relations, comments, board view, fuzzy search, sort by recent activity |
| **Documentation** | Markdown pages in recursive folders, with comments, labels, lifecycle status, full-text search, and Mermaid diagrams |
| **MCP interface** | 21 tools, ~3,000-token schema, human-readable identifiers |
| **REST API** | Full CRUD for all resources, search, board view |
| **Web UI** | Markdown editing with live preview, drag-and-drop board, Mermaid and code-copy, dark/light theme |
| **User accounts** | Individual auth, per-tool bot identities, project lead permissions |
| **OAuth 2.1** | PKCE, dynamic client registration, token revocation, per-user token identity |
| **Backups** | Automatic SQLite snapshots with configurable retention |
| **CLI** | Full CRUD for issues, projects, pages, modules, labels, folders. No server needed |
| **Single binary** | No runtime dependencies, embedded SQLite, ~16MB |
SQLite is bundled via rusqlite and compiled into the binary. No system SQLite required.
cargo install lific
Or grab a binary from the releases page.
git clone https://github.com/VoidNullable/lific
cd lific
mkdir -p web/dist
cargo build --release
The mkdir -p web/dist creates the empty directory that rust-embed expects at compile time. The resulting binary has full functionality (MCP, REST API, CLI, OAuth, backups) but visiting the web UI will return a message pointing you to build the frontend.
git clone https://github.com/VoidNullable/lific
cd lific
cd web && bun install && bun run build && cd ..
cargo build --release
The frontend is a Svelte 5 SPA built with Vite. bun run build outputs static files to web/dist/, which cargo build embeds into the binary. The final binary is fully self-contained with no runtime dependencies.
lific init # creates lific.toml + lific.db
lific start # starts on port 3456
On first run, Lific generates an API key and prints it to the console. It won't be shown again. This key is used for MCP and API access.
Open http://localhost:3456 to use the web UI. The first account you create is the admin.
The CLI also works directly against the database. No server or auth required:
lific project list
lific issue list --project APP
lific issue create --project APP --title "Fix login bug" --priority high
lific issue get APP-42
lific issue update APP-42 --status done
lific search "authentication" --project APP
Add --json to any command for machine-readable output.
<details> <summary><code>lific.toml</code></summary>
lific init generates this:
[server]
host = "0.0.0.0"
port = 3456
[database]
path = "lific.db"
[backup]
enabled = true
dir = "backups"
interval_minutes = 60
retain = 24
[log]
level = "info"
CLI flags (--db, --port, --host) override config values.
</details>
轻量级、易用的MCP工具
AI Skill Hub 为第三方内容聚合平台,本页面信息基于公开数据整理,不对工具功能和质量作任何法律背书。
建议在沙箱或测试环境中充分验证后,再部署至生产环境,并做好必要的安全评估。
✅ Apache 2.0 — 宽松开源协议,可商用,需保留版权声明和 NOTICE 文件,含专利授权条款。
总体来看,本地问题跟踪器 是一款质量良好的MCP工具,在同类工具中具备一定竞争力。AI Skill Hub 将持续追踪其更新动态,建议收藏备用,结合自身场景选择合适时机引入使用。
| 原始名称 | lific |
| 原始描述 | 开源MCP工具:Local-first, lightweight issue tracker. Single Rust binary, SQLite-backed, MCP-n。⭐7 · Rust |
| Topics | issue_trackerrustsqlite |
| GitHub | https://github.com/VoidNullable/lific |
| License | Apache-2.0 |
| 语言 | Rust |
收录时间:2026-05-26 · 更新时间:2026-05-30 · License:Apache-2.0 · AI Skill Hub 不对第三方内容的准确性作法律背书。
选择 Agent 类型,复制安装指令后粘贴到对应客户端