KBAISE/ for lovable
Library
Docs

MCP registries

about 5 minBuildingchecked 5d agoOfficial page
The short version

You can connect a shared directory of external tools to your workspace so members can browse and link them in a few clicks. Each team member connects tools using their own individual login credentials.

Workspace admins and builders who want a shared directory of approved tool servers instead of pasting server links manually.

Do this, in order

  1. 1

    Make sure Remote MCP connectors are enabled in your workspace Privacy and security settings.

    If this setting is turned off by an admin, the MCP registries area will not appear at all.

  2. 2

    Open Connectors in your dashboard, scroll to the bottom, and click Add registry.

    This opens the configuration form where you register your directory.

  3. 3

    Enter the Registry URL, an optional display name, and a bearer token if the directory requires one, then click Connect.

    This saves the directory so everyone in the workspace can view available servers.

  4. 4

    Select Browse + add server on the registry card to see the full list of tools.

    You can search and select tools without hunting for their individual web addresses.

  5. 5

    Click Connect next to a server, choose your authentication method, and select Add & authorize.

    This links the tool as a chat connector under your personal account so you can use its data in project chats.

Paste this into your project

List all active chat connectors and tools available to this chat, and explain how we can use them to help build this application.

Words decoded

MCP registry
A shared directory or catalog of external tools that AI models can look up and connect to.
Bearer token
A secret password-like text key used to prove your permission to access a private service.
OAuth
A secure sign-in process that lets you grant permission through an external provider without typing your password directly into the app.

Where people get stuck

  • Connecting a server only connects it for your own account; other team members must connect it individually using their own credentials.
  • Servers behind firewalls that require Lovable static IPs cannot be configured through a registry; you must add those directly as custom server URLs.
  • Viewers and collaborators cannot connect servers; you must have an Editor role or higher in the workspace.
  • Local servers shown in a registry cannot connect through a web browser and require the Lovable Desktop app.

The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.