@forked-online/platform-mcp

MCP server for the Forked Online platform (multi-tenant). Point Claude Code (or any MCP client) at your workspace to read & write projects, work items, todos, and activities.

Note: this is the platform client (workspace-key auth against platform.forked.online). The original single-operator client is @forked-online/mcp.

Install

npm i @forked-online/platform-mcp

Configure

Grab your workspace API base + key from the in-app /mcp page (owner only), then run:

FORKED_API_BASE=https://platform.forked.online/api/v1 \
FORKED_API_KEY=fkd_your_workspace_key \
npx @forked-online/platform-mcp

Or wire it into your MCP client config (e.g. Claude Code mcpServers):

{
  "mcpServers": {
    "forked-online-platform": {
      "command": "npx",
      "args": ["@forked-online/platform-mcp"],
      "env": {
        "FORKED_API_BASE": "https://platform.forked.online/api/v1",
        "FORKED_API_KEY": "fkd_your_workspace_key"
      }
    }
  }
}

Tools

list_projects, get_project, list_work_items, get_work_item, get_next_work_item, create_work_item, update_work_item, set_work_item_status, assign_workitem_to_branch, post_thread_message, create_todo, complete_todo, list_todos, log_activity, list_activities.

Epic Loop

File a parent create_work_item(kind:"epic"), then children with parent_ref and a drift_guard ({ allowed_paths, out_of_scope, acceptance_criteria }); order them with link_work_items. A coding agent then drives the whole feature through get_next_work_item(epic_ref), which returns a runbook + the next dependency-unblocked child under a hard scope guard, and a file-boundary review gate keeps each child on-spec — no hand-pasted orchestration prompt.

The key is workspace-scoped: it grants full access to that one workspace. Keep it secret; rotate it anytime in workspace Settings.

Develop

npm install
npm run build   # tsc → dist/
npm start

License

MIT