Skip to content
MCP server

Lific

Self-hosted, SQLite-backed issue tracker that coding agents drive over MCP

Runs locallyStatus and history
Install
Pricing
Open source
Platforms
Linux, macOS, Windows
Runs
Locally
Version
2.11.1
Listing updated
2 days ago

About Lific

Lific is an open-source MCP server for developer tools. It runs locally on your machine and is started by your AI client.

Lific keeps plans and issues on your own server so work outlives a single agent session. It ships as one binary with the web UI and backups included, and uses human-friendly identifiers like APP-42 rather than UUIDs. lific init sets up config, the database, an admin account and a background service on port 3456, and lific connect writes MCP configuration for eleven AI clients, including Claude Code, Cursor, Codex, Zed and Gemini.

Some calls are built for resuming work: get_briefing shows what changed since the last briefing, and list_issues with workable=true returns only issues whose blockers are resolved. Issues can be blocked on a person or a date window, and closing one with evidence stores a verification comment. Edit tools change one string without resending the whole document.

Each AI tool connects as its own bot under your account, so history reads like a named actor closed an issue and one tool can be revoked without affecting the rest. Project roles are Lead, Maintainer and Viewer.

Install

Run in a terminal

claude mcp add lific -- npx -y lific

Add to claude_desktop_config.json

{
  "mcpServers": {
    "lific": {
      "command": "npx",
      "args": [
        "-y",
        "lific"
      ]
    }
  }
}
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "lific": {
      "command": "npx",
      "args": [
        "-y",
        "lific"
      ]
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "lific": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "lific"
      ]
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "lific": {
      "command": "npx",
      "args": [
        "-y",
        "lific"
      ]
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "lific": {
      "command": "npx",
      "args": [
        "-y",
        "lific"
      ]
    }
  }
}

Tools this server provides (32)

Taken from the project documentation; the running server may differ.

list_issues
Lists issues, optionally only workable ones.
get_issue
Reads an issue.
create_issue
Creates an issue.
update_issue
Updates an issue, including status and evidence.
move_issue
Moves an issue.
bulk_update
Updates several issues.
edit_issue
Changes one string in a description.
get_board
Reads a board.
link_issues
Links issues or blocks one on a person or date.
unlink_issues
Removes a link.
get_page
Reads a page.
create_page
Creates a page.
update_page
Updates a page.
edit_page
Changes one string in a page.
create_plan
Creates a step plan.
get_plan
Reads a plan.
edit_plan_step
Edits a plan step.
update_plan_step
Updates a plan step.
add_comment
Adds a comment.
list_comments
Lists comments.
edit_comment
Edits a comment.
delete_comment
Deletes a comment.
upload_attachment
Uploads an attachment.
get_attachment
Reads an attachment.
list_attachments
Lists attachments.
get_briefing
Summarises what changed since the last briefing.
search
Searches the project.
get_activity
Shows who changed what.
list_resources
Lists resources.
manage_resource
Manages a resource.
delete
Deletes an item.
export
Exports data.

What it does

Resume with a briefing
get_briefing summarises changes, plans, blocked and workable issues.
Plans that persist
Nested step plans survive the session and close with their issue.
Evidence on close
Closing an issue can attach proof as a verification comment.
Per-tool identities
Each connected AI client acts as its own revocable bot.
Small string edits
edit_issue and edit_page replace one string without resending the document.
Single binary
One executable with SQLite, web UI and backups; no Docker or Postgres.

Good for

  • Track agent work across coding sessions
  • Mark tasks only a human can do
  • Review who changed what while you were away
  • Plan a project in nested steps that agents tick off

Pricing

Open source

Free and open source.

Prices change. Check lific.dev before you buy.

Lific FAQ

How do I install it?

Via cargo, Homebrew or winget, or a static binary from the releases page.

Which AI clients can it configure?

Eleven, including opencode, claude-code, claude-desktop, cursor, vscode, codex, zed, gemini, windsurf, goose and crush.

Does it need a database server?

No. It uses a single SQLite file.

What roles exist?

Lead, Maintainer and Viewer.

Is Lific free?

Yes. Lific is open source, so you can use and self-host it for free.

How do I add Lific to Claude Code?

Run this command in your terminal: claude mcp add lific -- npx -y lific

What are the best alternatives to Lific?

The closest alternatives to Lific are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.

Alternatives to Lific

  1. REA

    MCP server

    CLI and MCP server that lets coding agents reverse engineer apps and binaries

    Runs locally
    • Open source
    • 464K GitHub stars
    • Developer tools
  2. Codebase Memory

    MCP server

    Local MCP server that builds a code knowledge graph for AI coding agents

    Runs locally
    • Open source
    • 48.7K GitHub stars
    • Knowledge and memory
  3. GitHub

    MCP server

    Official MCP server connecting AI assistants to GitHub repos, issues and workflows

    Not checked yet
    • Remote
    • Open source
    • 34.5K GitHub stars
    • Developer tools
  4. MCP toolkit giving coding agents symbol-level code retrieval and editing

    Runs locally
    • Open source
    • 31.5K GitHub stars
    • Developer tools
  5. XERJ

    MCP server

    Local search engine for AI agents with cited answers over your code and docs

    Runs locally
    • Open source
    • 19.2K GitHub stars
    • Knowledge and memory
  6. Ha MCP

    MCP server

    MCP server for managing and automating Home Assistant from AI assistants

    Runs locally
    • 8 tools
    • Open source
    • 7.9K GitHub stars
    • Productivity