FeatureBoard install help

The server is plain stdio MCP — the same package runs in Claude Cowork, Claude Code, Cursor, Grok Build, or anything else that speaks MCP. Pick your host below. Requires Node.js ≥ 18. AI assistants: a machine-readable install manifest is embedded at the end of this page (<script id="featureboard-install-manifest">) — parse it and follow the deterministic steps.

Updated October 30, 2026 · v0.16.12 · ✅ Supported · support@featureboard.ai · release notes

Get the server unpacked install

⬇ featureboard.mcpb — Claude Cowork / Desktop (server + skills)  ·  ⬇ featureboard-openclaw.tgz — OpenClaw plugin  ·  ⬇ featureboard-cursor.zip — Cursor plugin  ·  ⬇ featureboard-mcp.zip — Grok Build / any MCP client (server only)

featureboard.mcpb is an ordinary zip archive. The unpacked install is the same everywhere:

# unzip the release above (server + dependencies included, no npm needed)
unzip featureboard-mcp.zip -d featureboard

Either way the launch command is node /absolute/path/featureboard/server/index.js. Boards live in ~/FeatureBoard unless FEATUREBOARD_DATA_DIR says otherwise.

Claude Cowork

Use the packaged bundle: open featureboard.mcpb in Cowork or Claude Desktop and press Install. One install carries the MCP server plus the featureboarding and daily-plan skills. No config needed.

Claude Code

Download featureboard.plugin and upload it in Claude under Customize → Plugins → Add → Upload plugin. It syncs into Claude Code at the next session start, tools and skills together. For one session from a folder, unzip it and run claude --plugin-dir ./featureboard.

OpenClaw

Download featureboard-openclaw.tgz — it's a plugin bundle: skills plus the MCP server, ready for the gateway.

openclaw plugins install ./featureboard-openclaw.tgz

Then restart the gateway. Verify with openclaw plugins list — every tool registers as featureboard__<tool>.

Cursor

Recommended: download featureboard-cursor.zip and unzip it into ~/.cursor/plugins/local/featureboard, then run Developer: Reload Window.

Or configure it by hand — add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "FeatureBoard": {
      "command": "node",
      "args": ["/absolute/path/featureboard/server/index.js"],
      "env": {
        "FEATUREBOARD_CORE_ONLY": "1",
        "FEATUREBOARD_CLIENT_NEUTRAL": "1"
      }
    }
  }
}

Cursor warns above ~40 enabled tools, so run core-only mode (140 board/task tools) plus per-tool toggles in Cursor's settings.

Grok Build

grok mcp add featureboard -- node /absolute/path/featureboard/server/index.js

Or configure [mcp_servers.featureboard] in ~/.grok/config.toml. Grok Build also auto-loads a repo's .mcp.json and .cursor/mcp.json — a checkout of the FeatureBoard repo works with zero reconfiguration.

Any MCP client

For AI assistants automatable

If you are an AI assistant installing FeatureBoard for a user, follow these deterministic steps:

1. GET  https://featureboard.ai/releases/latest.json          → read version + artifact URLs
2. Claude Cowork host?  → download artifacts.mcpb, ask the user to open it and press Save. DONE.
3. Otherwise: download artifacts.mcpZip, unzip to a stable absolute path <DIR>.
4. Write the host's MCP config (see manifest below): command=node, args=["<DIR>/server/index.js"],
   env FEATUREBOARD_CORE_ONLY=1 and FEATUREBOARD_CLIENT_NEUTRAL=1 for non-Claude hosts.
5. Verify: spawn the command, send JSON-RPC initialize then tools/list —
   expect 321 tools (140 when FEATUREBOARD_CORE_ONLY=1). Report the count to the user.

Everything runs locally; the server makes no outbound calls except explicitly-invoked tools (see the privacy policy in the repo). Boards are plain markdown in ~/FeatureBoard.

Licensing is identical in every host: free for personal & public work, US$9.99/seat/mo (or US$99.99/seat/yr) for commercial use — see pricing.

Troubleshooting Cowork sandbox

Running inside Claude Cowork and the shell/tests stop working — errors like useradd failed: exit status 12: cannot create directory /sessions/… or “Workspace unavailable”, or a scheduled task that silently stops? That’s the Cowork sandbox filling its disk, not FeatureBoard. Reset the sandbox’s disk image (your boards and repos are never touched) — full macOS/Windows steps ship in the bundle’s README.md, or ask us via a support booking.