MCP serverPartly tested (needs an account)
Build and publish Lovable apps by chat
Lovable MCP
Lovable's official connector: create, change and publish Lovable web apps from your assistant, and check each change before it goes live on the web.
- Works with
- Claude Code, Codex CLI
- Good for
- Build an app
What it does
Lovable is an AI app builder that creates and hosts web apps. This is Lovable's official MCP server (a bridge that lets an AI assistant use an outside service), packed as a Claude Code plugin. With it, your assistant can work on your Lovable account: create projects, send instructions to Lovable's own builder, read code and diffs, look at visitor numbers, run database queries and publish apps.
You sign in with your Lovable account in the browser. OAuth sign-in (a browser login that gives the assistant a token) is the only way to connect. There is no API key for this server.
The plugin adds 3 commands on top of the server:
/lovable:build: create a new app from a description, and publish it if you say yes./lovable:iterate: send a change to an existing app and show you the diff./lovable:db: switch on a Postgres database for a project and run SQL.
The build and iterate commands tell the assistant to confirm with you before it spends credits. The db command tells it to show the SQL and ask before any write or table change.
Everything runs live on your real account. Only creating a project and sending a message to Lovable's builder use Lovable credits; Lovable's docs say the other tools are free. A database query runs with your full permissions, including writes and table changes. On Free and Pro plans, a published app is open to anyone with the link unless its website access is set to Invite only. The connection is not limited to one project: the assistant can reach every workspace and project your account can, and it can change project visibility, instructions and connectors.
The server works on all Lovable plans. On Enterprise workspaces an admin must first turn on third-party MCP clients in Workspace settings → Security → Privacy & security.
Who it is for
People who build apps on Lovable and want to start, change and publish them by talking to Claude Code or Codex instead of the Lovable editor.
Example prompts
- "/lovable:build A booking page for my hair salon with a calendar and a contact form"
- "List my Lovable projects and tell me which ones changed this week."
- "/lovable:iterate pricing-page — make the prices clearer and add a FAQ section. Ask before spending credits."
- "Show me the visitor numbers for my published shop app."
How to install
claude plugin install lovable@claude-plugins-officialcodex mcp add lovable --url https://mcp.lovable.devcodex mcp login lovableHow to use it
Ask: List my Lovable workspaces, then create a simple booking page project and show me the changes before you publish anything. Sign in to Lovable when asked.
Other assistants
Codex CLI (from Lovable's README; you get the server tools, not the 3 commands):
- Add the server:
codex mcp add lovable --url https://mcp.lovable.dev- Sign in to Lovable in your browser:
codex mcp login lovable- Ask Codex to list your Lovable workspaces.
Gemini CLI: Lovable gives no Gemini CLI steps, so we do not list a route.
Check it works
- Run
/mcpin Claude Code and look forlovable. Finish the Lovable sign-in in your browser. - Ask "list my Lovable workspaces". You should get your workspace names.
- If you prefer the server without the plugin, Lovable's README gives
claude mcp add --transport http lovable https://mcp.lovable.dev. Use one route, not both.
Common problems
- The install command cannot find the plugin — Claude Code cannot find
lovable@claude-plugins-official— Claude Code adds Anthropic's official plugin list the first time you open an interactive session. On a new machine or in a script, runclaude plugin marketplace add anthropics/claude-plugins-officialfirst. - Claude Code sign-in fails at the last step —
400 invalid_grantand "The 'redirect_uri' from this request does not match the one from the authorize request." — Open issue #7 says Lovable rejects thelocalhostsign-in address that Claude Code uses. Lovable's docs say local clients onlocalhostneed no approval, so the two sources disagree. There is no confirmed fix yet. Follow issue #7 or contact Lovable support. - Calls stop working after a while —
401 Unauthorized— Your sign-in expired. Run the login again (/mcpin Claude Code,codex mcp login lovablein Codex). On workspaces with SSO, log in to your identity provider again in the browser. - No Lovable tools appear — the server shows, but has no tools — Remove the Lovable entry and add it again, so the sign-in runs again.
- A tool fails on the workspace — a missing
workspace_id— Ask the assistant to list your workspaces first and use the ID it returns. - Publishing is refused — "Publishing was refused because the latest security scan found unresolved critical security findings" — Open the project's Security view in Lovable, fix or ignore the named findings, then publish again.
What to watch out for
- Creating a project and sending messages to Lovable's builder use your Lovable build credits (README)
- Publishing (deploy_project) puts your app on a public web address (README); say you do not want to publish until you are ready
- query_database runs SQL directly against your project's database (README); approve each call and keep backups
- Can add or remove connectors such as Notion, Slack or Linear on your Lovable project
- Acts as you in every Lovable workspace and project your account can reach, and can change project visibility and project instructions
- On an Enterprise workspace an admin must first turn on third-party MCP clients (Lovable docs)
- Open issue #7: Claude Code sign-in can fail with 400 invalid_grant because Lovable rejects localhost sign-in addresses; no fix yet
- On Free and Pro plans a published app is open to anyone with the link unless website access is Invite only (Lovable docs)
Licence and author
- Licence
- Apache-2.0
- Author
- Lovable
- Source code
- github.com/lovablelabs/mcp
How we tested it
We installed it on an empty test computer on 15 Oct 2026. Partly tested: installed in a clean test system, but its main features need an account or key we did not use.
We did not sign in or build an app, because that needs a Lovable account and uses build credits. Not run: the Codex lines. Not yet used on real work.
Technical details of the test
- Date
- 15 Oct 2026
- Method
- In a clean container with no account we installed lovable 0.1.0 from Anthropic's official plugin directory with the Claude Code command line (Claude Code 2.1.296). claude plugin list showed it as enabled, with the build, iterate and db commands, and claude mcp list showed Lovable's hosted server asking for a sign-in.
Checked again on 16 Oct 2026
Alternatives
- Wix skills: builds and manages Wix sites instead of Lovable apps.
- Expo skills: for phone apps built with Expo instead of hosted web apps.
FAQ
Does it cost credits? Creating projects and sending messages to Lovable's builder use your normal Lovable credits. Lovable's docs say the other tools are free.
Is my app public after I publish? On Free and Pro plans, yes, to anyone with the link, unless website access is Invite only. On Business and Enterprise plans it follows your workspace default.
Can I use an API key instead of signing in? No. Lovable's docs say OAuth is the only supported way to connect to the MCP server.
Sources
- github.com/lovablelabs/mcp
- docs.lovable.dev/integrations/lovable-mcp-server
- raw.githubusercontent.com/lovablelabs/mcp/main/README.md
- raw.githubusercontent.com/lovablelabs/mcp/main/CLAUDE.md
- raw.githubusercontent.com/lovablelabs/mcp/main/commands/build.md
- raw.githubusercontent.com/lovablelabs/mcp/main/commands/db.md
- github.com/lovablelabs/mcp/issues/7
- raw.githubusercontent.com/anthropics/claude-plugins-official/main/.claude-plugin/marketplace.json
- developers.openai.com/codex/mcp
- code.claude.com/docs/en/discover-plugins