Lovable Integrations: MCP Server, API, GitHub, Stripe and n8n

Lovable plugs into other software through five separate layers, and each one has its own plan gate and its own bill. Git sync with GitHub, GitLab or Bitbucket Cloud, the connector catalog, custom connectors and the Lovable MCP server all work on the Free plan. Built-in Stripe or Paddle payments start on Pro. The Lovable API, workspace API keys and Events & Hooks need Business, and Business with 100 credits costs $50 per month billed monthly or $42 per month billed annually, per workspace. The catch sits in the meter. Managed connectors, agent tool calls and a live app's backend traffic all draw on the same credit balance you build with.

Git sync mirrors your code both ways, with a few hard edges

Every plan, Free included, can sync a project two ways with github.com, GitLab (hosted or self-managed) or Bitbucket Cloud ^[1]. Lovable pushes each change, and commits pushed to the synced branch flow back into the editor. Each project gets a brand-new private repository, because Git sync cannot attach to one you already have. Starting from existing code means importing a ZIP as a new project, which Lovable rebuilds on TanStack Start. Only one branch syncs at a time. When branch protection rejects a push, Lovable parks the work on a lovable-sync branch for you to merge.

The repository's contents shape any exit plan. You get source, config and database migration files, but not database records, uploaded files, secrets or connector connections. Paid plans add a codebase ZIP download, so GitHub is not required just to hold a copy. Disconnecting leaves the repository in place. Reconnecting creates a fresh one. GitHub Enterprise Server and GitHub Enterprise Cloud with data residency are Enterprise-only, and recording members' emails in commits is a Business setting.

Shared, personal or per-user: three ways a tool can connect

Lovable sorts third-party tools into three connection types, and the type decides who acts and whose account answers. An app + chat connector runs on one shared account. It works in the project chat while you build and inside the published app for every visitor; Stripe, Slack, Google Workspace, Microsoft 365, Salesforce, HubSpot and Resend arrive this way. A chat connector is an MCP server, such as Linear, Notion, Miro or n8n, used only in chat by the person who connected it. It never ships with the app.

The third type, the app user connector, lets each person using your published app sign in to their own Google, Microsoft, Slack, Salesforce, Notion, GitHub or Snowflake account, so the app sees only their data. You register an OAuth application with each provider yourself. Tokens stay encrypted in Lovable's connector gateway. For anything missing, a workspace admin or owner can define a custom connector for any HTTPS REST API on any plan, up to 200 per workspace. The gateway allows 1,000 requests per minute per connector per project, and services inside a private network are out of reach.

Connecting a tool costs nothing by itself. Credits move when Lovable writes code for it, and when you pick the Managed by Lovable option for Perplexity, Firecrawl, Parallel or LlamaParse, which bills usage as Run credits. Managed Perplexity search uses 20 credits per 1,000 searches, or 10 on Business, where each credit is dearer. Twilio, Resend and other services connected with your own keys bill you directly. Underneath it all, a live app's backend, AI and managed-connector usage comes out of the balance you build with, so visitors spend the owner's credits (how the balance works).

The MCP server lets outside assistants drive Lovable

The Lovable MCP server at mcp.lovable.dev runs opposite to chat connectors. ChatGPT, Claude, Claude Code, Cursor, VS Code or another OAuth-capable client can create projects, send build messages, read code, query the database and deploy. It is available on every plan, Free included ^[2]. OAuth is the only way in. Only create_project and send_message spend standard credits; the other tools are free. Buyers comparing the category should know Base44 keeps MCP connections for its Builder plan and up, as our Base44 vs Lovable comparison explains.

Two cautions belong here. The query_database tool runs SQL with your full database permissions, writes and schema changes included. And deploy_project refuses to publish while the latest security scan shows unresolved critical findings. Third-party MCP access is always on for Free and Pro, on by default on Business where admins can switch it off, and off by default on Enterprise until an admin or owner enables it. Agent integrations flip the direction again: Lovable hosts an MCP server for a published app, so assistants can call the actions you publish. Public apps get this on every plan. Tool calls count as the owner's backend and AI usage.

The API, webhooks and hooks sit behind Business

The REST API at api.lovable.dev launched in September 2026 and manages what already exists: list and update projects, publish and unpublish, read analytics over ranges up to 365 days, pull security scan results and create one-hour preview embeds. It cannot create or edit apps with AI, and its current endpoints use no build credits. Workspace API keys require Business or Enterprise plus an owner or admin role ^[3]. Each key is bound to one workspace, carries fixed scopes and can carry its own monthly cap on AI build credits.

Events & Hooks, also Business and up, send signed HTTPS webhooks. There are four events (a project created, published, transferred or deleted) and one hook that asks your service to allow or deny each message before submission. That hook has sharp edges. It gets five seconds and is never retried. Under the default failure setting, every message in the workspace is blocked while your endpoint is down. Save the signing secret immediately, since it is shown once and cannot be rotated.

Taking money: built-in payments or your own Stripe key

Built-in payments start on Pro, which costs $25 per month billed monthly or $21 per month billed annually with 100 credits, per workspace. Lovable creates and manages a Stripe or Paddle account for the project, for subscriptions and one-time sales of digital products. Lovable adds no fee on top. Through Lovable, Paddle charges 5.0% + $0.50 per transaction, or a flat 10% under $10, and acts as merchant of record for tax and invoices ^[4]. Stripe charges its standard rates.

Only one provider runs per project, and switching moves no products, prices or subscriptions. PayPal has no native support. On Free, the route is your own Stripe account: paste a restricted or secret key and Lovable stores it as a backend secret. One key works at a time, so a live key turns preview payments into real ones. A project uses built-in payments or its own Stripe, never both. Physical goods point instead to Lovable's Shopify integration.

Figma, n8n, Slack and the automation tools

Figma designs come in three ways: the plugin, which needs at least a Dev seat in your Figma organization; a .fig upload, which carries colors, typography and frame structure but not interactive components; and the Figma MCP, which runs only through the Lovable desktop app and needs a Figma Dev or Full seat. Exporting is free. Building from the design spends credits. The n8n connector needs a paid n8n Cloud workspace or a self-hosted instance at a public HTTPS address, and n8n bills the workflow runs. Zapier and Make instead reach your app through an edge function acting as their endpoint or webhook.

Lovable in Slack works on every plan: mention @Lovable in a channel or direct message to create or update projects. One Lovable workspace pairs with exactly one Slack workspace, only teammates matched by verified Slack email can use it, and builds spend build credits counted against the sender. The Slack connector inside apps is a separate thing, limited to 100 API requests per minute per project. Telegram is for Free and Pro only.

The bottom line

Lovable's integrations are broad on Free and gated where control and automation begin. Git sync, catalog and custom connectors and the MCP server cost nothing to switch on, built-in payments wait for Pro, and the API, webhooks and message hooks wait for Business. The real cost is metered: managed connectors, agent integrations and a live app's traffic all draw on one credit balance. List the connections your published app will call, set usage limits before launch (Pro and up), and plan your exit knowing that data, secrets and connections stay behind when the code leaves.