Flux plugin

Kanban board with a CLI, an MCP server and a Claude Code plugin: tasks in one JSON file in your repo, shared by humans and agents.

  • 109 ★ on the repository
  • Last commit
Plugin

Extended access

Why this level

  • An agent creates and closes tasks and webhooks, and an MCP endpoint without a key exposes the board to anyone on the network.
All reasons and checks

sirsjg/flux

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add plugins/flux

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

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

  • An agent creates and closes tasks and webhooks, and an MCP endpoint without a key exposes the board to anyone on the network.

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

What it does

Flux keeps tasks for several projects in one JSON file in your repository and syncs them through a `flux-data` git branch with `flux push` and `flux pull`. The CLI, web board, REST API, webhooks and MCP server all work on the same data. An agent sees epics, tasks, dependencies and P0 to P2 priorities, and `flux ready` shows only unblocked tasks by priority. The MCP server exposes more than 25 tools for projects, epics, tasks, comments, webhooks and blobs. Task comments serve as agent memory between sessions. The Claude Code plugin adds `/flux-generate`, `/flux-add` and `/flux-status`; the first reads project documents and creates epics and tasks with dependencies.

Who it is for. Teams where humans and agents share tasks, and developers who want a board without a database or SaaS.

Good fit when

  • README or requirements have to become epics and tasks with dependencies through `/flux-generate`.
  • An agent must be given the next unblocked task by priority.
  • Tasks should travel with the repository and work offline.
  • Webhooks on task changes have to go to Slack, GitHub or CI.

Not a fit when

  • You need a managed cloud board with roles and reports; Flux keeps data in one file.
  • Dozens of people edit at once and JSON merge conflicts are unacceptable.
  • The board must be exposed to the internet without authentication.

Example request

Read the project README, create epics and tasks with dependencies on the Flux board, then show the next ready task.

Limitations

Tasks live in a single JSON file, so large teams may hit merge conflicts. The web UI binds to localhost by default. When exposed beyond localhost the server is locked: set `FLUX_API_KEY` or explicitly allow anonymous access with `FLUX_ALLOW_ANONYMOUS=1`. The MCP HTTP endpoint is unauthenticated by default. claude.ai connectors need OAuth, which `FLUX_MCP_PASSWORD` enables, and the server must be reachable from outside. The Docker quickstart runs the web UI and an MCP server on stdio, and the Claude Code plugin needs a restart after install.

How to disable. Remove the plugin through `/plugin` and the CLI with `npm uninstall -g flux-tasks`. Stop the container with `docker stop flux-web` and delete the `flux-data` branch from the repository by hand.

FAQ

How do I install Flux?

Run `npm install -g flux-tasks` for the CLI alone. The full stack with the web UI comes up through the Docker `quickstart.sh` script, with `quickstart.ps1` for Windows.

How do I connect the MCP server to Claude Code?

With the Docker stack running, run `claude mcp add flux -- docker exec -i flux-web bun packages/mcp/dist/index.js`. Codex uses the same command with `codex mcp add`.

What do the plugin commands do?

`/flux-generate` reads project docs and creates epics and tasks, `/flux-add` quickly adds a task and `/flux-status` shows the board state and suggests the next step.

How do I sync the board between machines?

With `flux push` and `flux pull`: data goes through the repository's `flux-data` branch, so ordinary git works, including offline.

How do I make an agent use the board?

Add a Flux section to `AGENTS.md` or `CLAUDE.md`. The README has sample rules: always pass `project_id` and take work through `flux ready`.

Discussion

No questions or reviews yet.

Plugins
Official

A local kanban board and MCP server give people and coding agents shared tasks, comments and visible work progress in a browser.

MCP serverExtended access1.2KRepository stars

A self-hosted issue tracker and wiki on Cloudflare with MCP: 126 tools, issue leases and file claims for several agents

MCP serverBroad access66Repository stars

Planfix MCP

planfix-mcp

Russian stack

Planfix MCP server: tasks, projects, contacts, comments and employees through the REST API

MCP serverBroad access5Repository stars

Kanvas хранит план проекта в одном kanvas.json: агенты вносят задачи на утверждение и сдают на ревью.

CLIMinimal access404Repository stars
Official

The official Taskade MCP and plugin: an agent manages workspace projects, tasks, automations and AI agents.

MCP serverBroad access169Repository stars
Official

A terminal kanban board with a 47-tool MCP server: the agent manages boards, cards and sprints in a local file

MCP serverExtended access189Repository stars

README in short

A task engine with a CLI, web dashboard, REST API, webhooks and MCP server on one JSON file, plus a plugin that generates a board from requirements.

README badge

Report a problem