Connect Windsurf to your fenbs board
Windsurf’s Cascade agent can use MCP servers. Add fenbs with one URL and Cascade reads your board, files what it finds and moves what it finishes — under your role, signed.
Last checked
Connect
- In Windsurf, open the Cascade settings and the MCP servers section (it edits
mcp_config.json). - Add fenbs as a server with the URL below. Windsurf opens fenbs in your browser; sign in, tick what it may do, approve.
- In Cascade, ask what is on your board. The first call is
fenbs_whoami.
{
"mcpServers": {
"fenbs": {
"serverUrl": "https://fenbs.ai/api/mcp"
}
}
}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 fenbs-mcp. It forwards to the same endpoint and the token holds the same role.
What it can do once connected
- Read the board:
fenbs_list_itemswith filters by lane, kind or free text, andfenbs_get_itemfor 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 withfenbs_search. - Read your AI context with
fenbs_get_contextand add to it withfenbs_add_context_note. - Ask
fenbs_whoamifirst: 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.