Connect Gemini CLI to your fenbs board
Gemini CLI reads MCP servers from its settings file. Add fenbs and Gemini can read the board, file bugs and move tasks from the terminal, under your role, signed by name.
Last checked
Connect
- Open Gemini CLI’s settings file (
~/.gemini/settings.json, or the project’s.gemini/settings.json). - Add fenbs under
mcpServerswith the URL below. - Start Gemini CLI and run
/mcp. A browser opens on fenbs; sign in, tick what it may do, approve. - Ask what is on your board.
{
"mcpServers": {
"fenbs": {
"httpUrl": "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.