lighterpack-mcp

An MCP server that lets AI agents create and manage LighterPack packing lists — add gear, track weights, organize categories, and share lists, all through natural conversation.

Unofficial. This project is not affiliated with or endorsed by LighterPack. It talks to LighterPack's own web API (the same one lighterpack.com's browser client uses) — see Architecture below.

What is this?

LighterPack is a free tool backpackers and travelers use to plan and share packing lists — tracking item weights, prices, and categories to optimize what they bring. This MCP server exposes LighterPack's list/category/item model as ~35 tools, so an MCP-compatible AI agent (Claude Desktop, Claude Code, etc.) can build and edit packing lists on your behalf: "Create a 3-day backpacking list with a Shelter category containing my tent and rain jacket, mark the jacket as worn, and give me a share link."

Related MCP server: Jilebi

Quick start

Requires Node.js ≥20 and a LighterPack account.

npx @paladini/lighterpack-mcp

Add it to your MCP client's config (example for Claude Desktop, claude_desktop_config.json):

{
  "mcpServers": {
    "lighterpack": {
      "command": "npx",
      "args": ["-y", "@paladini/lighterpack-mcp"],
      "env": {
        "LIGHTERPACK_USERNAME": "your-username",
        "LIGHTERPACK_PASSWORD": "your-password"
      }
    }
  }
}

Configuration

One account per server instance — there's no tool to switch accounts mid-session, by design.

Tool reference

Weights are always in grams at the tool boundary (weight / weightUnit inputs, weightGrams outputs), regardless of what unit LighterPack's own UI happens to display. Internally LighterPack always stores weight in milligrams, so nothing is lost either way.

Library / account

Lists

Categories

Items

Item flags (per category placement)

Batch / composite

Deliberately out of scope: account registration/deletion, password/email changes, and password recovery — high-risk, low-value for an agent to hold.

Architecture

LighterPack has no granular REST API — there's no "create list" or "add item" endpoint. Instead, a user's entire library (every list, category, and item) is a single JSON document, synced via POST /saveLibrary with an optimistic-concurrency token (sync_token). That fetch → mutate → save cycle, the sync_token retry logic, and the business rules (worn/consumable exclusivity, id sequencing, shared items, etc. — ported from LighterPack's own open-source client) all live in @paladini/lighterpack, a standalone TypeScript SDK this server depends on. This repo is intentionally thin: src/tools/* just registers each MCP tool (Zod input schema + agent-facing description) and calls the corresponding SDK method (lp.lists.*, lp.categories.*, lp.items.*, lp.batch.*), returning the SDK's already-formatted view objects (weights in grams, computed totals, etc.) as the tool result.

Limitations

• No realtime push — if you (or someone else) edits the list on lighterpack.com while an agent session is open, call refresh_library to pick up the change.

• One LighterPack account per server instance.

• Account creation/deletion and credential changes are intentionally not exposed as tools.

Contributing

Contributions are welcome! See CONTRIBUTING.md for dev setup, testing, and how to add a new tool.

License

MIT