Do I need Lovable Business for custom MCP?

No. Custom remote MCP chat connectors are available on all plans. Your workspace must allow custom MCP servers, and an admin can disable that option.

Can my teammates use my fenbs connection?

No. Lovable chat connectors are personal to the person who connects them. Each teammate needs their own connection.

Will my published app get this connector?

No. A chat connector is used in your conversations with Lovable. It is separate from integrations in the app you publish.

Does Lovable still call its saved guidance Knowledge?

The current name is Instructions. Workspace and app-specific guidance are chiefly plain-text fields, not a required file named knowledge.md. Use them for Lovable guidance and save shared conclusions in fenbs for the next connected assistant.

Connect Lovable to your fenbs kanban board

Connect fenbs to Lovable as a personal chat connector on any plan, where your workspace allows custom MCP. Save the useful results of a build so the next connected AI has a place to start.

Last checked October 28, 2026

Connect Lovable to fenbs

Lovable’s chat connectors connect your own tool accounts to its chats. Custom MCP servers are available on all Lovable plans, subject to workspace admin controls. Each person connects their own account; teammates cannot use your personal connection.

Open Connectors in Lovable. Choose Add custom, then MCP server.
Name the server fenbs, keep Direct connection and paste the URL below into Server URL.
Keep OAuth. Choose Add & authorize, sign in to fenbs and approve.
Open the chat for your app, or Chats, and ask: “What is on my fenbs kanban board?”

The MCP server URL

https://fenbs.ai/api/mcp

If MCP server is grayed out, ask your workspace admin to allow Custom MCP. Lovable’s custom MCP guide (opens in a new tab) covers the connection and its admin controls (opens in a new tab) explain workspace restrictions. Set it up in fenbs.

What to save from a Lovable session, and how the next AI picks it up

A useful stopping point is more than “the build is done.” Ask Lovable to save what changed, what you approved, what was checked and what remains in fenbs before you leave. Include the reason for a choice that the next assistant might otherwise undo.

The change you asked for and how far it got.
The result of the preview or a check, with any unfinished work.
An approach that failed and what you learned from it.
The next step, including anything that needs your answer.

When you return, ask the connected AI to read fenbs first. The saved account gives Lovable, or another connected assistant, the conclusions it needs to continue. Lovable also has Instructions (opens in a new tab), formerly Knowledge, for guidance inside a workspace or app. Those fields guide Lovable; save the conclusions you want the next connected AI to read in fenbs.

How fenbs helps

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 account

Free for up to 5 people and 50 open tasks · No credit card · Works with Claude, ChatGPT, Cursor and more

Where the connector works

The connection is for Lovable’s chats. It does not ship fenbs access inside a published app. Lovable’s chat connector guide (opens in a new tab) makes that distinction: connecting your own tools for the conversation is separate from adding an integration to the app you are building.