Get started with FeatureBoard
FeatureBoard is a local, file-backed project board your AI agent actually works: it pulls the next ticket, writes the code, logs the diff and commits per ticket. Your boards are plain markdown you own forever. No SaaS, no login, no lock-in. The only thing that leaves your machine is an anonymous, opt-out usage count, never your board content. Installing takes about a minute.
Updated October 30, 2026 · v0.16.12 · ✅ Supported · support@featureboard.ai · release notes
1 · Install it
Pick the app you use. Claude Cowork and Claude Desktop take one file and one click. Install guide
Bundle (.mcpb)
One file, one click. No terminal.
- Download
featureboard.mcpb - Open it in Claude Cowork and press Install
- On Claude Desktop, double-click the
.mcpbinstead — or Settings → Extensions → Advanced → Install Extension
Activates the MCP server plus the featureboarding and daily-plan skills together. Always the current release; versioned bundles (e.g. featureboard-0.16.12.mcpb) stay up if you'd rather pin.
Plugin (.plugin)
Tools and skills, synced into every Claude Code session.
- Download
featureboard.plugin - In Claude: Customize → Plugins → Add → Upload plugin
- Start a new Claude Code session
Plugin bundle
Skills + MCP server, installed into your gateway.
- Download
featureboard-openclaw.tgz - Run
openclaw plugins install ./featureboard-openclaw.tgz - Restart the gateway
Verify with openclaw plugins list — tools appear as featureboard__<tool>.
Cursor plugin
One folder drop, then reload.
- Download
featureboard-cursor.zip - Unzip into
~/.cursor/plugins/local/featureboard - Run Developer: Reload Window
Cursor caps active tools around 40 across all servers — core-only mode plus per-tool toggles keeps you under it.
MCP server zip
Point your MCP config at the server entry point.
- Download
featureboard-mcp.zipand unzip it - Target
server/index.jsin your MCP config
Needs Node.js 18+. Dependencies: @modelcontextprotocol/sdk and zod. For non-Claude hosts also set:
FEATUREBOARD_CORE_ONLY=1
FEATUREBOARD_CLIENT_NEUTRAL=1
2 · Point it at a boards folder
On first run FeatureBoard asks where your boards live, defaulting to ~/FeatureBoard. Any subfolder
containing a featurelist.md or buglist.md is a board — so an existing folder of markdown
works immediately, and a brand-new empty folder is fine too.
It starts in Essential tools only mode (~140 core board tools) to keep your context light. Turn on the full toolset later if you want the website builder, CRM, analytics, and the rest.
3 · Talk to it
There is no UI to learn. Ask for the board, then describe what you want.
“Open the FeatureBoard board.”
The live board renders as an artifact. From there, plain language does the work:
“Log a bug: gallery modal won't dismiss on mouse-out.”
“Brainstorm five onboarding features and add them.”
“Work the next ticket.”
“How's velocity looking this week?”
What it costs
Free forever for personal and public work. Commercial use is licensed per seat, and you can try it commercially for a day before paying anything.
| Plan | Price | For |
|---|---|---|
| Personal & public | Free | Personal projects and public/open-source work |
| Commercial trial | 24 hours, free | Evaluating it at work — starts from inside the product, once per org |
| Commercial | $9.99/seat/mo — or $99.99/seat/yr | Commercial use, licensed per seat |
When a trial ends, writes freeze — your markdown stays yours and readable either way.
Want it set up for you?
If you would rather not do any of this yourself, there are guided setup and done-for-you bootstrap options, or you can book a session to walk through it together.
Stuck on install? Install help for humans and AI assistants covers the edge cases, including machine-readable instructions you can hand to an agent.