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:Open the custom MCP form
Name the server
Choose how Lovable reaches the server
Enter the server URL
https://mcp.example.com.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.
Add the server
Lovable static IPs
By default, Lovable reaches a custom MCP server over a Direct connection, and requests do not come from a fixed set of IP addresses. That works for servers on the public internet, but not for servers behind a firewall that only accepts traffic from allowlisted IPs, such as on-premises deployments. Lovable static IPs is a per-connection option for custom MCP servers that routes all Lovable traffic to the server through Lovable’s published static egress IP ranges. Allowlist these ranges in your firewall, and Lovable can reach the server:- IPv4:
185.41.150.0/28and185.41.150.16/28 - IPv6:
2a07:8241:fca:1000::/56
- It works with every authentication type. OAuth, bearer token, and no authentication all work with Lovable static IPs.
- You can only choose it for custom MCP servers. Featured connectors from the catalog don’t offer the option.
- Enterprise only, enabled per workspace. Lovable static IPs requires an Enterprise plan, and Lovable must also enable the option for your workspace. If you don’t see Lovable static IPs in the Connection dropdown, contact your Lovable account team.
- Add the server by URL, not from a registry. Servers connected from an MCP registry always use a direct connection, and the Connection dropdown doesn’t appear for them.
- The choice is fixed when you add the server. Lovable checks the option when you create the connection, and the connection keeps its setting from then on. If the option is later disabled for your workspace, existing static-IP connections keep working, but you can’t create new ones. To switch an existing connection between Direct connection and Lovable static IPs, remove the server and add it again.
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”), the last row in Connectors → Admin settings → Chat connectors, turns custom MCP servers on or off for everyone. It is a workspace-wide setting rather than a connector, so the 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.
FAQ
Which plans support custom MCP servers?
Which plans support custom MCP servers?
Can my published app use a custom MCP server?
Can my published app use a custom MCP server?
Why doesn't my custom MCP server show up in Admin settings?
Why doesn't my custom MCP server show up in Admin settings?
Which IP addresses does Lovable connect to my MCP server from?
Which IP addresses does Lovable connect to my MCP server from?
185.41.150.0/28, 185.41.150.16/28, and 2a07:8241:fca:1000::/56, which you can allowlist in your firewall.Why don't I see the Lovable static IPs option?
Why don't I see the Lovable static IPs option?
Can other people in my workspace use my custom MCP connection?
Can other people in my workspace use my custom MCP connection?