Skip to main content
Glama

BoardAgent

A task manager that lives on your computer — for you and your AI agents. Terminal UI, REST API, MCP server. Free, local, no cloud.

Install (Windows)

You need the prebuilt exes. Two ways to get them:

Option A — use the release binaries (easiest): Download the latest release from GitHub → unzip → double-click INSTALL.bat. That's it. It copies the programs, sets up autostart, installs a watchdog, and adds the app to your PATH.

Option B — build them yourself: Requires Python 3.10+.

pip install -e .          # installs the 3 CLI commands
python scripts/build_exes.py   # builds boardagent.exe, boardagent-server.exe, boardagent-mcp.exe into dist/

Then run INSTALL.bat.

Related MCP server: MCP Task Assistant

Run

Windows (after INSTALL.bat): double-click boardagent.exe (or type boardagent in a terminal). The background server auto-starts at logon.

Anywhere (source):

boardagent-server   # terminal 1 — the background service
boardagent          # terminal 2 — the task board UI

First-time tips:

  • Press c to create a task, a for AI mode, q to quit.

  • Full keyboard-first: arrows move, space selects/opens, enter activates.

  • Settings tab: theme, opacity, API keys, keybinds.

Let an AI agent use the board

Point your MCP host (Claude Desktop, Cursor, Hermes) at boardagent-mcp:

{
  "mcpServers": {
    "boardagent": { "command": "C:\\path\\to\\boardagent-mcp.exe" }
  }
}

Create an API key in Settings → API Keys for anything else.

How it works

  • REST API — source of truth, http://127.0.0.1:7373.

  • MCP server — thin adapter over the same service layer.

  • Textual TUI — the app you see, talks to the service over localhost.

  • Data lives in ~/.boardagent/boardagent.db (SQLite). Everything local.

Docs

  • For humans: docs/human/ — intro, MCP setup, themes, packaging.

  • For AI agents: docs/agent/ — token-optimized REST + MCP references.

Development

python -m pytest
python scripts/generate_agent_docs.py   # needs the server running
python scripts/build_exes.py            # Windows exes into dist/

License

MIT — see LICENSE.

Available Tools

7 tools
boardagent_claim_taskB

Claim/lock a todo task for an agent. Returns an error if unavailable. Requires write role.

Inputs: id (required), agent_id (required).

boardagent_complete_taskA

Mark a task done. Only the owning agent may complete it. Requires write role.

Inputs: id (required), agent_id (required).

boardagent_create_taskA

Create a new task. Priority is a color: red/orange/yellow/green/blue/white. Tasks are always created as todo (claim to start work). Requires write role.

Inputs: title (required), due, tags, links, +10 more.

boardagent_delete_taskA

Delete a task by id. Requires admin role.

Inputs: id (required).

boardagent_get_taskB

Read a single task by id. Requires read role.

Inputs: id (required).

boardagent_list_tasksC

List tasks, optionally filtered. Requires read role.

Inputs: limit, owner, offset, status, +1 more.

boardagent_update_taskC

Update a task. Metadata is merged into agent_id's namespace. Requires write role.

Inputs: id (required), due, tags, links, +12 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a distinct action: CRUD (create/list/get/update/delete) plus two clearly-scoped lifecycle operations (claim for locking, complete for finishing). Claim vs update are well separated by their descriptions (lock vs metadata merge), so misselection is unlikely.

    Naming Consistency5/5

    All seven tools share the boardagent_ prefix and follow a strict verb_noun pattern (create_task, list_tasks, get_task, delete_task, update_task, claim_task, complete_task). No mixed conventions or vague verbs.

    Tool Count5/5

    Seven tools is a well-scoped set for a task board, covering the essential operations without bloat. Every tool earns its place.

    Completeness4/5

    Full CRUD plus claim/complete lifecycle is strong, but a few natural operations are absent: releasing/unclaiming a task, reopening a completed task, and explicit assignment. These are minor gaps an agent can largely work around.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for task management that enables AI agents to read, create, update tasks, and track work sessions, allowing agents and humans to collaborate on the same task board.
      14
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to manage task state through MCP, including creating, updating, and tracking tasks, with support for client-side encryption and secure local credential storage.
      21 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to browse task groups, list open or completed todos, create new tasks, mark them done, and update their content or status through a token-authenticated MCP connection.
      5
      MIT