Labsco
MCP SERVER

Task Manager (Go)

by gosvig123

Keep projects as markdown task files that you and the assistant both edit — tasks, subtasks, status, priority and dependencies.

Project & Task Management
Summary
A task list that lives in your repository.

Because a project is a markdown file rather than a row in someone else's database, the plan diffs, reviews and travels with the code it belongs to.

What it is

A task manager whose storage is plain markdown, one file per project. Tasks carry status, priority, category and complexity, support subtasks up to three levels deep, and stay readable in version control.

What you get
  • A project created as its own markdown task file
  • Tasks added with category, priority and dependencies on other tasks
  • The projects you have, listed back
  • Status tracked across todo, in progress, done and blocked
  • Complex tasks broken into subtasks, recursively up to three levels
Requirements

Go 1.21 or later to build it. Tasks are written to a directory you choose — ./tasks unless the environment says otherwise — and it speaks stdio by default, or SSE if you set TRANSPORT.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary