convez.ai
MCP ServerAutomaçãoIntermediário
dizlexic

Moo Tasks

dizlexic/moo-tasks

Kanban multiusuário com MCP server integrado para colaboração humano-IA

Ver no GitHub
BomPluginScore · de 0 a 100

Servidor MCP com dashboard kanban para gerenciamento colaborativo de tarefas. Humanos gerenciam tarefas via interface web com drag-and-drop, enquanto agentes IA conectam via MCP para descobrir, aceitar, atualizar e criar tarefas programaticamente. Inclui suporte multi-usuário, múltiplos boards, templates de tarefas e sincronização em tempo real.

Instalação

$npx convez-ai dizlexic/moo-tasks

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
45
Forks
3
Acompanhando
1
Saúde
42%
Último commit
há 2 semanas
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Gerenciar tarefas de agentes IA em projetos self-hosted
  • Coordenar workflows entre usuários humanos e agentes autônomos
  • Implementar sistema de task management com interface visual e API programática

Veredito

Solução bem arquitetada que resolve um problema real: orquestração de tarefas entre humanos e agentes IA com interface acessível. Stack moderno (Nuxt 4, MySQL, MCP) e features práticas como multi-board, templates e changelog automático. Adequado para quem quer self-hosted task management com suporte nativo a agentes.

README

A tradução para o português deste README ainda está na fila.


✨ Features

FeatureDescription
👤User AccountsEmail/password registration and login with sealed cookie sessions
⚙️Account SettingsManage global MCP tokens and user account information
📋Multiple BoardsCreate and manage multiple project boards with custom descriptions
📋Task PlansCreate, manage, and apply task templates/plans to project boards
💾Import/ExportImport and export boards as JSON
👥Board CollaborationInvite users by email, manage member roles (Owner/Member)
🔄5-Column KanbanWorkflow stages: Backlog → To Do → In Progress → Review → Done
🔢Sequential Task IDsTasks have human-readable sequential IDs (e.g., #1, #2) per board
🔀Dual View ModesToggle between visual Kanban Board and condensed Task List
🖱️Drag & DropIntuitive task movement between columns using vuedraggable
🔧Correction TasksRequest specific fixes with linked child tasks for task refinement
🤖MCP ServerPer-board MCP endpoints with bearer token auth & Public/Private toggles
📝Configurable InstructionsGlobal and per-board MCP instructions with "Reset to Default" support
📝Changelog GenerationAI-powered generation of markdown changelogs from completed tasks
🔗Task Deep-LinkingCopy unique task URLs for direct navigation and easy sharing
⚡Real-time PollingAutomatic board sync to keep human and AI agent actions in sync
🗄️MySQL PersistenceReliable data storage with Drizzle ORM

Screenshots


💾 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.

VariableDefaultDescription
BASE_URLhttp://localhost:3000Public app URL used in verification, password-reset, and invitation emails
HOSTlocalhost in the example; Compose uses 0.0.0.0Server bind address
PORT3000Server port
DB_ROOT_PASSWORDpasswordMySQL root password for the Compose database; replace before deployment
DB_USERmootasksMySQL application user
DB_PASSWORDpasswordMySQL application password; replace before deployment
DB_NAMEmootasksMySQL database name
DB_HOSTlocalhostMySQL host for local development; Compose connects to db internally
DB_PORT3306MySQL connection port for local development; Compose uses internal port 3306
DB_LOCAL_PORT3307Host 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_HOSTmailpitSMTP server; use localhost when running the app directly on the host
SMTP_PORT1025SMTP server port
SMTP_USER / SMTP_PASSWORD(empty)SMTP credentials; not needed for Mailpit
SMTP_FROMnoreply@localhostSender address for outgoing email
ADMINER_PORT8080Host port published for Adminer
MAILPIT_UI_PORT8025Host port published for the Mailpit inbox
MAILPIT_SMTP_PORT1025Host 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

ModeDescription
🔒 Private (Default)Requires a token in the Authorization: Bearer <token> HTTP header
🌐 PublicAllows access without a token (for local development)

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

🛠️ Tools

ToolDescription
list-tasksList tasks with optional status/priority/limit filters
get-taskGet full details of a task by ID
create-taskCreate a new task
update-task-statusUpdate a task's status
accept-taskAssign yourself to a task and move it to in_progress
reject-taskReject a task review and move it back to todo
add-commentPost progress notes or questions on a task
submit-for-reviewMark a task ready for human review
request-correctionsCreate a linked correction task
generate-changelogGenerate a markdown changelog from completed tasks
list-plansDiscover available task plans/templates
apply-planApply a task plan to the board
create-boardCreate a new board (requires account token)
get-installation-instructionsGet setup instructions

📚 Resources

URIDescription
moo-tasks://<boardId>/board-stateFull board snapshot grouped by status
moo-tasks://<boardId>/agent-instructionsWorkflow instructions for agents

💬 Prompts

PromptDescription
task-workflowGuided 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

LevelDescription
🌍 GlobalEdit at /settings/instructions, applies to all boards by default
📋 Per-BoardOverride in board settings, falls back to global when reset

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


🔌 MCP Client Configuration

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

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>"
      }
    }
  }
}

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

MethodRoutePurpose
POST/api/auth/registerRegister with email/password
POST/api/auth/loginLogin with email/password
MethodRoutePurpose
GET/api/boardsList boards for current user
POST/api/boardsCreate a new board
GET/api/boards/:idGet board details
PATCH/api/boards/:idUpdate board (owner only)
DELETE/api/boards/:idDelete board (owner only)
MethodRoutePurpose
GET/api/boards/:id/membersList board members
POST/api/boards/:id/membersInvite user by email
DELETE/api/boards/:id/members/:userIdRemove member
MethodRoutePurpose
GET/api/boards/:id/tasksList tasks for a board
POST/api/boards/:id/tasksCreate a task in a board
GET/api/tasks/:idGet a single task
PATCH/api/tasks/:idUpdate task fields
DELETE/api/tasks/:idDelete a task
MethodRoutePurpose
GET/api/instructionsGet global instructions
PUT/api/instructions/:idUpdate global instruction
POST/api/instructions/:id/resetReset to default
GET/api/boards/:id/instructionsGet board instructions
PUT/api/boards/:id/instructions/:instructionIdUpdate board instruction
POST/api/boards/:id/instructions/:instructionId/resetReset 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

TechnologyPurpose
Nuxt 4 (Nitro + Vue 3)Framework
Tailwind CSS v4Styling
MySQL + Drizzle ORMDatabase
nuxt-auth-utilsAuth (sealed cookie sessions, scrypt hashing)
@modelcontextprotocol/sdkMCP server integration
vuedraggableDrag & drop
nanoidID generation

Ver o original no GitHub

Bom para

Relacionados