mc — project management for developers and AI agents

Manage tasks, meetings, research, contacts, and sprints with plain Markdown files. No database, no server, no account — just files in your repo that you can git diff, review in PRs, and edit with any tool. Works from your terminal and from AI editors via MCP.

Quickstart

cargo install mc
cd my-project && mc init --embedded
mc -y new task "Ship the feature" --priority 2
mc task board

That's it. You now have a .mc/ folder with task tracking in your project.

Why mc?

• Plain Markdown + YAML frontmatter — git diff your project management
• No database, no server, no account — just files in your repo
• Built for AI agents — full MCP server, one command to connect
• Embedded mode — .mc/ folder lives alongside your code
• Kanban board, sprint planning, meeting notes, research tracking, contact management — all from the terminal

Two Ways to Use It

Embedded Mode (recommended for most projects)

Add mc to an existing project. Creates a .mc/ folder for tasks, meetings, research, sprints, and proposals (no customers, projects, or contacts).

cd my-project
mc init --embedded

my-project/
├── .mc/
│   ├── config.yml
│   ├── tasks/
│   ├── meetings/
│   ├── research/
│   ├── sprints/
│   └── proposals/
└── (your code)

Standalone Mode (for portfolios and CRM)

Create a dedicated repository for managing customers, projects, and all related work.

mc init --name "My Company"

my-company/
├── config/config.yml
├── customers/
├── projects/
├── meetings/
├── research/
├── tasks/
├── sprints/
└── proposals/

Standalone mode adds customers, contacts, and projects — useful for agencies, freelancers, or anyone managing multiple clients.

What You Can Track

Task Management

Tasks are first-class citizens with a full kanban workflow.

Kanban Board

mc task board

┌─────────────────────────────────────────────────────────────────────┐
│ backlog          todo             in-progress      done             │
├─────────────────────────────────────────────────────────────────────┤
│ TASK-003 [P3]    TASK-002 [P2]    TASK-001 [P1]                     │
│ Write tests      Update docs      Fix auth bug                      │
└─────────────────────────────────────────────────────────────────────┘

Move Tasks

mc task move TASK-001 in-progress
mc task move TASK-001 done

Next Task

Get the highest-priority unblocked task:

mc task next

Filtering

mc list tasks --status in-progress --priority 1
mc list tasks --sprint 2026-W06 --owner alice
mc task board --project PROJ-001

Dependencies

Tasks can depend on other tasks:

mc new task "Deploy to prod" --depends-on TASK-001,TASK-002

Blocked tasks are hidden from mc task next until their dependencies are done.

AI Agent Integration (MCP)

Connect your AI editor to mc with one command:

Claude Code:

claude mcp add mc -- mc mcp

Cursor, Windsurf, Claude Desktop (add to your MCP config):

{
  "mcpServers": {
    "mc": {
      "command": "mc",
      "args": ["mcp"]
    }
  }
}

VS Code (.vscode/mcp.json):

{
  "servers": {
    "mc": {
      "type": "stdio",
      "command": "mc",
      "args": ["mcp"]
    }
  }
}

Now your AI assistant can create tasks, move them through the board, query status, create meetings, and more.

Available MCP Tools

All tools return JSON with documented fields. Parameter descriptions include valid values, defaults, and examples — AI agents can discover the full API from the tool schema alone.

MCP Resources

Resources provide read-only data snapshots. Start with mc://config to discover valid status values and ID prefixes.

Web Dashboard

Browse all your data in a local web UI:

mc serve
# Open http://localhost:5000

Installation

From crates.io

cargo install mc

Prebuilt Binaries

Download from GitHub Releases:

tar xzf mc-<platform>.tar.gz
sudo mv mc /usr/local/bin/

Build from Source

git clone https://github.com/RaaSaaR-org/mission-control.git
cd mission-control
cargo build --release
# Binary is at target/release/mc

Configuration

Config lives at .mc/config.yml (embedded) or config/config.yml (standalone). It controls:

• Directory paths for each entity type
• ID prefixes (CUST, CONT, PROJ, MTG, RES, TASK, SPR, PROP)
• Allowed status values per entity type

The defaults work out of the box. Edit the config when you want to customize status workflows or add new prefixes.

CLI Reference

Use mc <command> --help for detailed options.

Contributing

CI runs on every push and PR:

• cargo fmt --check
• cargo clippy -- -D warnings
• cargo test
• cargo build --release

See CLAUDE.md for architecture details and build commands.

License

MIT