Not every connector supports every type. Each connector’s page in the catalog shows the types it supports, and the Add connection button lists the available options.
For anything the catalog does not cover, you can integrate any API or connect your own custom MCP server.
What is an API?
API (Application Programming Interface) is a structured way for services or applications to communicate and share data with each other. It defines what you can ask for, what you’ll get back, and how to make the request.
API (Application Programming Interface) is a structured way for services or applications to communicate and share data with each other. It defines what you can ask for, what you’ll get back, and how to make the request.
Where to find connectors
All connectors live in one catalog, at lovable.dev/dashboard?connectors. You can open it from:- The Lovable dashboard sidebar navigation, under Connectors
- The
+menu next to the prompt input on the dashboard when starting a new project
- The
+menu next to the prompt input in the project chat - The project name menu at the top of the editor, under Project connectors
- The project toolbar, under More → Connectors
Which connection type do I need?
Use this table to pick the right connection type for what you’re building:
An app + chat connection already works in the chat, so you don’t need a separate chat connection for a tool your app is connected to. Choose a chat connection when the tool only offers one, or when you want Lovable to read your own account without sharing a credential with your workspace or your app.
You can also combine types. For example, connect Notion as a chat connector to build from your own specs, and as an app + chat connector so the finished app reads and writes your team’s Notion pages while people use it.
Hosting, backend, and AI
Hosting, a backend, and AI are built into Lovable, so there is no external account to connect. Lovable hosts your app and includes a built-in backend (Cloud) with database, authentication, storage, and edge functions. For AI features, Lovable AI gives your app AI capabilities without API keys or external accounts. You manage both from the same Connectors catalog as everything else. If you prefer to run your backend on Supabase, connect your own Supabase project instead.Managing connectors in your workspace
Workspace admins and owners control who can create connections for each connector, which is also how connectors are made available or disabled, and the defaults differ by plan. Who can use an individual connection is chosen by whoever creates it. See Manage connectors in your workspace for the full picture, and Integration security for how credentials are stored and how the connector gateway works. Once a connector is available, any builder with permission can create a connection and link it to a project.FAQ
What integrations does Lovable support?
What integrations does Lovable support?
Lovable has a built-in catalog of connectors covering payments, messaging, data, productivity, CRM, and more. Beyond the catalog, nothing is off limits:
- Custom MCP servers bring any MCP-compatible tool into the chat as context.
- Any API can be integrated into your published app. Describe the API in a prompt and Lovable writes the integration.
- Cloud and Lovable AI cover backend and AI needs without any external service.
What is the difference between the connection types?
What is the difference between the connection types?
The difference is whose account is used and where the connection works:
- An app + chat connection runs on one shared account. It works in the chat and in your published app, and everyone using the app shares it.
- A chat connection (MCP server) uses your own account and is personal to you. Lovable reads it as context while building, and it is never part of the published app.
- An app user connection belongs to each user of your published app. Every user signs in with their own account, and the app acts with their permissions.
Can Lovable integrate with any API?
Can Lovable integrate with any API?
Yes. Lovable can integrate with any external API, public or private. APIs without authentication can be called directly, while authenticated APIs are integrated securely using the built-in backend (Cloud), secrets, and Edge Functions to protect credentials. See Integrate any API.