FeatureBoard

FeatureBoard — the board Claude actually runs

A local, markdown-backed project board that lives inside Claude— packaged as a Claude Desktop / Cowork extension (.mcpb). Point it at a folder, and Claude plans, logs, prioritizes, andworkstickets in plain language — then renders the whole thing as a live, interactive board artifact with a full analytics dashboard. No SaaS, no login, no lock-in. Your boards are plainfeaturelist.md/buglist.mdfiles you own forever.

It started as a hosted web app (OpenClaw). We rebuilt it as an MCP server by taking the original app's file list and porting it, tool by tool,while learning MCP from scratch— and it came together fast. What you get is ~216 tools spanning the entire product surface: board and churn loop, analytics, testing, a media studio, CRM, leads, contracts, mail and marketing, a website builder with git deploys, and per-ticket commits. The board is the front door; everything the original app did is one sentence away in chat.

- It's the board Claude drives, not a database you poke.Ask "what's on my plate," "break FBF-300 into subtasks," or "ship the next ticket" — Claude pulls work, sets status, writes the code, logs the diff, and commits. The board stays honest because the agent keeps it honest.
- One command opens the real UI.get_boardreturns the shipped board as a Cowork artifact — Todo / In Progress / Done columns, filters, dark mode, click-to-move, and a 📊 analytics dashboard (velocity, timeline, bug health, work-log feed) — all wired live to the server. No hand-rolled mockups.
- Your files, your rules.Boards are byte-compatible markdown. Existing FeatureBoard folders work with zero migration. Writes are atomic. Delete the extension tomorrow and your boards are still just markdown.
- Depth when you want it.The same server that tracks tickets also generates media, runs a CRM, drafts contracts and campaigns, builds and deploys a marketing site, and commits your code per ticket. Turn it down to the essentials with one toggle, or open the whole toolbox.