Veritas Kanban MCP

The Veritas Kanban MCP server hands an agent 42 tools for a local kanban board: tasks, sprints, comments and projects.

  • 852 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

Why this level

  • The agent creates, changes and closes tasks on the board.
  • The admin key gives full access to the board API.
All reasons and checks

bradgroux/veritas-kanban

Install

Manual install

{
  "mcpServers": {
    "veritas-kanban": {
      "command": "node",
      "args": ["/path/to/veritas-kanban/mcp/dist/index.js"],
      "env": {
        "VK_API_URL": "http://localhost:3001",
        "VK_API_KEY": "your-agent-api-key"
      }
    }
  }
}

A snippet from the README; the path points to the built `mcp/dist/index.js` in your clone of the repository.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The agent creates, changes and closes tasks on the board.
  • The admin key gives full access to the board API.

This is third-party code. Review the repository files before installing.

What it does

Veritas Kanban, a local task board, gives agents an MCP server with 42 tools in nine groups: tasks, agents, automation, notifications, summaries, sprints, comments, projects and run-scoped tool control. The agent creates and moves cards, writes comments and builds board summaries. The board starts from source with `pnpm install` and `pnpm dev`, and the MCP server is built from the `mcp` folder. A `vk` command-line client exists too. The board works on its own, and further layers are switched on as needed.

Who it is for. Developers who keep tasks on a local board and want agents to see and update it. It suits those who prefer not to store tasks in a cloud tracker.

Good fit when

  • The agent picks up tasks from the board, changes status and comments with the result.
  • Before a sprint the agent gathers a summary of open cards.
  • Several agents share tasks on one board, and the key role limits their rights.
  • Tasks cannot go to a cloud tracker and stay on the machine.

Not a fit when

  • A managed cloud tracker with no server of your own is needed.
  • The board is not running: the MCP tools need the API address.
  • Agents would get the admin key instead of an agent-role key.

Example request

Show the open sprint tasks on the board, take the highest-priority one, move it to in progress and leave a comment with a plan.

MCP

Transport
stdio
Authentication
key is optional

Environment variables

VK_API_URL required
API address of the running board, for example http://localhost:3001
VK_API_KEY secret
API key for write tools; an agent-role key is preferred

Limitations

The MCP server needs a running board: it calls the board API at `VK_API_URL`. Write tools require `VK_API_KEY` unless local auth bypass grants an agent or admin role. Agents should get an agent-role key, not the admin one. In the README the config points to the built `mcp/dist/index.js`, so the project must be built first. Version 6.3.0 includes optional ChatGPT sign-in and an OrcaRouter profile that need separate setup, and the authors mark OrcaRouter compatibility as unverified.

How to disable. Remove the `veritas-kanban` entry from the client MCP configuration and restart it. Stop the board itself, delete task data by hand and revoke agent keys in the board settings.

FAQ

Does the MCP server need the board?

Yes. The server calls the API of a running board and returns no data without it.

Which key should the agent get?

One with the agent role. Write tools need it, while the admin key opens full access to the board API.

Is there a desktop app?

Yes, for Mac: `brew tap BradGroux/tap`, then `brew install --cask veritas-kanban`.

What if the server is not visible?

Restart the MCP client after editing the config. For OpenClaw run `openclaw gateway restart` and `openclaw mcp list`.

How many tools does the server have?

42 tools in nine groups: tasks, agents, automation, notifications, summaries, sprints, comments, projects and run-scoped tool control.

Discussion

No questions or reviews yet.

Four skills for agents working with the Agent Kanban task board: worker, maintainer, task creator and project planner, with human review of the result

SkillBroad access506Repository stars

A workspace for parallel Claude Code and Codex tasks, with separate Git worktrees, terminals and change review

CLIBroad access1.2KRepository stars

A bridge between local CLI agents: Codex, Cursor or Claude Code delegate work to Antigravity, Grok, Kimi and seven more.

MCP serverBroad access134Repository stars
Official

runpane MCP server: an agent in any repository opens Pane panels, starts other agents and reads their status

MCP serverBroad access664Repository stars
Official

A local MCP bridge sends chat-client tasks to authorized projects and shows execution and approvals in a workbench.

MCP serverExtended access314Repository stars

A local MCP server for coordinating teams of agents: identities, messages, handoffs and a live dashboard in one repo.

MCP serverExtended access111Repository stars

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialAuthenticationRepository starsMain difference
Veritas Kanban (this card)nokey is optional852
Agent Kanbanno506a separate board for agents; Veritas Kanban adds an MCP server with 42 tools, sprints and key roles
CodeKanbanno227a kanban for code work; Veritas Kanban keeps tasks local and ships a `vk` command-line client

README in short

The README starts with the board quick start, then lists features, setup paths and optional layers. A separate section covers the MCP server, environment variables and verification.

README badge

Report a problem