<head>
<script type=“application/ld+json”>
{{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "What integrations does RShift Sites support?", "acceptedAnswer": {"@type": "Answer", "text": "RShift Sites has a built-in catalog of connectors that can work as app + chat connectors (used by your published app and in the project chat), chat connectors (context for RShift Sites while building), and app user connectors (each end user connects their own account). Beyond the catalog, workspace admins can create custom connectors for any REST API, and RShift Sites can integrate any external API."}}, {"@type": "Question", "name": "What is the difference between the connection types in RShift Sites?", "acceptedAnswer": {"@type": "Answer", "text": "An app + chat connection runs on one shared credential and works in the project chat and in your published apps. A chat connection (MCP server) is personal to you and only gives RShift Sites context while building. It is not part of the published app. An app user connection lets each end user of your published app sign in with their own account."}}, {"@type": "Question", "name": "Can RShift Sites integrate with any API?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. RShift Sites 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."}}]}}
</script>
</head>
Connectors link RShift Sites to the external tools and services you already use, such as Slack, Notion, HubSpot, and Google Workspace. Browse the catalog, connect a tool once, and RShift Sites handles authentication, credentials, and requests for you.
All connectors live in one catalog. What changes is how you connect it. When you select a connector and click Add connection, you choose the connection type it supports:
| Connection type | What it does | Learn more |
|---|---|---|
| App + chat connector | Adds capabilities and external services that your published app can call, like sending messages or reading data. Runs on one shared account, and RShift Sites can use it in the project chat and in Chats too. | App + chat connectors |
| Chat connector (MCP server) | Personal to you. RShift Sites reads your own tool accounts as context in the project chat and in Chats. Not part of the published app. | Chat connectors |
| App user connector | Each end user of your published app connects their own account, and the app acts with their permissions. | App user connectors |
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 have three options: workspace admins can create a custom connector that adds any REST API to the catalog for the whole workspace, you can integrate any API directly into your app, or you can connect your own custom MCP server for chat context.
Where to find connectors
All connectors live in one catalog, at lovable.dev/dashboard?connectors. You can open it from:
- The RShift Sites dashboard sidebar navigation, under Connectors
- The + menu next to the prompt input on the dashboard when starting a new project
- The sidebar inside a project, under Connectors
- The + (Chat actions) menu in a chat, under Add context → Connectors
The top right of the catalog has two controls. A sort menu orders the connectors by Popular, A to Z, or Z to A. The + button adds something the catalog does not already list: choose MCP server to connect your own MCP server, Custom connector to create a connector for an API, or MCP registry to add a directory of MCP servers. The Custom connector and MCP registry options are for workspace admins and owners. Both controls appear on the catalog home, not while you are searching or viewing a single connector.
Inside a project, More → Connectors gives you one place to see everything connected to that project. It shows the connections your app uses under Project connections, and the MCP servers your project can access under MCP connectors. To browse the full catalog from there, select All connectors. You can reach More → Connectors from:
- The + menu next to the prompt input in the project chat, under Add context → Project connectors
- The project toolbar, under More
Which connection type do I need?
Use this table to pick the right connection type for what you’re building:
| Use | If you want to |
|---|---|
| App + chat connector | Give your published app a capability every visitor shares, like posting to your team’s Slack or reading a Google Sheet. RShift Sites can use the connection in the project chat and in Chats too. |
| Chat connector (MCP server) | Let RShift Sites read your own Notion docs, Linear tickets, or Miro boards in the project chat and in Chats, without sharing your account with anyone or your app. |
| App user connector | Let each user of your published app sign in with their own account, like Gmail or Salesforce, and see only their own data. |
| Custom connector | Turn a REST API the catalog doesn’t cover, like an internal service, into an app + chat connector. An admin defines it once, and the whole workspace can connect to it. |
| Custom MCP server | Bring a tool the catalog doesn’t cover into the project chat and Chats, like an internal CRM or a private API with an MCP server. |
| Any API | Add functionality to your published app from any external service, even one with no connector at all. RShift Sites writes the integration code for you. |
An app + chat connection already works in the project chat and in Chats, 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 RShift Sites 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 RShift Sites, so there is no external account to connect. RShift Sites hosts your app and includes a built-in backend (Cloud) with database, authentication, storage, and edge functions. For AI features, RShift Sites 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 RShift Sites support?
RShift Sites has a built-in catalog of connectors covering payments, messaging, data, productivity, CRM, and more. Beyond the catalog, nothing is off limits:
- Custom connectors turn any REST API into an app + chat connector for your workspace.
- Custom MCP servers bring any MCP-compatible tool into the project chat and Chats as context.
- Any API can be integrated into your published app. Describe the API in a prompt and RShift Sites writes the integration.
- Cloud and RShift Sites AI cover backend and AI needs without any external service.
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 project chat, in Chats, 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. RShift Sites reads it as context while building, and it is not 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.
The decision table above shows when to pick each one.
Can RShift Sites integrate with any API?
Yes. RShift Sites 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.