Claude Lovable connectorWhat Claude can do in your Lovable account.
The Claude Lovable connector exposes 35 tools. 18 read your workspaces and projects, 11 build, publish or change something, and 6 are documented nowhere. Below: what Claude can ship from a chat, what spends credits, what it asks first and who can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can drive Lovable
Lovable builds web apps from plain-language prompts. With the connector, Claude talks to Lovable for you: it can start a project from your description, pass your follow-up requests to Lovable's own agent, read the resulting code and publish the app. You stay in one conversation instead of juggling the Lovable editor and a separate chat.
Go from idea to running app. create_project starts a project from your brief, and send_message relays each change you ask for to the Lovable agent, then waits for its answer.
See exactly what changed. get_diff, list_edits and read_file let Claude walk you through the code an edit touched, without opening the editor.
Ship and watch. deploy_project publishes the app and returns its live address, and get_project_analytics brings back visits, page views and traffic sources once it is out.
Where it stops: six listed tools have no description in any Lovable source, so this page says nothing about them. Publishing is refused while critical security findings remain open. Lovable says tool calls run live on your real projects, and building or messaging spends credits. Nothing starts by itself: Claude acts only while answering you, never on a schedule or after an event. For other app connectors, see our Integrations hub.
Five words before you connect
The terms around this connector, kept short.
- Connector
- A link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named capability the connector gives Claude. It picks which to call mid-answer, and the directory lists each one by name.
- Authorization
- The service's own login screen, where you grant the access Claude will use. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it changes something in an account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on, the piece that lets an assistant like Claude talk to an outside service.
Connect Lovable to Claude in three steps
- 01
Find Lovable in Claude
Open Claude's settings, go to Customize then Connectors, and look for Lovable. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector before members can each sign in.
- 02
Log in to Lovable
Click Connect on its row, then log in to Lovable in the window it opens. If the link breaks later, Disconnect and connect again. Lovable also describes a route from the chat itself: the + sign, then Connectors.
- 03
Read the authorization screen
Go through Lovable's authorization screen before accepting. It is Lovable's screen, not Claude's, and it sets what the access covers. Approval before each action remains Claude's default afterwards.
The 35 tools: 18 read, 11 write, 6 undocumented
Lovable gives Claude 35 tools: 18 that read your account, 11 that change something in it, and 6 no official source describes.
Names stay exactly as Claude shows them. The split comes from Lovable's tool reference, not from the names.
- 18 read
- 11 write
- 6 not documented
What Claude reads (18)
18 toolsTools that look at your account, projects, code, knowledge and analytics without altering them.
get_me
Returns the profile of the signed-in Lovable user along with the workspaces they belong to, which tells Claude whose account it is working in.
list_workspaces
Lists every workspace you belong to. Claude uses the result to pick the right workspace ID before looking for projects. get_me returns the same workspaces next to your profile.
get_workspace
Shows a workspace's details, including its plan, credit balance, member count and settings. Claude reads it when you need the state of the workspace rather than of one project.
list_projects
Searches and lists the projects of a workspace, with filters and full-text search, so Claude can locate one by name or by a keyword it contains.
get_project
Returns a project's details: editor link, preview link and a screenshot of its current state. The public address of a published app comes from deploy_project instead.
list_template_projects
Lists the project templates available to start from, so Claude can suggest one that fits your idea instead of a blank start.
get_message
Fetches the status and content of a message exchanged with a project's agent, typically to check on a request Claude did not wait for.
get_diff
Returns the unified diff of a message or a commit, the line-by-line view of what the code gained and lost. It pairs with list_edits, which pages through the project's history.
list_files
Lists all the files of a project at a given point of its code history, the map Claude needs before opening anything in particular.
read_file
Reads the contents of a single file at a given point of the code history, so Claude can explain it or go through it line by line with you.
list_edits
Lists a project's history page by page, the trail of everything that happened to its code over time. Claude reads it to tell you what came when.
get_workspace_knowledge
Reads the workspace knowledge, the custom AI instructions Lovable applies to every project in that workspace. That text is rewritten with set_workspace_knowledge, which replaces it in full.
get_project_knowledge
Reads the knowledge of one project, the custom AI instructions that apply to it alone and not to the rest of the workspace.
get_database_status
Checks whether Lovable Cloud is enabled for a project, which tells Claude if there is a database to query at all.
list_connectors
Lists every connector integration available in a workspace, whether standard, built in or MCP-based, and shows which ones are switched on.
list_connections
Returns the connector accounts already authenticated in a workspace, as opposed to the ones that are merely available. Claude can tell you which outside accounts are really linked.
get_project_analytics
Pulls historical analytics for a published project: visits, page views, bounce rate, visit length, broken down by page, source, device and country. It needs a start and an end date.
get_project_analytics_trend
Gives the real-time visit count and the short-term trend of a published project, the live view next to the historical one.
What Claude builds or changes (11)
11 toolsTools that create, publish, overwrite or open something in your Lovable account. No source describes their confirmation, so the general rule applies.
create_project
Approval: see the ruleStarts a new project from a build prompt handed to Lovable's agent, optionally from a template or a design system. It spends standard Lovable credits.
deploy_project
Approval: see the rulePublishes a project to Lovable's hosting and returns the live address. Lovable says who can reach that address depends on your Lovable plan and workspace settings.
remix_project
Approval: see the ruleCopies an existing project into a workspace. The source must be reachable from it: your own projects, templates, or projects open to public remixing.
set_project_visibility
Approval: see the ruleChanges who can access a project in the editor, matching the options of the share dialog. It governs editor access only, not who can visit the published app.
set_folder_visibility
Approval: see the ruleSwitches a folder between personal and workspace visibility, and the change carries over to every project inside it.
send_message
Approval: see the rulePasses a request to a project's own AI agent and waits for the reply. It can ask for a plan first, attach files, or return at once and be checked later. Each call spends credits.
set_workspace_knowledge
Approval: see the ruleWrites the workspace knowledge, the instructions that apply to every project, and replaces the existing text entirely rather than adding to it.
set_project_knowledge
Approval: see the ruleWrites the instructions of a single project, replacing whatever was there before in full.
enable_database
Approval: see the ruleTurns on Lovable Cloud for a project, the condition for query_database to have a database to query. Lovable says activation takes 30 to 60 seconds.
query_database
Approval: see the ruleExecutes an SQL query on a project's Lovable Cloud database. Lovable is explicit that it covers reads, writes and schema changes, with your full database permissions.
get_file_upload_url
Approval: see the ruleReturns a presigned address to upload a file that will travel as an attachment with a message to the Lovable agent.
Undocumented (6)
6 toolsListed on the directory sheet, absent from Lovable's documentation. We do not guess what they do from their names.
list_library_projects
This name appears on the directory sheet only. Lovable's MCP page, read on 1 October 2026, does not list it, and neither does the machine-readable tool reference Lovable says matches its server.
get_database_connection_info
Same situation: listed in the directory, missing from both Lovable references we read. We will not infer its purpose from its wording, so the page stops at that.
list_mcp_servers
No Lovable source we found mentions this tool. Lovable's documentation instead names connector tools that are absent from the sheet. Neither Lovable's MCP page nor its machine-readable reference, both read on 1 October 2026, describes it.
list_mcp_catalog
The directory publishes the name and nothing more. Neither the Lovable MCP page nor its tool reference describes it, so any description here would be a guess.
add_mcp_server
Listed on the directory sheet, undocumented by Lovable as of 1 October 2026. This page gives it no capability at all, because no official text grants it one.
remove_mcp_server
One more name the sheet shows and Lovable's references leave out. Until Lovable documents it somewhere public, this page has nothing reliable to add about it.
What Claude checks with you first
By default, Claude stops and asks for confirmation before each action it takes on an account in someone's place.
No source describes a confirmation for any of the eleven Lovable tools that build, publish, overwrite instructions, open a database or run SQL, so the default rule covers them all. That matters here: Lovable says calls run live, edit real projects and spend real credits. On Team and Enterprise, workspace owners decide whether members may let some actions through without a prompt, and they can restrict the connector for everyone. Lovable adds that the server inherits your Lovable permissions exactly, with nothing extra.
Which plans this works on
Plan availability is published for no single connector: 0 of the 819 directory sheets shows it.
The published rule is general. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and on Team and Enterprise an Owner or Primary Owner enables the connector before members connect. Lovable's documentation answers the question for its own plans, not Claude's; the limits section puts both side by side. For the live state on your account, check the Lovable sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls Lovable while it answers you; a new visit, a failed build or a teammate's edit does not start anything on its own.
Only Lovable documents this connector; no Claude help page covers it. Six tools on the sheet are missing from Lovable's references, while those references name other tools the sheet lacks. The partner badge is not a security audit, and Anthropic says on every sheet that it does not choose a publisher's tools or guarantee their behavior. Lovable also mentions a tool that imports a Claude design, available in Claude clients only and absent from the sheet.
Which plans can use the Lovable connector?
- Claude help center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise an Owner must enable each one first.
- Lovable MCP server documentation ↗October 2026 (read date)Lovable states its MCP server is available on all plans, meaning Lovable's own plans.
What this page followsThey do not talk about the same plans: Lovable opens its server to every Lovable plan, Anthropic states the rule on Claude's side for all connectors. Neither is outdated. For Claude's side, check the directory sheet on your own account.
Need help connecting Lovable to Claude?
A person reads every message.