Connect cloud Devin to your fenbs kanban board
Admin only for setup: cloud Devin requires Manage MCP Servers permission. Add fenbs under Customize → MCPs, choose Personal access for separate sign-ins, and ask Devin what is on your kanban board.
Last checked
Admin only for this cloud Devin setup. You need Manage MCP Servers permission in your Devin organization. Other members can use Suggest MCP Integration to ask an administrator. Devin’s MCP guide (opens in a new tab) separates installing a server from signing in to it, and explains the difference between Personal and Organization access.
Connect Devin to fenbs
- In cloud Devin, open Customize → MCPs. Choose Add MCP, then Add custom MCP.
- Set Server Name to fenbs and add a short description. Choose HTTP and paste the URL below into Server URL.
- Choose Personal in the server’s Access setting for separate sign-ins. Click Save, then Test tools.
- When Devin gives you a sign-in link, open it and finish the fenbs sign-in.
- Start a new Devin session and ask: “What is on my fenbs kanban board?”
https://fenbs.ai/api/mcp
Set it up in fenbs for these steps beside the server address. Personal access lets each member connect their own fenbs account. Organization access shares one signed-in connection. Personal access is not a security boundary between people who can interact with one another’s Devin sessions, so choose it for separate sign-ins without assuming that it isolates every session.
What to save from a Devin session, and how the next AI picks it up
Before a coding session ends, ask Devin to save what it changed, what it checked, what remains unfinished and the next action in fenbs. Include the task reference, useful file locations and any decision you made. A short account of the result helps the next assistant distinguish finished work from a suggestion that was never tried.
At the start of the next session, ask Devin or another connected AI to read that saved work before editing. It can pick up the next action you recorded and check the current code. Saving the outcome in fenbs is a request you make; connecting the server does not by itself copy every session or instruction.
Reusable instructions inside Devin have their own place. Its Skills guide (opens in a new tab) documents procedures in Skills, while older Knowledge and Playbooks are moving there. Keep a reusable procedure separate from the record of what happened in one session. These connection steps are for cloud Devin; Devin Desktop has a separate page.
Never lose the work you did in an AI session
After a useful AI session, save it in fenbs: the key observations, findings, research and context. Then carry on from exactly where you left off, on any device and in any other AI. The next AI you connect reads it at the start of the session, so you never have to explain the same problem again.
Create a free accountFree for up to 5 people and 50 open tasks · No credit card · Works with Claude, ChatGPT, Cursor and more