Skip to main content
A custom MCP server is any remote server that supports the Model Context Protocol and is not already a prebuilt connector in the Lovable catalog. Connect one as a chat connector (MCP server), and Lovable can read from it as live context while you build: internal CRMs, private APIs, company knowledge bases, or niche third-party tools. Custom MCP servers are available on all plans. Like all chat connections, they are personal to you, and they are never part of your published app. If your published app needs to call a service while people use it, use an app + chat connector or integrate the API directly.
Explore remote MCP servers, a curated list of high-quality remote MCP servers compatible with Lovable.

​
How to connect a custom MCP server

To connect a custom MCP server, you need the server’s URL and, depending on the server, its credentials:
1

Open the custom MCP form

Open Connectors, scroll to the bottom of the All view, and select the Custom card labeled MCP (“Connect your own MCP”). See Where to find connectors for every place you can open the catalog.
2

Check the workspace suggestions

If someone in your workspace already connected a server, pick it from the Used by others in this workspace suggestions. This fills in the server details for you, and you can skip straight to authentication.
3

Name the server

Enter a clear Server name (for example, Internal CRM or Analytics API).
4

Enter the server URL

Enter the Server URL where Lovable can reach your MCP server, for example https://mcp.example.com.
5

Choose authentication

  • OAuth (default): Lovable uses OAuth by default. After you click Add & authorize, you’re prompted to authorize.
  • Bearer token or API key: For servers that don’t support OAuth, authenticate with a bearer token or API key.
  • No authentication: Connect without credentials if the server doesn’t require authentication.
6

Add the server

Click Add & authorize (OAuth) or Add server. The custom MCP server now appears in your list of chat connectors and can provide contextual data for builds.
To confirm the connection works, ask Lovable something the server can answer, for example:

​
Manage custom MCP servers

Custom MCP servers follow the same workspace controls as other chat connectors, through two settings:
  • The Custom MCP row (“Allow members to connect their own MCP servers”) in Connectors → Admin settings → Chat connectors turns custom MCP servers on or off for everyone. It governs them as a group, so individual custom MCP servers that members have connected do not appear in the admin table.
  • Remote MCP connectors in Privacy & security turns all chat connectors on or off for the workspace, custom MCP servers included.
See Chat connector controls for all chat connector governance settings.

​
FAQ

All plans. Custom MCP servers are chat connectors, which are enabled by default everywhere, including on Enterprise workspaces. A workspace admin can turn them off with the Custom MCP setting described in Manage custom MCP servers.
No. Chat connections, including custom MCP servers, only give Lovable context while building. For functionality in your published app, use an app + chat connector or ask Lovable to integrate the API directly.
By design. The Admin settings table lists catalog connectors only. Custom MCP servers are controlled as a group through the Custom MCP row in Connectors → Admin settings → Chat connectors.
No. Chat connections are per-user. Others in your workspace can see the server in the Used by others in this workspace suggestions and connect it themselves with their own credentials.