| Method | Best for | How it works |
|---|---|---|
| MCP Server | AI-driven exploration, prototyping from live schemas | Lovable queries Nekt in real-time through the MCP protocol |
| Supabase | Production apps that need a live database | Nekt sends data to the Supabase instance your Lovable app already uses |
| Google Sheets | Quick setups, read-only data, non-technical teams | Nekt sends data to a spreadsheet that Lovable can read from |
| Data API | Custom integrations, on-demand SQL queries from app code | Your Lovable app queries Nekt directly via HTTP using SQL |
MCP Server
Connect Lovable directly to Nekt’s MCP Server so the Lovable Agent can explore your schemas, preview data, and generate apps grounded in your actual tables.Requires a paid Lovable plan (for custom MCP servers) and a paid Nekt plan (for MCP Server access).
Setup
Activate the MCP Server in Nekt
Go to Integrations > MCP Server in Nekt and enable the server. See the MCP setup guide for detailed instructions.
Add Nekt as a custom MCP server in Lovable
In Lovable, go to Settings > Connectors > Personal connectors and click New MCP server.
- Server name — enter
Nekt - Server URL — paste the Endpoint from the MCP Server page in Nekt
Authenticate
Choose one of the following methods:OAuth (recommended) — Select OAuth and click Add & authorize. You will be redirected to log in with your Nekt credentials and select a token.Bearer token — Select the bearer token option and paste a token from the MCP Tokens section in Nekt.
Tokens created during the OAuth flow use the creating user’s permissions by
default. Tokens created manually can be scoped to specific tables for
fine-grained access control.
Example prompts
| Scenario | Prompt |
|---|---|
| Explore available data | List the tables available in Nekt and describe their schemas. |
| Build a dashboard | Build a dashboard that shows monthly revenue trends using the orders table from Nekt. |
| Prototype from real data | Preview the products table and build a product catalog page based on its structure. |
Supabase Destination
If your Lovable app already uses Supabase as its database, you can send processed data from Nekt directly into the same Supabase instance. Your app reads from Supabase as usual — Nekt keeps the data fresh on a schedule.Setup
Get your Supabase connection details
In your Supabase project, click Connect in the top navigation bar and select the Session pooler tab. Copy the host, port, user, password, and database values.
Add a Supabase destination in Nekt
Go to Destinations in Nekt, click Add destination, and select Supabase. Enter the Session pooler credentials from the previous step and choose a load method (append, upsert, or overwrite).See the full Supabase destination guide for details on IP whitelisting, SSL, and load methods.
Select the tables to send
Choose which tables from your Catalog should be sent to Supabase. Define a primary key for each table and set a schedule for how often data should be refreshed.
When to use this method
- Your Lovable app needs to query data at runtime (filters, search, pagination).
- You want Lovable to work with production-ready tables managed by Nekt.
- You need scheduled refreshes so the app always has current data.
Google Sheets Destination
For simpler setups, you can send data from Nekt to a Google Sheet and have Lovable read from it. This works well for read-only data, small datasets, or teams that want to get started quickly.Setup
Add a Google Sheets destination in Nekt
Go to Destinations in Nekt, click Add destination, and select Google Sheets. Paste the link to your spreadsheet and grant Editor access to the email address provided by Nekt.See the full Google Sheets destination guide for details on tab mapping and cell range configuration.
Select the tables to send
Choose which tables from your Catalog should be sent. Each table is written to a separate tab in the spreadsheet. Set a schedule for how often data should be refreshed.
When to use this method
- You need a quick, low-effort setup without database configuration.
- The data is read-only and doesn’t require filtering or pagination at runtime.
- Non-technical team members want to review or edit the data in the spreadsheet before it reaches the app.
Data API
If your Lovable app needs to query Nekt data on demand from its own code, you can use the Data API. Your app sends a SQL query over HTTP and receives the results as a downloadable file (Parquet or CSV).Requires a paid Nekt plan and an API key created in your workspace settings.
Setup
Create an API key in Nekt
Go to Workspace Settings > API Keys in Nekt and create an API key.
Call the Data API from your Lovable app
In your Lovable prompt, ask the agent to add a server-side function (e.g. a Supabase Edge Function) that calls the Nekt Data API endpoint with a SQL query. The API returns a download link to the results.Example: Add an Edge Function that queries the
orders table from Nekt using the Data API and returns the results as JSON.See the full Data API documentation for endpoint details and output formats.When to use this method
- Your app needs to run arbitrary SQL against Nekt data at runtime.
- You want on-demand queries rather than scheduled syncs.
- You are building a custom integration that doesn’t fit the MCP, Supabase, or Sheets patterns.