Connect Claude to your fenbs board

Claude joins your board as a member over MCP: a browser sign-in, a role you choose, and its name on every change. No key to copy, nothing to paste into a config file.

Last checked

Connect in two minutes

  1. Sign in to fenbs. Your board is already there; add one task so there is something to see.
  2. In Claude, open the connectors (integrations) settings and choose to add a custom connector. Give it the URL below.
  3. Claude opens fenbs in your browser. Sign in if you are not already, tick what the assistant may do — read, write, comment — and press Approve.
  4. Back in Claude, ask it: “What is on my fenbs board?” It will call fenbs_whoami and then list your tasks.
The connector URL
https://fenbs.ai/api/mcp

That is the whole setup. fenbs speaks MCP with OAuth, so Claude signs in the way you do — in a browser — and is handed a token it keeps. You never see the token and never paste one anywhere. Custom connectors are available on Claude plans that allow them; if you cannot find the option, your plan or your organisation’s settings may not include it yet.

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.

Things people ask Claude to do on a board

  • “Read my AI context, then file these three bugs from my notes as Bug tasks in To Do.”
  • “Which In Progress tasks have not moved in a week? Comment on each asking for a status.”
  • “Summarise what changed on the board today, by person.”
  • “Move FE-014 to Completed and add a comment saying which pull request shipped it.”

Questions people ask.

Do I need Claude Desktop or the web app?

Either, as long as your plan lets you add custom connectors. Claude Code, the command-line tool, connects with one command and has its own page: /integrations/claude-code.

Is the assistant’s access separate from mine?

It is a separate token, listed by name under Settings, and revoking it does not touch your own sign-in. But it acts as you: it inherits your role on the board, narrowed by the scopes you ticked. It can never do something you could not.

Can I see what the assistant changed?

Yes. Every change it makes is recorded in the board’s history with its name, for example “Claude via Sam Ade”, so its work can always be told apart from a person’s.

Does connecting an assistant cost extra?

No. AI assistants are free on every plan, including the free personal board, and you can connect as many as you like.

Start with one thing.

Your own board is free. AI assistants cost nothing extra on any plan.