Skip to content
dizlexicPublic

About

A simple multiuser multiboard task MCP server managed via kanban board interface. Created to allow simple self hosted agent task management.

Topics

Resources

Stars

45 stars

Watchers

1 watching

Forks

Latest commit

Β 

History

214 Commits

Folders and files

Repository files navigation

Moo Tasks Logo

Moo Tasks

mootasks.dev

A kanban-style task management dashboard with an integrated MCP server.
Human users manage tasks via a drag-and-drop web UI, while AI agents connect via the MCP server to discover, accept, update, and create tasks programmatically.

Moo Tasks Workflow

Nuxt 4 Tailwind CSS v4 MySQL MCP MIT License


✨ Features

Feature Description
πŸ‘€ User Accounts Email/password registration and login with sealed cookie sessions
βš™οΈ Account Settings Manage global MCP tokens and user account information
πŸ“‹ Multiple Boards Create and manage multiple project boards with custom descriptions
πŸ“‹ Task Plans Create, manage, and apply task templates/plans to project boards
πŸ’Ύ Import/Export Import and export boards as JSON
πŸ‘₯ Board Collaboration Invite users by email, manage member roles (Owner/Member)
πŸ”„ 5-Column Kanban Workflow stages: Backlog β†’ To Do β†’ In Progress β†’ Review β†’ Done
πŸ”’ Sequential Task IDs Tasks have human-readable sequential IDs (e.g., #1, #2) per board
πŸ”€ Dual View Modes Toggle between visual Kanban Board and condensed Task List
πŸ–±οΈ Drag & Drop Intuitive task movement between columns using vuedraggable
πŸ”§ Correction Tasks Request specific fixes with linked child tasks for task refinement
πŸ€– MCP Server Per-board MCP endpoints with bearer token auth & Public/Private toggles
πŸ“ Configurable Instructions Global and per-board MCP instructions with "Reset to Default" support
πŸ“ Changelog Generation AI-powered generation of markdown changelogs from completed tasks
πŸ”— Task Deep-Linking Copy unique task URLs for direct navigation and easy sharing
⚑ Real-time Polling Automatic board sync to keep human and AI agent actions in sync
πŸ—„οΈ MySQL Persistence Reliable data storage with Drizzle ORM

Screenshots

Moo Tasks Workflow

Moo Tasks Workflow

Moo Tasks Workflow


πŸ’Ύ Board Management

  • Import Board: Available on the Dashboard page.
  • Export Board: Available in the Board Settings panel.

πŸš€ Quick Start

The quickest way to run a local instance is Docker Compose. This starts the app, MySQL, and development-only Adminer and Mailpit services.

🐳 Run locally with Docker Compose

Prerequisites: Docker Desktop or Docker Engine with the Compose v2 plugin.

git clone https://github.com/dizlexic/moo-agent-board.git
cd moo-agent-board
cp .env.example .env

Before starting, edit .env and replace NUXT_SESSION_PASSWORD, DB_ROOT_PASSWORD, and DB_PASSWORD with unique secrets. Generate a secret with openssl rand -hex 32; use a different value for each password. The session password must be at least 32 characters. The example database credentials are for local development onlyβ€”never expose them to the internet.

Start the stack:

docker compose up --build -d
docker compose logs -f app

The app is at http://localhost:3000. Register an account to create your first board. The container waits for MySQL and runs database migrations on startup; the first start can take a few minutes. Adminer (http://localhost:8080) and the Mailpit inbox (http://localhost:8025) are for local development only. To log into Adminer, select MySQL, use db as the server, and enter DB_USER and DB_PASSWORD from .env. Mailpit captures outgoing messages so you can inspect them without sending real email.

MySQL data is stored in the db-data Docker volume. docker compose down stops the services without removing data; docker compose down -v deletes the database volume and all its data.

πŸ› οΈ Run the app from source

For development, install Node.js v26.13.0 (see .nvmrc), npm, and MySQL 8. Copy .env.example to .env, configure the database connection and a 32-character-or-longer NUXT_SESSION_PASSWORD, then install dependencies with npm ci. Set DATABASE_URL to your MySQL connection string; npm run db:migrate applies migrations, and npm run dev starts the app. If using the Compose Mailpit service from your host, set SMTP_HOST=localhost and SMTP_PORT to MAILPIT_SMTP_PORT (default 1025).

πŸ“– Usage Guide

Get up and running in just a few minutes:

  1. Launch: Once the server is running, navigate to http://localhost:3000 (or the live site at mootasks.dev).
  2. Account: Register your account at /register or login.
  3. Create Board: Head to the Dashboard to create your first project board.
  4. Manage Tasks: Add, move, and update tasks on your new board using the drag-and-drop Kanban view or the list view.
  5. Connect AI: Go to Board Settings to view your MCP configuration and connect your favorite AI agent (e.g., Claude Code, Cursor, VS Code).
  6. Seed Data: Need test data? Run npx tsx server/db/seed.ts to populate the database with sample tasks.

βš™οΈ Environment Variables

Copy .env.example to .env and adjust for your environment. Compose supplies its own internal database URL and uses the db service name; when running the app directly on your host, use localhost and the published database port instead.

Variable Default Description
BASE_URL http://localhost:3000 Public app URL used in verification, password-reset, and invitation emails
HOST localhost in the example; Compose uses 0.0.0.0 Server bind address
PORT 3000 Server port
DB_ROOT_PASSWORD password MySQL root password for the Compose database; replace before deployment
DB_USER mootasks MySQL application user
DB_PASSWORD password MySQL application password; replace before deployment
DB_NAME mootasks MySQL database name
DB_HOST localhost MySQL host for local development; Compose connects to db internally
DB_PORT 3306 MySQL connection port for local development; Compose uses internal port 3306
DB_LOCAL_PORT 3307 Host port published by Compose for MySQL
DATABASE_URL (unset) MySQL connection string; required for migrations and takes precedence over individual database settings
DB_SSL (unset) Set to REQUIRED to enable TLS when connecting with individual database settings
NUXT_SESSION_PASSWORD (required) Unique secret of at least 32 characters for session cookies
SMTP_HOST mailpit SMTP server; use localhost when running the app directly on the host
SMTP_PORT 1025 SMTP server port
SMTP_USER / SMTP_PASSWORD (empty) SMTP credentials; not needed for Mailpit
SMTP_FROM noreply@localhost Sender address for outgoing email
ADMINER_PORT 8080 Host port published for Adminer
MAILPIT_UI_PORT 8025 Host port published for the Mailpit inbox
MAILPIT_SMTP_PORT 1025 Host port published for Mailpit SMTP

When running the app on the host against the Compose database, use DB_HOST=localhost and set DB_PORT to DB_LOCAL_PORT (default 3307). Set BASE_URL to the public origin and configure a real SMTP provider before sending email from a deployed instance. See Self-hosting and production setup before exposing an instance to the internet.


πŸ€– MCP Server

Moo Tasks is primarily an MCP server and Agent API. While it provides a web interface for humans, its core purpose is to enable AI agents to manage tasks programmatically.

🎯 Board-Scoped Architecture

Everything in Moo Tasks is scoped to a board. There are no global queries for tasks. This ensures that agents only work within the context they are assigned to, improving focus and security.

  • Each board has its own unique MCP endpoint.
  • AI agents connect to a specific board to work on its tasks.
  • Resources, prompts, and tools are all scoped to the active board.

πŸ“‹ Working with Tasks via MCP

The board acts as the primary task list for this application. To programmatically work on tasks:

  1. Get the MCP Token: In the Board Settings, generate an MCP token if the board is private.
  2. Configure Your Agent: Add the MCP server configuration for your specific board.
  3. Use Tools: Use the available tools (list-tasks, accept-task, update-task-status, etc.) to interact with the tasks.

πŸ” Security & Privacy

Mode Description
πŸ”’ Private (Default) Requires a token in the Authorization: Bearer <token> HTTP header
🌐 Public Allows access without a token (for local development)

Tokens can be generated, rotated, or revoked at any time from Board Settings.

πŸ› οΈ Tools

Tool Description
list-tasks List tasks with optional status/priority/limit filters
get-task Get full details of a task by ID
create-task Create a new task
update-task-status Update a task's status
accept-task Assign yourself to a task and move it to in_progress
reject-task Reject a task review and move it back to todo
add-comment Post progress notes or questions on a task
submit-for-review Mark a task ready for human review
request-corrections Create a linked correction task
generate-changelog Generate a markdown changelog from completed tasks
list-plans Discover available task plans/templates
apply-plan Apply a task plan to the board
create-board Create a new board (requires account token)
get-installation-instructions Get setup instructions

πŸ“š Resources

URI Description
moo-tasks://<boardId>/board-state Full board snapshot grouped by status
moo-tasks://<boardId>/agent-instructions Workflow instructions for agents

πŸ’¬ Prompts

Prompt Description
task-workflow Guided workflow for discovering and completing tasks

πŸ”„ Task Hierarchy & Corrections

Moo Tasks supports a refined workflow for task completion:

  • Review Status β€” Move tasks to "Review" when ready for human verification
  • Request Corrections β€” From "Review" or "Done", create linked "Correction Tasks"
  • Linked Navigation β€” Correction tasks link to their parent for easy navigation

Configurable Instructions

Level Description
🌍 Global Edit at /settings/instructions, applies to all boards by default
πŸ“‹ Per-Board Override in board settings, falls back to global when reset

Both support reset to default to restore the original built-in instructions.


πŸ”Œ MCP Client Configuration

Claude Code
{
  "mcpServers": {
    "moo-tasks": {
      "type": "streamable-http",
      "url": "http://localhost:3000/api/boards/<boardId>/mcp",
      "headers": {
        "Authorization": "Bearer <your-bearer-token>"
      }
    }
  }
}
Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "moo-tasks": {
      "type": "streamable-http",
      "url": "http://localhost:3000/api/boards/<boardId>/mcp",
      "headers": {
        "Authorization": "Bearer <your-bearer-token>"
      }
    }
  }
}
VS Code / JetBrains / generic MCP client

Add to your client's MCP config (e.g. .vscode/mcp.json or JetBrains MCP settings):

{
  "mcpServers": {
    "moo-tasks": {
      "type": "streamable-http",
      "url": "http://localhost:3000/api/boards/<boardId>/mcp",
      "headers": {
        "Authorization": "Bearer <your-bearer-token>"
      }
    }
  }
}

πŸ’‘ The board page has a πŸ“‹ Copy JSON button that emits this exact snippet pre-filled with your board ID and token.

πŸ” Security & Scoping

  • Each MCP endpoint is scoped to a single board (/api/boards/<boardId>/mcp). The server only ever sees tasks, comments, and instructions belonging to that one board.
  • Tokens are sent via the standard Authorization: Bearer <token> HTTP header per the MCP authorization spec. Query-string tokens are no longer accepted.
  • Generate or revoke a board's token from the board settings drawer at any time. Revoking immediately invalidates all existing agent connections.
  • Boards may also be marked mcpPublic in settings for read-friendly demos; in that mode no token is required, but it is not recommended for real work.

πŸ“‘ API Routes

Authentication
Method Route Purpose
POST /api/auth/register Register with email/password
POST /api/auth/login Login with email/password
Boards
Method Route Purpose
GET /api/boards List boards for current user
POST /api/boards Create a new board
GET /api/boards/:id Get board details
PATCH /api/boards/:id Update board (owner only)
DELETE /api/boards/:id Delete board (owner only)
Board Members
Method Route Purpose
GET /api/boards/:id/members List board members
POST /api/boards/:id/members Invite user by email
DELETE /api/boards/:id/members/:userId Remove member
Tasks
Method Route Purpose
GET /api/boards/:id/tasks List tasks for a board
POST /api/boards/:id/tasks Create a task in a board
GET /api/tasks/:id Get a single task
PATCH /api/tasks/:id Update task fields
DELETE /api/tasks/:id Delete a task
Instructions
Method Route Purpose
GET /api/instructions Get global instructions
PUT /api/instructions/:id Update global instruction
POST /api/instructions/:id/reset Reset to default
GET /api/boards/:id/instructions Get board instructions
PUT /api/boards/:id/instructions/:instructionId Update board instruction
POST /api/boards/:id/instructions/:instructionId/reset Reset board instruction

☁️ Deploy your own instance

The Compose stack above is for local use, not production: it publishes development tools and uses a local database volume. For a production checklist covering hosting, secrets, database, email, and migrations, see Self-hosting and production setup. A DigitalOcean App Platform example is available in .do/app.yaml; the GitHub Actions workflow only builds the project and does not deploy it.


🧱 Tech Stack

Technology Purpose
Nuxt 4 (Nitro + Vue 3) Framework
Tailwind CSS v4 Styling
MySQL + Drizzle ORM Database
nuxt-auth-utils Auth (sealed cookie sessions, scrypt hashing)
@modelcontextprotocol/sdk MCP server integration
vuedraggable Drag & drop
nanoid ID generation

Moo Tasks
Built with πŸ„ by dizlexic

About

A simple multiuser multiboard task MCP server managed via kanban board interface. Created to allow simple self hosted agent task management.

Topics

Resources

Stars

45 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors

Languages