Lovable

Name: Lovable MCP Server
Availability: InStock
Author: Lovable

HIPAA CompliantSOC2 ReadyISO 27001 Ready

Developer Tools35 tools

Create, build, inspect and deploy Lovable apps from your AI assistant. 35 tools, OAuth, and a deploy_project tool that publishes a live public site.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 18 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Lovable via MCP

https://mcp.lovable.dev

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect Lovable once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Lovable Tools & Capabilities (35)

get_me

list_workspaces

get_workspace

list_projects

get_project

create_project

deploy_project

remix_project

set_project_visibility

set_folder_visibility

list_template_projects

list_library_projects

send_message

get_message

get_diff

list_files

read_file

list_edits

get_workspace_knowledge

set_workspace_knowledge

get_project_knowledge

set_project_knowledge

get_database_status

enable_database

query_database

get_database_connection_info

list_mcp_servers

list_mcp_catalog

list_connectors

list_connections

add_mcp_server

remove_mcp_server

get_project_analytics

get_project_analytics_trend

get_file_upload_url

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

This connector publishes to the public internet. deploy_project puts a real site on a real lovable.app URL. On Free and Pro plans Lovable states website access cannot be restricted, so anyone with the link can reach it. Restricting the audience requires Business or Enterprise.
The connection is account-wide, not project-scoped. Lovable's own warning states the connected client can list, read and edit every project you have access to. There is no per-project narrowing at the consent screen, and no scope in the descriptor expresses one.
query_database runs SQL with your full database permissions. Lovable names reads, writes and schema changes. Nothing in the published surface limits it to SELECT.
Two tools spend credits, and the guard rail is a notification, not a cap. create_project and send_message bill. The credit check-in pauses a run at a threshold — 20 credits by default — but Lovable calls it a notification threshold that a run can overshoot, and the feature is in beta. Auto top-up will buy more credits automatically if you have enabled it.
A Free workspace's build allowance is small. Lovable grants 5 daily build credits, up to 30 per month, so a handful of send_message calls can exhaust a day.
The directory's 35 names omit at least five write-capable tools the vendor documents, including delete_workspace_skill, which Lovable describes as not undoable except by recreating the skill. Three published lists give 35, 41 and 33 as of the dates above, and their union is 48. Treat no single count as the surface.
Only five client families can complete the OAuth flow. Lovable names ChatGPT, Claude, Claude Code, Cursor and VS Code, and states other MCP clients cannot authenticate at this time. A gateway outside that list will not connect regardless of configuration.
The refresh-token scope is offline, not offline_access. A client hardcoding the conventional spelling gets no refresh token and will re-authenticate unexpectedly.
workspaces:create is grantable but has no tool behind it in any of the three lists we collected. Grant narrowly; a scope on a consent screen is not evidence of a matching capability.
Lovable's own pages disagree on the server's status. The MCP page presents general availability; the Lovable API overview calls it a Research Preview. Both were read on 2026-08-18.
Deleting a Lovable project is permanent. Lovable's remix documentation states there is no way to recover or remix a deleted project afterwards. No delete-project tool appears in any of the three lists, but the irreversibility bounds what a remix-based backup can save you from.
We read no schemas or annotations. Our checks were anonymous protocol requests that returned an authentication challenge, plus reads of public well-known documents and public documentation. We never signed in, never called a tool, never created a project and never deployed anything.

Frequently asked questions

All plans. Lovable's MCP documentation states the server is available on every plan, including Free. On Enterprise workspaces a workspace admin or owner must first enable Third-party MCP clients under Settings, Security, Privacy and security. Lovable's settings reference records that control as disabled by default on Enterprise and enabled by default on Free, Pro and Business.

No. Lovable's MCP documentation states that API key authentication is not currently available and OAuth is the only supported way to connect. We confirmed the posture on 2026-08-18: an anonymous request to the endpoint returned HTTP 401 with a Bearer challenge pointing at the server's OAuth resource descriptor, so nothing connects without a browser sign-in.

Yes, for two tools. Lovable's MCP documentation states standard credits apply to create_project and send_message calls, and that other tools are free. Lovable's credits reference prices Plan mode at 1 credit per message and Build mode by complexity, with illustrative examples from 0.50 credits for a styling change to 2.00 for a landing page.

It deploys a snapshot of the project to a live URL on lovable.app and returns that URL. Lovable's publishing documentation states each publish deploys only the current version, that later changes are not pushed automatically, and that a published site stays live indefinitely with no expiry and no automatic unpublishing for inactivity.

On Free and Pro plans, yes. Lovable's publishing documentation states website access cannot be restricted on those plans, so anyone with the link can visit a published app. Business and Enterprise workspaces can set a default website access policy and restrict the audience to workspace members, groups or named people.

Yes. Lovable documents three ways to unpublish: Project settings, the Publish dialog overflow menu, or selecting several projects on the dashboard. Once unpublished the live URL becomes inaccessible and the project remains in the editor. Unpublishing is not among the 35 directory tool names, so it is a UI action rather than an agent one.

Every project you can reach. Lovable's own warning states the connected client has the same account access you do, so it can list, read and edit every project you have access to, and that scope is your full account rather than one project. Lovable also states the server inherits your user permissions exactly, with no additional surface area.

Yes, with full permissions. Lovable's documentation states query_database runs SQL with your full database permissions covering reads, writes and schema changes. The vendor's machine-readable tool reference lists SELECT, INSERT, UPDATE, DELETE and DDL as supported, so an agent can alter or drop tables in a project's Cloud database.