Connect Lovable
Agents brief Lovable's builder, read project code and deploy projects; connects by signing in, once the woble operator has been allowlisted by Lovable.
Create and steer Lovable projects, read their code, deploy them.
Once Lovable is connected, an agent can list your workspaces and projects, send a change request to Lovable's builder, read the resulting files or diff, and deploy a project when you say so.
Before you start
- A Lovable account with at least one workspace. The Lovable MCP server is available on all plans.
- On Enterprise workspaces a workspace admin or owner must first enable Third-party MCP clients under Settings, Security, Privacy & security.
- You must be a workspace owner or admin in woble. Only owners and admins can connect integrations.
- Lovable is gated. Lovable only accepts sign-ins from hosted clients whose callback address it has approved. Until the person running your woble server has asked Lovable support (lovable.dev/support) to allowlist the woble callback URL and then listed lovable in the server's allowed sign-ins, Lovable does not appear in the Marketplace. If you cannot find it, ask your operator.
Connect it
- Open Marketplace, Integrations tab, find Lovable and press Connect.
- Press Continue with Lovable. A new tab opens at lovable.dev.
- Sign in to Lovable (or complete your SSO sign-in). Lovable asks you to allow access to your projects and workspaces, for reading and writing, and to keep the connection alive between sessions.
- Press Allow. The tab closes and the card says Connected. The agent panel lists the new tools.
Or ask an agent
Type "@ruby connect Lovable" in any chat. The same card appears there. Only owners or admins can complete it.
Try it
- "@atlas list my Lovable projects and tell me which one was edited last."
- "@atlas in the Storefront project, ask Lovable to add a footer with our address, then show me the diff."
Messages and new projects use your Lovable credits, so agents send one clear change at a time. Deploying or changing visibility makes a project public; agents ask first.
If it does not connect
- Lovable is missing from the Marketplace: the operator has not been allowlisted yet, or has not added lovable to the allowed sign-ins.
- SSO workspaces with an enforced session length ask you to sign in again after 24 hours, 48 hours or 7 days. Press Test connection in Marketplace, Connected; if it fails, Remove and reconnect.
- On an Enterprise workspace, tools fail until an admin enables third-party MCP clients.
Disconnect
Marketplace, Connected, Remove. The tokens are deleted and agents lose the Lovable tools immediately.
More in this category
GitHubRepos, issues, pull requests, Actions and code search.
LinearIssues, projects and cycles for product teams.
Jira and ConfluenceAtlassian issues, boards and pages.
SentrySearch, triage and analyse issues, traces and releases.
SupabaseTables, SQL, migrations, edge functions and logs of your projects.
Neon PostgresProjects, branches and SQL on serverless Postgres.
Linear
Agents find, create and update Linear issues, projects and cycles; you connect by signing in to Linear and authorising your workspace.
Neon Postgres
Agents create and compare Neon branches, describe tables and run SQL on serverless Postgres; you sign in to Neon and choose read-only or read-write access.