Connect OpenAI Codex CLI to your fenbs board
Codex CLI takes MCP servers from its config. Add fenbs and Codex can read your board, file what it finds and move what it finishes from the terminal — under your role, signed.
Last checked
Connect
- Open Codex CLI’s config (
~/.codex/config.toml). - Add fenbs as an MCP server with the URL below, or with the bridge command if your version only takes stdio servers.
- Start Codex. If it opens a browser, sign in to fenbs, tick what it may do, and approve.
- Ask what is on your board.
config.toml — remote
[mcp_servers.fenbs] url = "https://fenbs.ai/api/mcp"
config.toml — through the bridge
[mcp_servers.fenbs]
command = "npx"
args = ["-y", "fenbs-mcp"]
env = { FENBS_TOKEN = "your-token" }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.