Connect Devin Desktop (formerly Windsurf) to your fenbs kanban board

Connect Devin Desktop (formerly Windsurf)

1. Open your user MCP file, ~/.config/devin/mcp_config.json on macOS and Linux or %APPDATA%\devin\mcp_config.json on Windows, to use fenbs in every project. For one project only, use .devin/mcp_config.json in it.
2. Add fenbs under mcpServers with the URL below, and save. Devin Local, the only agent in Devin Desktop since Cascade was removed, reads the same files as Devin CLI.
3. The first time the agent uses fenbs, it opens fenbs in your browser; sign in, tick what it may do, approve. If fenbs later shows “Needs auth”, click Authenticate and sign in again.
4. Ask the agent what is on your kanban board. The first call is fenbs_whoami. Devin Local asks before it calls any MCP tool; you can allow one tool or all of fenbs, for the session or for good.

{
  "mcpServers": {
    "fenbs": {
      "url": "https://fenbs.ai/api/mcp"
    }
  }
}

From a terminal, Devin CLI writes the same file: devin mcp add -s user fenbs https://fenbs.ai/api/mcp, then devin mcp login fenbs.

If the client cannot open a browser, or only speaks stdio, use the fenbs-mcp bridge with a token from Settings, “Connect an AI assistant”: FENBS_TOKEN=… npx -y fenbs-mcp. It forwards to the same endpoint and the token holds the same role.

What it can do once connected

• Read the kanban 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 and keep it current with fenbs_add_context_note, fenbs_update_context_note and fenbs_delete_context_note.
• Ask fenbs_whoami first: it answers who the assistant is acting as and what it may do.

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: read, write, comment. A refusal is a sentence it can repeat to you. Revoke its token in Settings and it stops at once; everything it did stays in the history under its name.