How do ChatGPT and Claude build Lovable drafts?
ChatGPT and Claude can now build inside Lovable project drafts through the Lovable MCP server. Code changes stay in the draft until you approve them. This gives you a review step before changes enter a Lovable project.
Lovable added this workflow so you can inspect code, request a build, and review a summary before accepting the work. The draft approval step keeps changes in the draft while you decide whether they should enter the project. Team controls also cover connectors and API keys, with plan rules that determine which controls are available.
How do you build a Lovable draft with ChatGPT or Claude?
You can use ChatGPT or Claude through the Lovable MCP server to create, build, review, and approve a project draft.
- Connect ChatGPT or Claude to the Lovable MCP server. Use the client as the interface for creating and building the project draft.
- Ask ChatGPT or Claude to create a Lovable project draft for the feature you want to test. Keep the request focused on that draft first.
- Review the code and build inside the draft. Ask ChatGPT or Claude for a summary of the changes before moving to the acceptance step.
- Accept the draft in Lovable, or ask ChatGPT or Claude to accept it. If you do not approve it, the changes do not move into the project.
- On Enterprise plans, a workspace editor can request a disabled connector or one that only admins can connect. The editor sends the request from the connector’s page and can add an optional note.
- On Business and Enterprise plans, workspace admins and owners can require an IP allowlist on every workspace API key. An allowlist limits each key to the IP addresses you approve.
- After the requirement is enabled, every new key needs an allowlist. An existing key without one stops working until an admin or owner adds an allowlist to that key. The key remains in the list and does not need replacement.
Which Lovable plans support team controls?
Lovable limits connector requests to Enterprise and required IP allowlists to Business and Enterprise.
| Team control | Available plan | Who can use it | What it does |
|---|---|---|---|
| Connector requests | Enterprise | Workspace editors can request access | Admins and owners approve or decline requests in the Action center |
| Required IP allowlists | Business and Enterprise | Workspace admins and owners can set the requirement | Every workspace API key must use approved IP addresses |
Which prompt should you use for a Lovable draft?
Use a focused prompt that keeps code changes and builds inside the draft until you approve acceptance.
Create a draft in my Lovable project for this feature: [FEATURE]. Make the code changes and build inside the draft only. Summarize what changed, then wait for my approval before accepting the draft into the project.
The prompt gives ChatGPT or Claude a clear stopping point. The client should wait for your approval before accepting the draft into the Lovable project. After the build, ask for a summary, inspect the code, and request another build if the changes need more work.
How do Enterprise connector requests work?
Enterprise editors request access, while workspace admins and owners approve or decline requests in the Action center.
An editor can request a connector that is disabled or restricted to workspace admins. The request comes from the connector’s page and can include an optional note.
Lovable also shows a request button when the service suggests a connector in project chat or Chats. Workspace admins and owners then make the connector available or decline the request in the Action center.
Lovable notifies the editors who submitted the request in either case. Editors can ask for access, but admins and owners make the final decision.
How do required IP allowlists work for workspace API keys?
Business and Enterprise admins and owners can require an approved IP list for every workspace API key.
An IP allowlist limits each workspace API key to the IP addresses you approve. The requirement applies to every new key after an admin or owner enables it.
An existing key without an approved IP list stops working. The key stays in the list and does not need replacement. An admin or owner can restore access by adding an allowlist to that key.
Why does the Lovable draft approval step help?
The approval workflow lets you review code, request a build, and get a summary before changes enter the project.
ChatGPT and Claude can work inside a Lovable project draft without accepting the work early. You can inspect the code changes, ask for another build, and request a summary first.
Your approval decides whether the draft enters the Lovable project. Without approval, the changes remain in the draft. That makes the workflow useful when you want to test one focused feature before bringing it into the project.
My take
I would start with one focused feature and ask ChatGPT or Claude for a change summary before approving it. For Enterprise teams, I would review connector requests and IP allowlist rules early so the team knows who can request access and who makes the decision.
The catch
Building in a Lovable draft consumes standard build credits. Draft status changes when changes enter the project, not when ChatGPT or Claude creates them.
Team controls also depend on the Lovable plan. Connector requests are available through the policy on Enterprise plans, while required IP allowlists are available to admins and owners on Business and Enterprise plans. These controls do not replace administrator decisions.
Frequently asked questions
How do ChatGPT and Claude build a Lovable draft?
Connect ChatGPT or Claude to the Lovable MCP server. Then ask the client to create a draft and build code changes inside it.
Do Lovable draft builds use build credits?
Yes. Building in a draft counts as standard build usage and consumes Lovable build credits.
Which Lovable plans support connector requests?
Connector requests are available to workspace editors on Enterprise plans.
Can Lovable workspace API keys require IP allowlists?
Business and Enterprise admins and owners can require one for every workspace API key. Existing keys stop working until an allowlist is added.


