fenbs-mcp connects any MCP client to the fenbs board (https://fenbs.ai）。fenbs is a simple project management tool where both people and AI assistants are board members, each holding a role, and every change is signed by the operator. The board has four swimlanes, three task types (Feature, Enhancement, Bug), roles described in plain words, and an audit trail that names the AI assistant. It also supports decisions with sign-off, recording tests on each task, and tasks pre-approved by a person for an AI assistant to pick up when idle.
Most of the time you probably don't need this package. fenbs communicates over HTTP as MCP and supports browser login. Most clients can connect directly without copying a token. Step-by-step instructions are in https://fenbs.ai/integrations。只有客户端仅支持 stdio, or when the machine cannot open a browser (CI, server, container), use fenbs-mcp. It bridges stdin/stdout to the remote server using a manually issued token.
How to get a token: in fenbs, go to "Settings → Connect an AI assistant", name the assistant, check read / write / comment, and copy the token. The token is shown only once. It can also be used for client configurations that require a command.
The actions an assistant can perform fall into the following categories. Tasks: fenbs_whoami, fenbs_list_boards, fenbs_list_items, fenbs_get_item, fenbs_create_item, fenbs_update_item, fenbs_flag_item, fenbs_comment, fenbs_search, fenbs_delete_item, fenbs_restore_item. AI pre-approval: fenbs_next_approved_task, fenbs_release_task. Decisions and rules: fenbs_list_decisions, fenbs_get_decision, fenbs_add_decision, fenbs_update_decision, fenbs_request_signoff, fenbs_delete_decision, fenbs_restore_decision. AI context: fenbs_get_context, fenbs_add_context_note, fenbs_list_context_notes, fenbs_update_context_note, fenbs_delete_context_note. Projects: fenbs_list_projects, fenbs_add_project, fenbs_rename_project, fenbs_delete_project, fenbs_restore_project. The tool list comes from fenbs itself, so new tools require no update to this package.
About rules: a rule is a decision. A rule is a decision that stays in effect from this moment on (standingRule: true). When someone states how something must always be done, or must never be done, the assistant should record it with fenbs_add_decision (status decided, with that person as the decision-maker, and quoting their exact words), and must never record it as a context note. fenbs_get_context shows rules first and in full, and the assistant must follow every rule. Context notes are only for recording facts that no one chose: how the code works, a pitfall, where something is located.
The tool acts as the token issuer and holds their board role, with permissions limited by the checked scopes. A refusal is presented as one sentence that the assistant can relay to you, for example: "You are a Viewer on Kitchen Refit, which cannot move tasks between lanes." After the token is revoked in Settings, it stops immediately.
The full guide is written for both people and assistants:https://fenbs.ai/llms.txt。无依赖，需要 Node 20 or newer, MIT licensed.
