Independent review. Unpaid; no partnership with Lovable. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Build and iterate on websites or apps from natural-language instructions, then review the code and behavior. Lovable exposes an MCP server to external AI clients; its separate management/deployment API requires Business or Enterprise for project and workspace operations.
The Ion perspective
The five-point review
Judgment, not a score. Documentation checked 2026-10-18.
Value
Build and iterate on websites or apps from natural-language instructions, then review the code and behavior. Lovable exposes an MCP server to external AI clients; its separate management/deployment API requires Business or Enterprise for project and workspace operations.
Differentiation
Documented fit: Prototypes and internal tools; Founders validating an idea. Uniqueness is not established.
Replaceability and switching
Compare Cursor, Framer. Not drop-in replacements. Export completeness and migration effort remain unverified.
Ease and technical aptitude
Consider the fit limits: Complex production systems without code review. Setup effort has not been scored.
Interoperability and portability
See documented MCP, API and import routes below. Import does not prove export; API access does not prove a complete migration path. Check action scope, plans and portability.
Create and edit Lovable projects from ChatGPT, Claude or Cursor through the MCP server source ↗
Deploy existing projects and inspect workspace information through the Business/Enterprise API source ↗
In depth
Plans
Base Pro costs US$25 monthly or US$250 annually; Business costs US$50 monthly or US$500 annually. Each starts with 100 monthly subscription credits shared by workspace members. Free grants five daily build credits, capped at 30 per month. Hosting and app AI consume usage too; regional plan terms and credit values can differ. source ↗
Live account access
MCP operates on real projects, can span authorized workspaces and consumes credits for creation/editing. Database tools can write data and change schemas. Deployment can make an app reachable outside your team, so inspect its access setting before publishing. Enterprise workspaces must first enable third-party MCP clients. source ↗
How to use it with AI
How Lovable connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
Not documentedVerify which side exports and which imports, supported formats and permissions. Lovable's recorded upload/import status is yes; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route.Lovable file docs ↗Claude (incl. Claude Code) file docs ↗
Not documentedOpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Lovable publishes an API, but this pairing still needs network, authentication and execution-scope checks.Lovable API ↗OpenAI Codex docs ↗
InferredOnly in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Lovable is a web app; the pairing itself is not documented.OpenAI Codex browser docs ↗
Not documentedVerify which side exports and which imports, supported formats and permissions. Lovable's recorded upload/import status is yes; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route.Lovable file docs ↗OpenAI Codex file docs ↗
InferredThe /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Lovable is a web app; the pairing itself is not documented.Google Antigravity browser docs ↗
Not documentedVerify which side exports and which imports, supported formats and permissions. Lovable's recorded upload/import status is yes; Google Antigravity's file status is yes. These flags do not establish a file-transfer route.Lovable file docs ↗Google Antigravity file docs ↗
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
Agent compatibility
MCPAPI/CLIFile import
Level
Status
Detail / source
Native connector / MCP
Yes
Official docs ↗ — OAuth only; all plans, with Enterprise administrator enablement required.
API / CLI
Yes
Official docs ↗ — workspace API keys require Business/Enterprise and an owner/admin role; project editing via AI uses MCP instead.
Browser / manual
No
Browser access is recorded alongside a documented programmatic route.
File upload / import
Yes
Official docs ↗ — get_file_upload_url provides a presigned URL for message attachments; this does not establish arbitrary full-project import.
Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.
Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.
AI code editor and agent harness (desktop app, CLI for terminal and CI, MCP support). Cursor is the app; you choose the model: GPT, Claude, Gemini or Grok. Plus covers only Cursor's own models (Grok and Composer); third-party models need Premium or above.
Visual website builder with CMS and hosting. Its native Framer Agent connection lets local agents such as Claude Code, Cursor, Codex and Gemini CLI make structured project updates. It does not require a separate MCP server.