Connect GitHub Copilot in VS Code to your fenbs board

Connect

1. In VS Code, add an MCP server: either through the command palette (“MCP: Add Server”) or by creating .vscode/mcp.json in the workspace with the contents below.
2. Start the server from the MCP view. VS Code opens fenbs in your browser; sign in, tick what it may do, approve.
3. Open Copilot Chat in agent mode and ask what is on your board.

{
  "servers": {
    "fenbs": {
      "type": "http",
      "url": "https://fenbs.ai/api/mcp"
    }
  }
}

The file can be committed, so everyone who opens the repository gets the board without setup; each person signs in as themselves and gets their own role. MCP support in VS Code is in the editor’s own settings and may need enabling in some organisations.

What it can do once connected

• Read the board: fenbs_list_items with filters by lane, kind or free text, and fenbs_get_item for one task with its comments.
• Add tasks with fenbs_create_item — a Feature, an Enhancement or a Bug, in a lane, with a priority.
• Move and edit with fenbs_update_item: change the lane, the title, the note, the kind or the priority.
• Comment with fenbs_comment, and search across everything it can see with fenbs_search.
• Read your AI context with fenbs_get_context — the notes you keep on the board about how you work — and add to it with fenbs_add_context_note.
• Ask fenbs_whoami first: it answers who the assistant is acting as and what it may do, which is the question to settle before it writes anything.

What it cannot do

Anything you cannot. The assistant acts as you and holds your role on the board, narrowed by the scopes you ticked when you approved it: read, write, comment. If your role cannot move tasks between lanes, neither can the assistant, and it is told so in a sentence it can repeat to you: “You are a Viewer on Kitchen Refit, which cannot move tasks between lanes.” Revoke its token in Settings and it stops at once; everything it did stays in the history under its name.