Lemin-kanban

Lemin Kanban is a production-grade Kanban board application built with Next.js 16, TypeScript, and SQLite. As an MCP server, it exposes a robust API layer and a rich UI for managing multiple boards, columns, and cards, with features like board sharing, role-based access, subtasks, labels, attachments, and real-time updates via SSE. The server supports OAuth 2.1 for secure authentication and offers a suite of 24 CRUD tools for managing boards, columns, cards, subtasks, activities, label colors, and archive/restore operations. To get started, run the server and connect to its API endpoints from your client or integration scripts. The app includes a detailed docs section at /docs/mcp for setup and usage guidance.

Prerequisites:

• Node.js (LTS) and npm or pnpm
• SQLite or compatible database (the app uses SQLite by default)

1. Clone the repository:

git clone https://github.com/your-org/leminkanban.git
cd leminkanban

2. Install dependencies:

npm install

3. Configure the environment:

• Create a SQLite database file or provide a DATABASE_URL to your preferred SQLite file.
• Optionally set PORT and other app-specific environment variables.

4. Run the development/production server:

# Development
npm run dev

# Production (build and start)
npm run build
npm start

5. Access the app:

• UI: http://localhost:3000
• API/docs: /docs/mcp

Notes:

• If you are deploying to a hosting environment, ensure the port and database path are correctly configured via environment variables.
• For production, consider configuring a reverse proxy and enabling TLS termination.

Tips and common considerations:

• The app uses SQLite as its database by default; ensure the database file is writable by the process.
• Enable SSE auto-reconnect and live updates in your client to take advantage of real-time board changes.
• When sharing boards, assign appropriate roles (Owner, Admin, Editor, Viewer) to control access.
• If you encounter authentication issues, verify the OAuth configuration (redirect URIs, client registrations) as per the MCP documentation at /docs/mcp.
• For deployment, monitor server restarts and utilize the Deploy Notification feature to minimize user disruption during maintenance.
• Environment variables can be extended as needed; keep sensitive data secured and use secret management where possible.